Skip to content

Conversation

Copilot
Copy link
Contributor

@Copilot Copilot AI commented Oct 16, 2025

Summary

Moves the copilot-setup-steps.yml file from .github/ to .github/workflows/ to comply with GitHub Copilot's documentation requirements.

Problem

The copilot-setup-steps.yml file was located in the .github/ directory, but according to GitHub's documentation, this file should be located in the .github/workflows/ directory.

Changes

  • Moved .github/copilot-setup-steps.yml.github/workflows/copilot-setup-steps.yml
  • No content changes to the file itself

Verification

The file has been successfully relocated using git mv to preserve its history, and the content remains identical.

Fixes the incorrect file location to match GitHub's expected structure for Copilot agent customization files.

Original prompt

The copilot-setup-steps file is in the wrong location. https://docs.github.com/en/copilot/how-tos/use-copilot-agents/coding-agent/customize-the-agent-environment says it should be in a workflows directory rather than directly under .github


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

@Copilot Copilot AI changed the title [WIP] Move copilot-setup-steps to workflows directory Move copilot-setup-steps.yml to workflows directory per GitHub documentation Oct 16, 2025
@Copilot Copilot AI requested a review from stephentoub October 16, 2025 16:42
Copilot finished work on behalf of stephentoub October 16, 2025 16:42
@stephentoub stephentoub marked this pull request as ready for review October 16, 2025 16:42
@stephentoub stephentoub merged commit 6537514 into main Oct 16, 2025
3 checks passed
@stephentoub stephentoub deleted the copilot/move-copilot-setup-steps branch October 16, 2025 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants