Firstly, we appreciate you thinking about contributing to dbt-vertica so that it can continue to evolve. This document will guide you through the contribution process. There are several ways you can help:
If you find a bug, submit an issue with a complete and reproducible bug report. If the issue can't be reproduced, it will be closed. If you opened an issue, but figured out the answer later on your own, comment on the issue to let people know, then close the issue.
For issues (e.g. security related issues) that are not suitable to be reported publicly on the GitHub issue system, report your issues to Vertica open source team directly or file a case with Vertica support if you have a support account.
Feel free to share your ideas for how to improve dbt-vertica. We’re always open to suggestions. You can open an issue with details describing what feature(s) you'd like added or changed.
If you would like to implement the feature yourself, open an issue to ask before working on it. Once approved, please refer to the Code Contributions section.
Fork the project on Github and check out your copy locally.
git clone [email protected]:YOURUSERNAME/dbt-vertica.git
cd dbt-verticaYour GitHub repository YOURUSERNAME/dbt-vertica will be called "origin" in Git. You should also set up vertica/dbt-vertica as an "upstream" remote.
git remote add upstream [email protected]:vertica/dbt-vertica.git
git fetch upstreamMake sure git knows your name and email address:
git config --global user.name "John Smith"
git config --global user.email "[email protected]"Create a new branch for the work with a descriptive name:
git checkout -b my-fix-branchInstall the dbt-vertica dependencies for development:
pip install dbt-vertica
dbt-vertica comes with a test suite of its own, in the Tests directory of the code base. It’s our policy to make sure all tests always pass. We appreciate any and all contributions to the test suite! These tests use a Pytest framework: testing. You might want to check out the testing documentation for more details.
Syntax tests do simple syntax testing of individual metrics and configs, which do not require database connection. Examples of running tests:
Run all test :
$ cd /tests$ pytest functional/adapter/The Github Actions CI workflow committed as part of the project will automatically run test suite through different pytest versions. These CI tests must pass before any PR will be considered. This CI workflow can be run on your forked repository after you are enabling Github Actions on your fork.
At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner at first.
Every file in this project must use the following Apache 2.0 header (with the appropriate year or years in the "[yyyy]" box; if a copyright statement from another party is already present in the code, you may add the statement on top of the existing copyright statement):
Copyright (c) [yyyy] Micro Focus or one of its affiliates.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Make some changes on your branch, then stage and commit as often as necessary:
git add.
git commit -m 'Added two more tests for #166'When writing the commit message, try to describe precisely what the commit does. The commit message should be in lines of 72 chars maximum. Include the issue number #N if the commit is related to an issue.
Add appropriate tests for the bug’s or feature's behavior, run the test suite again and ensure that all tests pass. Here is the guideline for writing test:
- Tests should be easy for any contributor to run. Contributors may not get complete access to their Vertica database, for example, they may only have a non-admin user with write privileges to a single schema, and the database may not be the latest version. We encourage tests to use only what they need and nothing more.
- If there are requirements to the database for running a test, the test should adapt to different situations and never report a failure. For example, if a test depends on a multi-node database, it should check the number of DB nodes first, and skip itself when it connects to a single-node database.
You can publish your work on GitHub just by doing:
$ git push origin my-fix-branchWhen you go to your GitHub page, you will notice commits made on your local branch is pushed to the remote repository. When upstream (vertica/dbt-vertica) has changed, you should rebase your work. The rebase command creates a linear history by moving your local commits onto the tip of the upstream commits.
You can rebase your branch locally and force-push to your GitHub repository by doing:
git checkout my-fix-branch
git fetch upstream
git rebase upstream/master
git push -f origin my-fix-branchWhen you think your work is ready to be pulled into dbt-vertica, you should create a pull request (PR) at GitHub. A good pull request means:
- commits with one logical change in each
- well-formed messages for each commit
- documentation and tests, if needed
- Go to https://github.com/YOURUSERNAME/dbt-vertica and make a Pull Request to vertica:master.
Note: When you initate a contribution some background tests run to verify you proposed changes pass. These tests can take 5 to 10 minutes to execute, so be patient. It is out there doing something when you see the pause in activity.
Before we can accept a pull request, we first ask people to sign a Contributor License Agreement (or CLA). We ask this so that we know that contributors have the right to donate the code. You should notice a comment from CLAassistant on your pull request page, follow this comment to sign the CLA electronically.
Pull requests are usually reviewed within a few days. If there are comments to address, apply your changes in new commits, rebase your branch and force-push to the same branch, re-run the test suite to ensure tests are still passing. We care about quality, Vertica has internal test suites to run as well, so your pull request won't be merged until all internal tests pass. To produce a clean commit history, our maintainers would do squash merging once your PR is approved, which means combining all commits of your PR into a single commit in the master branch.
You are done! Thank you for your code contribution!
After your pull request is merged, you can safely delete your branch and pull the changes from the upstream repository.