Feature Request: Inline comments to suppress/ignore Copilot suggestion

[briankessler-ef]

Select Topic Area

Product Feedback

Copilot Feature Area

Copilot in GitHub

Body

Feature Request: Inline Suppression Comments for GitHub Copilot

Similar to how static analysis tools like SonarQube (// NOSONAR) or
ReSharper (// ReSharper disable) allow developers to suppress specific
warnings or suggestions at the line level, it would be valuable to have
similar functionality for GitHub Copilot.

Proposed syntax examples:

• // copilot:ignore
• // @copilot-disable-line
• // copilot:suppress-next-line

Use cases:

1. Suppressing suggestions for intentionally written code patterns
2. Preventing suggestions in sensitive code sections
3. Avoiding repetitive dismissal of unwanted suggestions
4. Better developer control over AI assistance

BONUS ENHANCEMENT: Cross-Tool Compatibility
GitHub Copilot should also respect existing suppression comments from
other development tools, including but not limited to:

• Visual Studio: #pragma warning disable, // TODO:, // HACK:
• ReSharper: // ReSharper disable, // ReSharper restore
• IntelliJ IDEA: //noinspection, @SuppressWarnings
• SonarQube: // NOSONAR
• PMD: // NOPMD
• ESLint: // eslint-disable-line
• StyleCop: #pragma warning disable SA####
• Code Analysis: [SuppressMessage(...)]

ADVANCED ENHANCEMENT: Solution-Wide Configuration Awareness
In contexts where Copilot has access to the entire solution, it should
also respect broader suppression and configuration settings from:

Configuration Files:

• .editorconfig (code style preferences, rule suppressions)
• .DotSettings files (ReSharper team-shared settings)
• ruleset files (*.ruleset for Code Analysis)
• omnisharp.json (OmniSharp configuration)
• Directory.Build.props (MSBuild-wide suppressions)

Project-Level Suppressions:

• GlobalSuppressions.cs files
• AssemblyInfo.cs suppressions
• Project file elements
• Package.json lint configurations (for mixed solutions)

This solution-wide awareness would:

1. Respect team coding standards automatically
2. Align Copilot suggestions with established project conventions
3. Prevent suggestions that violate configured style rules
4. Honor deliberately disabled analysis rules
5. Provide consistent behavior across the entire solution
6. Reduce cognitive load on developers

Implementation could be phased:
Phase 1: Native Copilot suppression syntax
Phase 2: Recognition of common inline suppression patterns
Phase 3: Solution-wide configuration file awareness
Phase 4: Project-level suppression integration

This would provide granular developer-level control, excellent ecosystem
integration, AND solution-wide consistency, making Copilot a true
team-aware development assistant that respects existing project
conventions and standards.

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

[AshleyGrant]

This would be great as I'm currently getting Copilot Code Review comments about something that I've suppressed warnings from CodeQL.