When you create a pull request, consider the following:
Bug or Feature Description
If it's a bug, how does it affect a customer?
If it's a feature, why do we need it?
Description of Your Change
If it's a bug, how did you fix it?
If it's a feature, what does it do?
Link to Design
If there is an external design, add a link to it. (The design should include a link to the discussion on the Forum)
Testing Logs or Output
Please attach your test log output from running the test you added (or from existing tests that cover your changes)
Optional Considerations
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