Skip to content

Commit b0aa744

Browse files
authored
Merge branch 'main' into docs/amend-copilot-cli-hooks-tutorial-bash-demo-rule
2 parents 5f3b817 + fca2765 commit b0aa744

9,167 files changed

Lines changed: 12743974 additions & 9817181 deletions

File tree

Some content is hidden

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

‎.devcontainer/devcontainer.json‎

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@
1515
"ghcr.io/devcontainers/features/copilot-cli:1": {
1616
"version": "prerelease"
1717
},
18-
"ghcr.io/devcontainers/features/github-cli:1": {}
18+
"ghcr.io/devcontainers/features/github-cli:1": {},
19+
"ghcr.io/devcontainers/features/docker-in-docker:2": {}
1920
},
2021

2122
"customizations": {

‎.env.example‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
# This file is a template for what your untracked .env file might look like for local development.
22
# Please copy this to a new .env file and fill in the values as needed.
33

4-
# Requires a running local Elasticsearch service. Can be started via Docker, see https://github.com/github/docs-engineering/blob/main/docs/elasticsearch/elasticsearch-locally.md
4+
# Requires a running local Elasticsearch service. Can be started via Docker, see https://github.com/github/technical-content/blob/main/engineering/search/elasticsearch-locally.md
55
# When this value is unset searches will be proxied to the production Elasticsearch endpoint
66
ELASTICSEARCH_URL=http://localhost:9200
77

8-
# Set for sending events in local development. See https://github.com/github/docs-engineering/blob/main/docs/analytics/hydro-mock.md
8+
# Set for sending events in local development. See https://github.com/github/technical-content/blob/main/analytics/hydro-mock.md
99
HYDRO_ENDPOINT=
1010
HYDRO_SECRET=
1111

‎.gitattributes‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
# Set default behavior, in case users don't have core.autocrlf set.
22
* text=auto
3-
# Explicitly declare text files we want to always be normalized and converted
4-
# to native line endings on checkout.
5-
*.md text diff=markdown
3+
# Explicitly declare text files we want to always be normalized, and for
4+
# Markdown files, enforce LF line endings on checkout.
5+
*.md text eol=lf diff=markdown
66
*.json.br filter=lfs diff=lfs merge=lfs -text
7+
.github/workflows/*.lock.yml linguist-generated=true merge=ours

‎.github/CODEOWNERS‎

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,5 @@
66
# Site Policy
77
content/site-policy/ @github/site-policy-admins
88

9-
# Enterprise
10-
data/release-notes/**/*.yml @github/docs-content-enterprise
11-
src/ghes-releases/lib/enterprise-dates.json @github/docs-content-enterprise
12-
139
# Requires review of #actions-oidc-integration, docs-engineering/issues/1506
1410
# content/actions/deployment/security-hardening-your-deployments/** @github/oidc

‎.github/CONTRIBUTING.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -78,11 +78,11 @@ For complete style guidance, see our [style guide](https://docs.github.com/en/co
7878

7979
<img src="/contributing/images/contribution_cta.png" />
8080

81-
**Make changes in a codespace:** See "[Working in a codespace](https://github.com/github/docs/blob/main/contributing/codespace.md)" for documentation-specific setup.
81+
**Make changes in a codespace:** See "[Working on GitHub Docs in a codespace](https://docs.github.com/en/contributing/setting-up-your-environment-to-work-on-github-docs/working-on-github-docs-in-a-codespace)" for documentation-specific setup.
8282

8383
**Make changes locally:**
8484
1. Fork the repository (see [official forking guide](https://docs.github.com/en/contributing))
85-
2. Install Node.js at the version specified in `.node-version` (see [development guide](../contributing/development.md))
85+
2. Install Node.js at the version specified in `package.json` (see [development guide](../contributing/development.md))
8686
3. Create a working branch and start with your changes
8787

8888
### Commit your update
@@ -100,7 +100,7 @@ Use our "[Self review checklist](https://docs.github.com/en/contributing/collabo
100100
- [Link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if applicable
101101
- Enable [maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork)
102102

103-
A Docs team member will review following our [standard review process](https://docs.github.com/en/contributing).
103+
A Technical Content team member will review following our [standard review process](https://docs.github.com/en/contributing).
104104

105105
### Your PR is merged!
106106

@@ -116,7 +116,7 @@ This site can be developed on Windows, however a few potential gotchas need to b
116116

117117
1. Regular Expressions: Windows uses `\r\n` for line endings, while Unix-based systems use `\n`. Therefore, when working on Regular Expressions, use `\r?\n` instead of `\n` in order to support both environments. The Node.js [`os.EOL`](https://nodejs.org/api/os.html#os_os_eol) property can be used to get an OS-specific end-of-line marker.
118118
2. Paths: Windows systems use `\` for the path separator, which would be returned by `path.join` and others. You could use `path.posix`, `path.posix.join` etc and the [slash](https://ghub.io/slash) module, if you need forward slashes - like for constructing URLs - or ensure your code works with either.
119-
3. Bash: Not every Windows developer has a terminal that fully supports Bash, so it's generally preferred to write [scripts](/script) in JavaScript instead of Bash.
119+
3. Bash: Not every Windows developer has a terminal that fully supports Bash, so it's generally preferred to write new scripts in TypeScript rather than Bash.
120120
4. Filename too long error: There is a 260 character limit for a filename when Git is compiled with `msys`. While the suggestions below are not guaranteed to work and could cause other issues, a few workarounds include:
121121
- Update Git configuration: `git config --system core.longpaths true`
122122
- Consider using a different Git client on Windows

‎.github/actions/clone-translations/action.yml‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,56 +11,56 @@ runs:
1111
using: 'composite'
1212
steps:
1313
- name: Clone Spanish
14-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
14+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
1515
with:
1616
repository: github/docs-internal.es-es
1717
token: ${{ inputs.token }}
1818
path: translations/es-es
1919

2020
- name: Clone Japanese
21-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
21+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
2222
with:
2323
repository: github/docs-internal.ja-jp
2424
token: ${{ inputs.token }}
2525
path: translations/ja-jp
2626

2727
- name: Clone Portuguese
28-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
28+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
2929
with:
3030
repository: github/docs-internal.pt-br
3131
token: ${{ inputs.token }}
3232
path: translations/pt-br
3333

3434
- name: Clone Simplified Chinese
35-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
35+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
3636
with:
3737
repository: github/docs-internal.zh-cn
3838
token: ${{ inputs.token }}
3939
path: translations/zh-cn
4040

4141
- name: Clone Russian
42-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
42+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
4343
with:
4444
repository: github/docs-internal.ru-ru
4545
token: ${{ inputs.token }}
4646
path: translations/ru-ru
4747

4848
- name: Clone French
49-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
49+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
5050
with:
5151
repository: github/docs-internal.fr-fr
5252
token: ${{ inputs.token }}
5353
path: translations/fr-fr
5454

5555
- name: Clone Korean
56-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
56+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
5757
with:
5858
repository: github/docs-internal.ko-kr
5959
token: ${{ inputs.token }}
6060
path: translations/ko-kr
6161

6262
- name: Clone German
63-
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
63+
uses: actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8 # v6.0.1
6464
with:
6565
repository: github/docs-internal.de-de
6666
token: ${{ inputs.token }}
Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
name: Create workflow failure issue
2+
description: Create or update a GitHub issue in technical-content when a workflow fails, for automated diagnosis by an agentic workflow.
3+
4+
inputs:
5+
token:
6+
description: A token with issues write permission on the target repo
7+
required: true
8+
repo:
9+
description: The repository to create the issue in
10+
default: github/technical-content
11+
required: false
12+
13+
outputs:
14+
issue_url:
15+
description: URL of the created or updated workflow-failure issue (empty if creation failed).
16+
value: ${{ steps.create-new.outputs.issue_url || steps.comment-existing.outputs.issue_url }}
17+
18+
runs:
19+
using: composite
20+
steps:
21+
- name: Check for existing open issue
22+
id: check-existing
23+
shell: bash
24+
env:
25+
GH_TOKEN: ${{ inputs.token }}
26+
ISSUE_REPO: ${{ inputs.repo }}
27+
WORKFLOW_NAME: ${{ github.workflow }}
28+
run: |
29+
existing=$(gh issue list \
30+
--repo "$ISSUE_REPO" \
31+
--label "workflow-failure" \
32+
--search "in:title [Workflow Failure] $WORKFLOW_NAME" \
33+
--state open \
34+
--json number \
35+
--jq '.[0].number // empty' 2>/dev/null || true)
36+
echo "existing_issue=$existing" >> "$GITHUB_OUTPUT"
37+
38+
- name: Comment on existing issue
39+
id: comment-existing
40+
if: steps.check-existing.outputs.existing_issue != ''
41+
shell: bash
42+
env:
43+
GH_TOKEN: ${{ inputs.token }}
44+
ISSUE_REPO: ${{ inputs.repo }}
45+
ISSUE_NUMBER: ${{ steps.check-existing.outputs.existing_issue }}
46+
WORKFLOW_NAME: ${{ github.workflow }}
47+
SOURCE_REPO: ${{ github.repository }}
48+
RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
49+
EVENT_NAME: ${{ github.event_name }}
50+
GIT_REF: ${{ github.ref }}
51+
run: |
52+
body=$(cat <<EOF
53+
### Repeat failure
54+
55+
**Workflow:** \`$WORKFLOW_NAME\`
56+
**Repository:** \`$SOURCE_REPO\`
57+
**Run:** $RUN_URL
58+
**Event:** \`$EVENT_NAME\`
59+
**Ref:** \`$GIT_REF\`
60+
**Timestamp:** $(date -u +%Y-%m-%dT%H:%M:%SZ)
61+
EOF
62+
)
63+
gh issue comment "$ISSUE_NUMBER" \
64+
--repo "$ISSUE_REPO" \
65+
--body "$body"
66+
echo "issue_url=$GITHUB_SERVER_URL/$ISSUE_REPO/issues/$ISSUE_NUMBER" >> "$GITHUB_OUTPUT"
67+
68+
- name: Create workflow failure issue
69+
id: create-new
70+
if: steps.check-existing.outputs.existing_issue == ''
71+
shell: bash
72+
env:
73+
GH_TOKEN: ${{ inputs.token }}
74+
ISSUE_REPO: ${{ inputs.repo }}
75+
WORKFLOW_NAME: ${{ github.workflow }}
76+
SOURCE_REPO: ${{ github.repository }}
77+
RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
78+
EVENT_NAME: ${{ github.event_name }}
79+
GIT_REF: ${{ github.ref }}
80+
ACTOR: ${{ github.actor }}
81+
run: |
82+
body=$(cat <<EOF
83+
### Workflow failure
84+
85+
**Workflow:** \`$WORKFLOW_NAME\`
86+
**Repository:** \`$SOURCE_REPO\`
87+
**Run:** $RUN_URL
88+
**Event:** \`$EVENT_NAME\`
89+
**Ref:** \`$GIT_REF\`
90+
**Triggered by:** \`$ACTOR\`
91+
**Timestamp:** $(date -u +%Y-%m-%dT%H:%M:%SZ)
92+
93+
---
94+
This issue was automatically created by the create-workflow-failure-issue action to enable automated diagnosis.
95+
EOF
96+
)
97+
url=$(gh issue create \
98+
--repo "$ISSUE_REPO" \
99+
--label "workflow-failure" \
100+
--label "workflow-generated" \
101+
--label "engineering" \
102+
--label "priority-2" \
103+
--title "[Workflow Failure] $WORKFLOW_NAME" \
104+
--body "$body")
105+
echo "issue_url=$url" >> "$GITHUB_OUTPUT"
106+
107+
# Set the type separately, and tolerate failure. This action is itself the
108+
# failure path, so losing the whole issue because issue types are unavailable
109+
# or `gh` is too old (--type needs gh 2.94+) would hide the original failure.
110+
gh issue edit "$url" --type Bug \
111+
|| echo "Warning: could not set issue type on $url; leaving it unset."

‎.github/actions/get-changed-files/action.yml‎

Lines changed: 0 additions & 40 deletions
This file was deleted.

0 commit comments

Comments
 (0)