Skip to content

Commit 99c4c69

Browse files
authored
Uodate guidance in PR template
1 parent 951bb12 commit 99c4c69

File tree

1 file changed

+11
-3
lines changed

1 file changed

+11
-3
lines changed

PULL_REQUEST_TEMPLATE.md

Lines changed: 11 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,19 @@
22
33
Thanks for creating a pull request to request a new subdomain from JS.ORG
44
5-
Before creating your pull request, please complete the following steps:
5+
Before creating your pull request, please read and complete the following steps:
66
77
- Ensure that your pull request changes only the cnames_active.js file, adding a single new line for your subdomain request
8-
- Tick the two checkboxes, agreeing to the sentences, below by placing an x inside the square brackets ([ ] becomes [x])
9-
- Add a link (GitHub repository, Vercel deployment, etc.) and explanation below for your content so we can validate your request
8+
- Follow the existing format established by the other entries, a new line with the subdomain as the key and the target hostname as the value
9+
- Add your new line to the file in alphabetical order, and follow the guidance given by the comments in the file itself
10+
11+
- Fill out this pull request template in your pull request description, maintaining the format provided to you
12+
- Tick the two checkboxes, agreeing to the sentences, below by placing an x inside the square brackets ([ ] becomes [x])
13+
- Add a link (GitHub repository, Vercel deployment, etc.), so we can review your site
14+
- Explain what your site content is and how it relates to the JavaScript community/ecosystem, so we can validate your request
15+
16+
- Ensure that your site content follows the content requirements set out in our README: https://github.com/js-org/js.org#content-requirements
17+
- Notably, make sure that your site is not a personal site, and that it is clearly content that is relevant to the JavaScript community/ecosystem
1018
1119
-->
1220

0 commit comments

Comments
 (0)