Coding Agent doesn't cope well with pre-commit and pre-push hooks

[z0u]

Select Topic Area

Bug

Copilot Feature Area

Copilot Coding Agent

Body

My repository contains pre-commit and pre-push hooks that run some basic checks. They're installed in my copilot-setup-steps.yml. The hooks are:

# pre-commit (quick checks)
ruff check --quiet --no-fix
ruff format --quiet --check

# pre-push (slow checks)
basedpyright
pytest --quiet

I added them specifically because Copilot Coding Agent was submitting PRs that couldn't be merged due to basic linting errors. But when they result in an error, Copilot just gives up:

Caution

Copilot stopped work due to an error

Copilot encountered an unknown Git error. If the problem persists, please contact GitHub Support. To retry, leave a comment on this pull request asking Copilot to try again.

Here's an example session where this happens, and the line in the detailed logs.

 GitError unknown git error: Command failed with exit code 1: git commit -m REDACTED git commit -m REDACTED
  + .git/hooks/pre-commit.d/30-fast-checks.sh
  + uv run --no-sync ruff check --quiet --no-fix
  + uv run --no-sync ruff format --quiet --check
  Would reformat: src/utils/progress/lightning.py
  Would reformat: tests/utils/progress/test_distributed.py
  format: ❌ failure. Try ./go format
    lint: ✅ success
...
  Committing and pushing any changes that occurred before error occurred.
...
  forceExit is shutting down the process

For now I'll remove the hooks from Coding Agent's environment. But it would be nice to have a way to tell it that it should run certain commands and try to fix any errors before marking the PR as ready for review. In this instance, it could have just run ./go format to fix the errors before committing again.

[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. ⭐

[Jonatthu]

It’s been a while and really important