Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit79ba132

Browse files
authored
sub list formatting
1 parentffa3c9d commit79ba132

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

‎squash-commits/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,23 +4,23 @@ Please, go through these steps before you submit a PR.
44
1. Make sure that your PR is not a duplicate.
55
2. If not, then make sure that:
66

7-
a. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the`fix/` or`feature/` prefixes. Good examples are:`fix/signin-issue` or`feature/issue-templates`.
7+
a. You have done your changes in a separate branch. Branches MUST have descriptive names that start with either the`fix/` or`feature/` prefixes. Good examples are:`fix/signin-issue` or`feature/issue-templates`.
88

9-
b. You have a descriptive commit message with a short title (first line).
9+
b. You have a descriptive commit message with a short title (first line).
1010

11-
c. You have only one commit (if not, squash them into one commit).
11+
c. You have only one commit (if not, squash them into one commit).
1212

13-
d.`npm test` doesn't throw any error. If it does, fix them first and amend your commit (`git commit --amend`).
13+
d.`npm test` doesn't throw any error. If it does, fix them first and amend your commit (`git commit --amend`).
1414

1515
3.**After** these steps, you're ready to open a pull request.
1616

17-
a. Your pull request MUST NOT target the`master` branch on this repository. You probably want to target`staging` instead.
17+
a. Your pull request MUST NOT target the`master` branch on this repository. You probably want to target`staging` instead.
1818

19-
b. Give a descriptive title to your PR.
19+
b. Give a descriptive title to your PR.
2020

21-
c. Provide a description of your changes.
21+
c. Provide a description of your changes.
2222

23-
d. Put`closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).
23+
d. Put`closes #XXXX` in your comment to auto-close the issue that your PR fixes (if such).
2424

2525
IMPORTANT: Please review the[CONTRIBUTING.md](../CONTRIBUTING.md) file for detailed contributing guidelines.
2626

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp