/
Pull Request Guidelines
Pull Request Guidelines
When you create a pull request, consider the following:
Pull Request Guidelines
Step Required for a feature? Required for a bug? Code follows coding style Required Required Design document in project documentation area Required Helpful for complex bugs Added PTL tests, or, if necessary, manual tests Required Required Added test output/logs Checked for memory leaks Join the pbspro community forum Optional Optional Sign the CLA Pull request consists of a single commit Commit is up to date Whenever possible Whenever possible Git ticket filed Optional Optional Code is signed off by at least one maintainer, and another contributor Required Required Code header contains license text Required Required PTL test header created by developer contains license text Required Required
, multiple selections available,
Related content
PP-1255: Guidelines for design documents
PP-1255: Guidelines for design documents
More like this
Checklist for Developing Features and Bug Fixes
Checklist for Developing Features and Bug Fixes
More like this
Inactive Pull Requests Closed
Inactive Pull Requests Closed
More like this
Shared links
Shared links
More like this
PTL User's Guide
PTL User's Guide
More like this
Rebasing Your Dev Branch
Rebasing Your Dev Branch
More like this