Skip to content

Signal that the copilot-setup-steps.yml samples are illustrative - #45862

Open
brignano wants to merge 1 commit into
github:mainfrom
brignano:claude/github-docs-42379-fix-b46de1
Open

Signal that the copilot-setup-steps.yml samples are illustrative#45862
brignano wants to merge 1 commit into
github:mainfrom
brignano:claude/github-docs-42379-fix-b46de1

Conversation

@brignano

Copy link
Copy Markdown
Contributor

Why:

Closes: #45861

Follow-up to #42379 and #45823, per @subatoi's suggestions on that issue.

What's being changed (if available, include any code snippets, screenshots, or gifs):

#45823 generalized the copy around the copilot-setup-steps.yml sample so it reads as illustrative. Two things still worked against that, plus one consistency fix:

1. The sample rendered a copy buttoncontent/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment.md

Dropped the copy annotation from the fence, so the sample keeps its syntax highlighting but no longer offers one-click copying of config the surrounding text advises against copying verbatim.

2. The tutorial prompt generates the file from that articlecontent/copilot/tutorials/cloud-agent/improve-a-project.md

The step 2 prompt asks Copilot to author copilot-setup-steps.yml using the reference article's details, so it reproduced both triggers. The prompt now ends:

Make sure that the workflow job is named copilot-setup-steps, and that the workflow includes a workflow_dispatch trigger so that it can be run manually. Choose any other triggers to suit this repository; there's no need to run on both push and pull_request.

3. The extract below that prompt showed triggers the text doesn't mention — same file

The sentence above it calls out only the on: workflow_dispatch trigger and the job name, so the extract is trimmed to those. Without this it would contradict the prompt it's meant to help verify.

Two files, three hunks, no changes to the sample workflow's own configuration.

Check off the following:

  • A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
  • The changes in this PR meet the docs fundamentals that are required for all content.
  • All CI checks are passing and the changes look good in the review environment.

Follow-up to issue 42379, per maintainer feedback. The sample workflow is meant
to illustrate rather than to be copied verbatim, but two things worked against
that.

Drop the `copy` annotation from the sample's fence in the reference article, so
it no longer renders a copy button.

In the "Improve a project" tutorial, extend the prompt that asks Copilot to
author the file, so the generated workflow gets a `workflow_dispatch` trigger
and doesn't run on both `push` and `pull_request`. Trim the extract below it to
the trigger and job name the surrounding sentence calls out, so it no longer
shows triggers the text never mentions.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FuL8Cm3afpXSBiiGnUo7FA
@github-actions

Copy link
Copy Markdown
Contributor

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source Review Production What Changed
copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment.md fpt
ghec
fpt
ghec
copilot/tutorials/cloud-agent/improve-a-project.md fpt
ghec
fpt
ghec

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

@github-actions github-actions Bot added the triage Do not begin working on this issue until triaged by the team label Sep 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

triage Do not begin working on this issue until triaged by the team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Signal that the copilot-setup-steps samples are illustrative, not copy-ready

3 participants