Skip to content

Clarify limitations of copilot-setup-steps concerning call of reusable workflows #44493

Description

@KubaZ

Code of Conduct

What article on docs.github.com is affected?

https://github.com/proxy/docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment

What part(s) of the article would you like to see updated?

The documentation for copilot-setup-steps does not explicitly state that calling reusable workflows via jobs.<job-id>.uses is not supported. This causes confusion for users who try to extract shared setup logic into a reusable workflow and reference it from the copilot-setup-steps job.

Current behavior

The copilot-setup-steps.yml documentation lists the job-level properties that can be customized (steps, permissions, runs-on, services, snapshot, timeout-minutes). However, it does not explicitly call out that uses at the job level — which is how GitHub Actions reusable workflows are invoked — is not among the supported properties and will be silently ignored or will cause unexpected behavior.

A user might reasonably author:

jobs:
  copilot-setup-steps:
    uses: ./.github/workflows/shared-setup.yml

...expecting the reusable workflow to run as part of Copilot's environment setup, only to find it does not work as intended.

Expected behavior

The documentation should explicitly state that:

  • jobs.<job-id>.uses (reusable workflow calls) is not supported in copilot-setup-steps.
  • Only inline steps are supported; shared setup logic must be inlined or extracted into a composite action (using uses inside a steps entry) rather than a reusable workflow.

Suggested workaround (to be documented)

Instead of a reusable workflow, users can extract shared setup steps into a composite action and reference it within a step:

jobs:
  copilot-setup-steps:
    runs-on: ubuntu-latest
    steps:
      - uses: ./.github/actions/shared-setup  # composite action — supported

References

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on May 29, 2026
  2. welcome commented on May 29, 2026

    @welcome

    Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

  3. added
    triageDo not begin working on this issue until triaged by the team
    on May 29, 2026
  4. added
    copilotContent related to GitHub Copilot
    and removed
    triageDo not begin working on this issue until triaged by the team
    on Jun 10, 2026
  5. Sharra-writes commented on Jun 10, 2026

    @Sharra-writes
    Contributor

    @KubaZ I've reached out to the Copilot team to make sure this is working as intended and to find out if they think it should be documented. I will let you know what they tell me.

  6. github-actions commented on Aug 10, 2026

    @github-actions
    Contributor

    A stale label has been added to this issue, because it has been open for 30 days with no activity. If you think this issue should remain open, please add a new comment.

  7. added
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Aug 10, 2026
  8. added and removed
    InactiveWill be closed automatically by a stall check if no activity is detected.
    on Sep 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    builder personacontentThis issue or pull request belongs to the Docs Content teamcopilotContent related to GitHub Copilotnever-staleDo not close as stale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions