]> git.proxmox.com Git - ceph.git/blame - ceph/.github/pull_request_template.md
bump version to 14.2.5-pve1
[ceph.git] / ceph / .github / pull_request_template.md
CommitLineData
11fdf7f2
TL
1
2<!--
3Thank you for opening a pull request! Here are some tips on creating
4a well formatted contribution.
5
6Please give your pull request a title like "[component]: [short description]"
7
8This is the format for commit messages:
9
10"""
11[component]: [short description]
12
13[A longer multiline description]
14
15Fixes: [ticket URL on tracker.ceph.com, create one if necessary]
16Signed-off-by: [Your Name] <[your email]>
17"""
18
19The Signed-off-by line is important, and it is your certification that
20your contributions satisfy the Developers Certificate or Origin. For
21more detail, see SubmittingPatches.rst.
22
23The component is the short name of a major daemon or subsystem,
24something like "mon", "osd", "mds", "rbd, "rgw", etc. For ceph-mgr modules,
25give the component as "mgr/<module name>" rather than a path into pybind.
26
27For more examples, simply use "git log" and look at some historical commits.
28
29This was just a quick overview. More information for contributors is available here:
30https://raw.githubusercontent.com/ceph/ceph/master/SubmittingPatches.rst
31
32-->
eafe8130 33## Checklist
11fdf7f2
TL
34- [ ] References tracker ticket
35- [ ] Updates documentation if necessary
36- [ ] Includes tests for new functionality or reproducer for bug
37
eafe8130
TL
38---
39
40<details>
41<summary>Show available Jenkins commands</summary>
42
43- `jenkins retest this please`
44- `jenkins test make check`
45- `jenkins test make check arm64`
46- `jenkins test submodules`
47- `jenkins test dashboard`
48- `jenkins test dashboard backend`
49- `jenkins test docs`
50- `jenkins render docs`
51
52</details>