If you would like to contribute code you can do so through GitHub by forking the repository and sending a pull request. Please follow these guidelines:
- Always retain backwards compatibility, unless a breaking change is necessary. If it is necessary, the associated release notes must make this explicit and obvious;
- Make every effort to follow existing conventions and style;
- Follow PEP8;
- Follow the Google Python Style Guide for docstrings;
- Use spaces, not tabs;
- Update the rez version appropriately, and follow semantic versioning;
- Use this format to mention the issue(s) your PR closes;
- Add relevant tests to demonstrate that your changes work;
- Add relevant documentation here to document your changes, if applicable. Those
markdown files prefixed with
_
are internal and should not be changed. - If your changes add a new rez config setting, update rezconfig.py and document the setting. The comments in this file are extracted and turned into documentation. Pay attention to the comment formatting and follow the existing style closely.
Rez enforces use of a Contributor License Agreement as per ASWF guidelines. You need only sign up to the EasyCLA system once, but until you do, your PRs will be automatically blocked.
For more info see https://easycla.lfx.linuxfoundation.org/#/
Rez enforces Developer Certificate of Origin (DCO) on all commits, as per ASWF guidelines. PRs are automatically blocked until all commits within the PR are signed off.
To automatically add the necessary sign-off line to every commit, we suggest you do the following,
in the root of the project (you'll only need to do it once, and the template file has been added
to .gitignore
):
]$ echo "Signed-off-by: $(git config user.name) <$(git config user.email)>" > .git-commit-template
]$ git config commit.template .git-commit-template
For more info see https://github.blog/changelog/2022-06-08-admins-can-require-sign-off-on-web-based-commits/ for web-based commits, and https://probot.github.io/apps/dco/ for all others.
If you report a bug, please ensure to specify the following:
- Rez version (e.g. 2.18.0);
- Platform and operating system you were using;
- Contextual information (what were you trying to do using Rez);
- Simplest possible steps to reproduce.