Skip to content

Commit ffbcd1d

Browse files
authored
Merge pull request #40739 from github/repo-sync
Repo sync
2 parents 82aaa3b + 2b8d935 commit ffbcd1d

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

Dockerfile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
# ---------------------------------------------------------------
99
# To update the sha:
1010
# https://github.com/github/gh-base-image/pkgs/container/gh-base-image%2Fgh-base-noble
11-
FROM ghcr.io/github/gh-base-image/gh-base-noble:20251003-000207-g33acdaa18 AS base
11+
FROM ghcr.io/github/gh-base-image/gh-base-noble:20251006-204801-gaa06a8885 AS base
1212

1313
# Install curl for Node install and determining the early access branch
1414
# Install git for cloning docs-early-access & translations repos

content/copilot/concepts/agents/about-copilot-cli.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ The following sections provide examples of tasks you can complete with {% data v
9393

9494
* `List my open PRs`
9595

96-
This lists your open pull requests from any repository on GitHub. For more specific results, include the repository name in your prompt:
96+
This lists your open pull requests from any repository on {% data variables.product.github %}. For more specific results, include the repository name in your prompt:
9797

9898
* `List all open issues assigned to me in OWNER/REPO`
9999

@@ -103,11 +103,11 @@ The following sections provide examples of tasks you can complete with {% data v
103103

104104
* Ask {% data variables.product.prodname_copilot_short %} to make file changes and raise a pull request on {% data variables.product.prodname_dotcom_the_website %}.
105105

106-
* `In the root of this repo, add a Node script called user-info.js that outputs information about the user who ran the script. Create a pull request to add this file to the repo on GitHub.`
106+
* `In the root of this repo, add a Node script called user-info.js that outputs information about the user who ran the script. Create a pull request to add this file to the repo on {% data variables.product.github %}.`
107107

108108
* `Create a PR that updates the README at https://github.com/octo-org/octo-repo, changing the subheading "How to run" to "Example usage"`
109109

110-
Copilot creates a pull request on github.com, on your behalf. You are marked as the pull request author.
110+
Copilot creates a pull request on {% data variables.product.prodname_dotcom_the_website %}, on your behalf. You are marked as the pull request author.
111111

112112
* Ask {% data variables.product.prodname_copilot_short %} to create an issue for you on {% data variables.product.prodname_dotcom_the_website %}.
113113

@@ -127,7 +127,7 @@ The following sections provide examples of tasks you can complete with {% data v
127127

128128
* Find specific types of issues.
129129

130-
`Use the Github MCP server to find good first issues for a new team member to work on from octo-org/octo-repo`
130+
`Use the {% data variables.product.github %} MCP server to find good first issues for a new team member to work on from octo-org/octo-repo`
131131

132132
> [!NOTE]
133133
> If you know that a specific MCP server can achieve a particular task, then specifying it in your prompt can help {% data variables.product.prodname_copilot_short %} to deliver the results you want.
@@ -138,7 +138,7 @@ The following sections provide examples of tasks you can complete with {% data v
138138

139139
* Create a {% data variables.product.prodname_actions %} workflow.
140140

141-
`Branch off from main and create a github actions workflow that will run on pull requests, or can be run manually. The workflow should run eslint to check for problems in the changes made in the PR. If warnings or errors are found these should be shown as messages in the diff view of the PR. I want to prevent code with errors from being merged into main so, if any errors are found, the workflow should cause the PR check to fail. Push the new branch and create a pull request.`
141+
`Branch off from main and create a {% data variables.product.prodname_actions %} workflow that will run on pull requests, or can be run manually. The workflow should run eslint to check for problems in the changes made in the PR. If warnings or errors are found these should be shown as messages in the diff view of the PR. I want to prevent code with errors from being merged into main so, if any errors are found, the workflow should cause the PR check to fail. Push the new branch and create a pull request.`
142142

143143
## Security considerations
144144

0 commit comments

Comments
 (0)