Skip to content

Commit 2f43c18

Browse files
committed
add pull request template
1 parent 5736d6e commit 2f43c18

File tree

2 files changed

+36
-0
lines changed

2 files changed

+36
-0
lines changed

.github/pull_request_template.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
**Checklist** <!-- Mandatory -->
2+
3+
Please verify the following checklist in order:
4+
- [ ] If releasing module changes, the Pull Request title is prepended with "[\<Azure Stack Hub Release Version\>]". E.g., a title may be "[2301] Compute RP changes". Otherwise, this is not necessary.
5+
- [ ] Updated origin `dev` branch locally. (`git fetch origin dev`)
6+
- [ ] The Pull Request has a single commit. The following is a standard way to achieve a single commit:
7+
- `git checkout feature`
8+
- `git rebase origin/dev -i`
9+
- In the VIM editor press `ESC` and `i` to enter edit mode.
10+
- Select commits to fixup or squash commits (instructions are in the editor).
11+
- Press `ESC`, type `:wq`, and press `Enter` to save and quit.
12+
- [ ] Resolved any rebase conflicts (basically merge conflicts).
13+
- [ ] Commits are rebased on top of latest remote `dev` branch.
14+
- [ ] The changes are tested. Make sure to test after the rebase step.
15+
- [ ] Updated remote feature branch. (Force push if you've rebased onto new changes from dev: `git push origin feature -f`)
16+
17+
**Description** <!-- Mandatory -->
18+
<!-- Give a detailed description of the changes. For small changes, you can just copy the single commit message. If releasing a new module version, this can be the same as the changelog update. If for some reason the pull request requires multiple commits, explain why that is required as well. -->
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
**Checklist** <!-- Mandatory -->
2+
3+
Please verify the following checklist in order:
4+
- [ ] If releasing module changes, the Pull Request title is prepended with "[\<Azure Stack Hub Release Version\>]". E.g., a title may be "[2301] Compute RP changes". Otherwise, this is not necessary.
5+
- [ ] Updated origin `dev` branch locally. (`git fetch origin dev`)
6+
- [ ] The Pull Request has a single commit. The following is a standard way to achieve a single commit:
7+
- `git checkout feature`
8+
- `git rebase origin/dev -i`
9+
- In the VIM editor press `ESC` and `i` to enter edit mode.
10+
- Select commits to fixup or squash commits (instructions are in the editor).
11+
- Press `ESC`, type `:wq`, and press `Enter` to save and quit.
12+
- [ ] Resolved any rebase conflicts (basically merge conflicts).
13+
- [ ] Commits are rebased on top of latest remote `dev` branch.
14+
- [ ] The changes are tested. Make sure to test after the rebase step.
15+
- [ ] Updated remote feature branch. (Force push if you've rebased onto new changes from dev: `git push origin feature -f`)
16+
17+
**Description** <!-- Mandatory -->
18+
<!-- Give a detailed description of the changes. For small changes, you can just copy the single commit message. If releasing a new module version, this can be the same as the changelog update. If for some reason the pull request requires multiple commits, explain why that is required as well. -->

0 commit comments

Comments
 (0)