/
Pull Request Guidelines

Pull Request Guidelines

When you create a pull request, consider the following:

Pull Request Guidelines


StepRequired for a feature?Required for a bug?
Code follows coding styleRequiredRequired
Design document in project documentation areaRequiredHelpful for complex bugs
Added PTL tests, or, if necessary, manual testsRequiredRequired
Added test output/logs

Checked for memory leaks

Join the pbspro community forumOptionalOptional
Sign the CLA

Pull request consists of a single commit

Commit is up to dateWhenever possibleWhenever possible
Git ticket filedOptionalOptional
Code is signed off by at least one maintainer, and another contributorRequiredRequired
Code header contains license textRequiredRequired
PTL test header created by developer contains license text
RequiredRequired

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