Skip to content

Commit acc7698

Browse files
saritaisaritai
authored
Merge branch 'main' into patch-1
2 parents f098026 + e443d87 commit acc7698

File tree

13,285 files changed

+192168
-68252
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

13,285 files changed

+192168
-68252
lines changed

‎.devcontainer.json

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,12 @@
22
// For format details, see https://aka.ms/vscode-remote/devcontainer.json
33
{
44
"name": "docs.github.com",
5-
"service": "container-doc",
65
"settings": {
76
"terminal.integrated.shell.linux": "/bin/bash",
87
"cSpell.language": ",en"
98
},
10-
// Install pre-requisites, and start to serve docs.github.com locally
11-
"postCreateCommand": "npm install && npm start",
9+
// Install pre-requisites and run a build to ensure we are ready to start serving docs.github.com locally (via `npm start`)
10+
"postCreateCommand": "npm ci && npm run build",
1211
"forwardPorts": [4000],
1312
// Visual Studio Code extensions which help authoring for docs.github.com.
1413
"extensions": [

‎.github/CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Order is important. The LAST matching pattern has the MOST precedence.
22
# gitignore style patterns are used, not globs.
3-
# https://help.github.com/articles/about-codeowners
3+
# https://docs.github.com/articles/about-codeowners
44
# https://git-scm.com/docs/gitignore
55

66
# Engineering

‎.github/ISSUE_COMMENT_TEMPLATE/target-date.yml

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
name: Target Date Update
3+
about: Target date update
4+
body:
5+
- type: input
6+
attributes:
7+
name: Target completion date
8+
placeholder: With context if the target completion date has changed
9+
inputType: text
10+
- type: input
11+
attributes:
12+
name: 'Attribution'
13+
value: '_created with :heart: by typing_ `/status`'
14+
inputType: text

‎.github/ISSUE_TEMPLATE/partner-contributed-documentation.md

Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
name: Partner-owned product documentation
3+
about: Initiate a set of tasks to be completed by a GitHub partner wishing to document how their product works with GitHub
4+
title: ''
5+
labels:
6+
- partner
7+
assignees: ''
8+
---
9+
10+
<!--
11+
Thank you for your interest in contributing to the GitHub documentation.
12+
13+
This issue template is only for use by GitHub's Technology Partners who wish to contribute documentation explaining how the partner's product works with GitHub, making it straightforward for our shared customers to adopt the product into their workflow.
14+
15+
As a general guide, we estimate we have bandwidth for prioritizing and reviewing up to 3 partner contributions per quarter.
16+
17+
Please be sure to complete all items in the checklists that follow, and feel free to comment with any questions. A member of the team will be glad to support you.
18+
-->
19+
20+
## Pre-requisites
21+
22+
- [ ] Prior to submitting documentation, please apply to join the GitHub Technology Partner Program: [partner.github.com/apply](https://partner.github.com/apply?partnershipType=Technology+Partner). Please feel free to proceed once your application is approved.
23+
24+
## What information would you like to add to docs.github.com?
25+
<!-- Please explain what your proposed article is about, what customers it benefits, and any other information that would help us to prioritize this request -->
26+
27+
## Tasks
28+
29+
Please be sure to complete each of the following:
30+
31+
**Third-party product documentation:**
32+
33+
- [ ] MUST follow our [general contributing guidelines](CONTRIBUTING.md) for voice and markup format.
34+
- [ ] MUST emphasize how the third-party product works with GitHub.
35+
- [ ] MUST be written in Markdown format, using [one of the templates provided](contributing/github-partners/README.md#templates)
36+
- [ ] MUST include the name and URL of the GitHub technology partner responsible for maintenance of the documentation being contributed. This should be added via the `contributor.name` and `contributor.URL` properties in the template's YAML frontmatter.
37+
- [ ] MUST be proposed via a pull request to this repo following [the GitHub Flow](https://guides.github.com/introduction/flow/).
38+
- [ ] MUST be located in the root of [the `content` folder](content). Your filename MUST match the GitHub technology partner name, and use the `.md` file extension.
39+
40+
**The `Pull Request`:**
41+
42+
- [ ] MUST reference this issue, e.g. via `closes #<this issue number>`
43+
- [ ] MUST pass the automated CI checks
44+
- [ ] MUST include links to supporting material demonstrating the functionality being documented (this can be a link to a public GitHub repo, _or_ a video / screencast walkthrough)
45+
46+
Once all tasks are completed, please mention `@github/docs-content` for next steps.
47+
48+
/cc @github/partner-engineering for :eyes:

‎.github/ISSUE_TEMPLATE/production-config-change.md

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Change production configuration
3+
about: Track changes to the production docs.github.com site
4+
title: ''
5+
labels: engineering
6+
assignees: ''
7+
---
8+
9+
A configuration change would be something outside of our code that we change with our production environment, such as environment variables, virtual machine tier or quantity, or service providers.
10+
11+
- _Primary person_:
12+
- _Second person_:
13+
- _When_:
14+
- _Zoom URL_:
15+
16+
### What is the configuration change?
17+
18+
### Why are we updating this configuration?
19+
20+
### What risks are there with this configuration change?
21+
22+
### If an issue happens, how do we roll back?
23+
24+
Once the change is verified good, please close this issue.

‎.github/allowed-actions.js

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ module.exports = [
1111
"actions/setup-node@c46424eee26de4078d34105d3de3cc4992202b1e", //actions/[email protected]
1212
"ruby/setup-ruby@fdcfbcf14ec9672f6f615cb9589a1bc5dd69d262", //ruby/[email protected]
1313
"actions/stale@9d6f46564a515a9ea11e7762ab3957ee58ca50da", //actions/stale@v3.0.16
14+
"alex-page/github-project-automation-plus@fdb7991b72040d611e1123d2b75ff10eda9372c9",
15+
"andymckay/labeler@22d5392de2b725cea4b284df5824125054049d84",
1416
"archive/github-actions-slack@d368c5a4ad757515a9344918f84c490b05777d94",
1517
"ashley-taylor/regex-property-action@93a24f845cd20790924208225cc72da8b4c6d46d",
1618
"crowdin/github-action@fd9429dd63d6c0f8a8cb4b93ad8076990bd6e688",
@@ -25,7 +27,6 @@ module.exports = [
2527
"juliangruber/find-pull-request-action@2fc55e82a6d5d36fe1e7f1848f7e64fd02d99de9",
2628
"juliangruber/read-file-action@e0a316da496006ffd19142f0fd594a1783f3b512",
2729
"lee-dohm/close-matching-issues@22002609b2555fe18f52b8e2e7c07cbf5529e8a8",
28-
"octokit/graphql-action@5b3e01d42dee4509b0ac6b1cb2cf7778cdce85c2",
2930
"pascalgn/automerge-action@c9bd1823770819dc8fb8a5db2d11a3a95fbe9b07", //pascalgn/[email protected]
3031
"peter-evans/create-issue-from-file@a04ce672e3acedb1f8e416b46716ddfd09905326",
3132
"peter-evans/create-or-update-comment@5221bf4aa615e5c6e95bb142f9673a9c791be2cd",
@@ -37,6 +38,6 @@ module.exports = [
3738
"repo-sync/pull-request@33777245b1aace1a58c87a29c90321aa7a74bd7d",
3839
"someimportantcompany/github-actions-slack-message@0b470c14b39da4260ed9e3f9a4f1298a74ccdefd",
3940
"tjenkinson/gh-action-auto-merge-dependency-updates@4d7756c04d9d999c5968697a621b81c47f533d61",
40-
"EndBug/add-and-commit@9358097a71ad9fb9e2f9624c6098c89193d83575",
41+
"EndBug/add-and-commit@b3c7c1e078a023d75fb0bd326e02962575ce0519",
4142
"dorny/paths-filter@eb75a1edc117d3756a18ef89958ee59f9500ba58",
4243
];

‎.github/workflows/60-days-stale-check.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
name: 60 Days Stale Check
2+
3+
# **What it does**: Pull requests older than 60 days will be flagged as stale.
4+
# **Why we have it**: We want to manage our queue of issues and pull requests.
5+
# **Who does it impact**: Everyone that works on docs or docs-internal.
6+
27
on:
38
schedule:
49
- cron: '40 16 * * *' # Run each day at 16:40 UTC / 8:40 PST

‎.github/workflows/auto-label-prs.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
name: Auto label Pull Requests
22

3+
# **What it does**: Automatically adds the engineering label when specific files change.
4+
# **Why we have it**: Other automation applies specifically to engineering label issues and pull requests.
5+
# **Who does it impact**: Automation that relies on the engineering label.
6+
37
on:
48
pull_request:
59

‎.github/workflows/automerge-dependencies.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,9 @@
11
name: Auto Merge Dependency Updates
22

3+
# **What it does**: Automatically merge pull requests from dependabot.
4+
# **Why we have it**: To keep our dependencies up-to-date, to avoid security issues.
5+
# **Who does it impact**: It helps docs engineering focus on higher value work.
6+
37
on:
48
pull_request:
59
paths:

‎.github/workflows/automerge.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11
name: automerge
2+
3+
# **What it does**: Pull requests with label "automerge" or "autosquash" will automatically merge.
4+
# **Why we have it**: While now this is a feature built into GitHub, we still use it as part of other automation.
5+
# **Who does it impact**: Any workflows that depend on automerge or autosquash labels.
6+
27
on:
38
pull_request:
49
types:

0 commit comments

Comments
 (0)