57 lines (34 loc) · 1.9 KB

Contributing

We warmly welcome and appreciate contributions from the community! By participating you agree to the code of conduct. To contribute:

Sign our Contributor License Agreement.
Fork the gpupgrade repository on GitHub.
Clone the repository.
Follow the README to set up your environment and run the tests.
Create a change
- Create a topic branch.
- Make commits as logical units for ease of reviewing.
- Try and follow similar coding styles as found throughout the code base.
- Rebase with master often to stay in sync with upstream.
- Add appropriate tests and view coverage with make coverage.
- Ensure a well written commit message as explained here and here.
- Format code with make format.
- Address any linter issues with make lint.
Submit a pull request (PR).
- Create a pull request from your fork.
- We will create a test pipeline which runs additional acceptance tests based on your branch.
- Address PR feedback with fixup and/or squash commits.
```
git add .
git commit --fixup <commit SHA> 
    Or
git commit --squash <commit SHA>
```
- Once approved, before merging into master squash your fixups with:
```
git rebase -i --autosquash origin/master
git push --force-with-lease $USER <my-feature-branch>
```

Community

Connect with Greenplum on: