"Fix merge conflicts with copilot" prewrites a message, that does nothing.

[kubo6472]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Copilot in GitHub

Body

I clicked "fix with copilot" and send the message it composed here. Nothing has happened since. I do not think this is how it is supposed to work, right?

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

[SouravRoy-ETL]

Yeah that's the expected behavior actually, even if the UX is confusing. The "Fix with Copilot" button just drops a pre-composed @copilot resolve the merge conflicts in this pull request comment into the box it doesn't auto-send it. You still have to hit Comment yourself to actually trigger Copilot.
Looking at your screenshot it looks like the message is just sitting there composed but not submitted. Click the Comment button below the textbox and Copilot should pick it up and start working on a resolution (it'll push commits to the PR branch).
If you did submit it and still nothing happened, check whether Copilot coding agent is actually enabled for the repo — it's a separate setting from Copilot chat/completions.

[kubo6472]

Okay, it has been sent and it does not show the mention @copilot as bold (like it does with some other bot/users).

Some Copilot stuff works, like CodeQL, but this is set as shown:

[SouravRoy-ETL]

The "@copilot not rendering as bold" thing is actually the smoking gun. That tells you Copilot cloud agent is not enabled for this repo, so the mention is just plain text and nothing is listening for it. The "Fix with Copilot" button doesn't check whether the agent is actually wired up before composing the message, which is why the UX is so confusing.
Important distinction: what your screenshot shows is Copilot Code Review settings. That is a completely separate product from Copilot cloud agent (also called the coding agent). They are not the same thing and enabling one does not enable the other:

Copilot Code Review = leaves comments on your PR. Read-only. This is what you have on.
Copilot cloud agent = actually pushes commits, resolves conflicts, responds to @copilot. This is what "Fix merge conflicts" needs. Not enabled for you.

To get the agent working you need three things in place:

A plan that includes it. Cloud agent is on Copilot Pro, Pro+, Business, and Enterprise. If you are on the free tier or a plan that does not include it, the @copilot mention will silently do nothing.
The agent enabled. On Business or Enterprise plans, an admin has to turn it on. The setting is not in the repo's Code Review page you screenshotted. It is under your personal Copilot settings (github.com/settings/copilot/features) or the org's Copilot policies if you are on a paid org plan. Look for "Copilot coding agent" or "Cloud agent" toggle.
Write access to the repo. The agent only responds to mentions from users with write permission.

How to know it is working once you flip it on: when you post the @copilot comment, the mention should render bold and linked, Copilot should add a 👀 reaction to your comment within a minute, and a "Copilot started work" event should appear in the PR timeline. If none of that happens, it is still not enabled.
Side note for GitHub if anyone from the team is reading: the "Fix with Copilot" button should either be hidden or show a tooltip when cloud agent is not provisioned for the user/repo. Composing a message that nothing will respond to is a bad pattern.