bahman/ceph
1
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
Files
wip-s3vector
ceph/.github/pull_request_template.md
John Mulligan 81b2d6c48e doc: github: add a note reminding to use one command per comment 
When I started using ceph I also thought it would be natural to issue >1
command per comment, but it doesn't work. I saw someone else doing it
recently and thought it would be good to have this reminder in the PR
template.

Signed-off-by: John Mulligan <jmulligan@redhat.com>
2025-09-15 16:40:11 -04:00

5.2 KiB
Raw Permalink Blame History

Contribution Guidelines

  • To sign and title your commits, please refer to Submitting Patches to Ceph.

  • If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

  • When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an x between the brackets: [x]. Spaces and capitalization matter when checking off items this way.

Checklist

  • Tracker (select at least one)
    • References tracker ticket
    • Very recent bug; references commit where it was introduced
    • New feature (ticket optional)
    • Doc update (no ticket needed)
    • Code cleanup (no ticket needed)
  • Component impact
    • Affects Dashboard, opened tracker ticket
    • Affects Orchestrator, opened tracker ticket
    • No impact that needs to be tracked
  • Documentation (select at least one)
    • Updates relevant documentation
    • No doc update is appropriate
  • Tests (select at least one)
Show available Jenkins commands

You must only issue one Jenkins command per-comment. Jenkins does not understand comments with more than one command.

Reference in New Issue View Git Blame Copy Permalink