You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/instructions/code.instructions.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ For code reviews, follow guidelines, tests, and validate instructions. For creat
16
16
- Avoid pull requests with over 300 lines of code changed. When significantly larger, offer to split up into smaller pull requests if possible.
17
17
- All new code should be written in TypeScript and not JavaScript.
18
18
- We use absolute imports, relative to the `src` directory, using the `@` symbol. For example, `getRedirect` which lives in `src/redirects/lib/get-redirect.ts` can be imported with `import getRedirect from '@/redirects/lib/get-redirect'`. The same rule applies for TypeScript (`.ts`) imports, e.g. `import type { GeneralSearchHit } from '@/search/types'`
19
+
- For updates to the content linter, read important information in `src/content-linter/README.md`.
# **What it does**: Automatically adds the "ready-for-doc-review" label to DIY docs PRs that contain content or data changes when they are opened in a non-draft state or converted from draft to ready for review.
4
+
# **Why we have it**: To ensure DIY docs PRs are automatically added to the docs-content review board without requiring manual labeling.
5
+
# **Who does it impact**: Contributors making content changes and docs-content reviewers.
6
+
7
+
on:
8
+
pull_request:
9
+
types:
10
+
- opened
11
+
- ready_for_review
12
+
paths:
13
+
- 'content/**'
14
+
- 'data/**'
15
+
16
+
permissions:
17
+
contents: read
18
+
pull-requests: write
19
+
20
+
jobs:
21
+
add-review-label:
22
+
name: Add ready-for-doc-review label to DIY docs PRs
gh pr comment $PR --body "## Requesting a review from the Docs team
48
48
49
-
**ποΈ Is this PR ready for review?** A PR is ready for a docs review _after_ the self-review checklist is complete.
49
+
### π§ Draft PRs
50
50
51
-
When this is ready for review, add the **\`ready-for-doc-review\`** label to this PR. The PR will then be automatically added to the [Docs Content review board](https://github.com/orgs/github/projects/2936). _Please allow at least 3 working days for a review, and longer if this is a substantial change._"
51
+
To add the PR to the Docs Content review board, click **Ready for review** in the merge box.
52
+
53
+
### π Non-draft PRs
54
+
55
+
The PR is **ready** and has automatically been added to the Docs Content review board. The docs team will review it as soon as possible.
56
+
57
+
### Lead time for review
58
+
59
+
Please allow at least 3 business days for a Docs Content review.
60
+
61
+
### Need help?
62
+
63
+
Reach out in [#docs-content](https://github-grid.enterprise.slack.com/archives/C0E9DK082) on Slack."
0 commit comments