Feature request: allow reusable workflow in copilot-setup-steps.yml

[carlos-quintero]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot Coding Agent

Body

When you have many repos of the same kind (for example, .NET repos that generate/publish NuGet packages), each one requires a copilot-setup-steps.yml file to set up GitHub Copilot Coding Agent. I would like all the copilot-setup-steps.yml files to call the same reusable workflow in one common repo.

Currently you get this error:

"Calling a reusable workflow with the uses: keyword is not supported in copilot-setup-steps jobs. Please specify the steps directly. For more details, see https://gh.io/copilot/actions-setup-steps."

I would like that limitation to be removed.

PS: I know I can reuse a GitHub Actions action of type "composite", but I would like to reuse a workflow

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[martinlansler]

+1 on this request... it's a must if having multiple repos that require a copilot-setup-steps.yaml

[mungojam]

see https://github.com/orgs/community/discussions/170877#discussioncomment-14593749 for a helpful workaround by @carlos-quintero that works for us