ppalaga commented on issue #990: [CAMEL-13704] - Added PR template file with instructions on what to include URL: https://github.com/apache/camel-quarkus/pull/990#issuecomment-604894462 I'd propose something like this: [ ] An [issue](https://github.com/apache/camel-quarkus/issues) should be filed for the change unless this is a trivial change (fixing a typo or similar). One issue should ideally be fixed by not more than one commit and the other way round, each commit should fix just one issue, without pulling in other changes. [ ] Each commit in the pull request should have a meaningful and properly spelled subject line and body. Copying the title of the associated issue is typically enough. Please include the issue number in the commit message prefixed by `#`. [ ] The pull request description should explain what the pull request does, how, and why. If the info is available in the associated issue or some other external document, a link is enough. [ ] Phrases like `Fix #<issueNumber>` or `Fixes #<issueNumber>` will auto-close the named issue upon merging the pull request. Using them is typically a good idea. [ ] Please run `mvn process-resources -Pformat` (and amend the changes if necessary) before sending the pull request. [ ] Contributor guide is your good friend: https://camel.apache.org/camel-quarkus/latest/contributor-guide.html
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
