Better debugging with GitHub Copilot on the web

GitHub Copilot Chat in github.com helps you get to the root cause of an error faster when you paste a stack trace. Copilot recognizes stack traces more reliably and will guide you through a structured root-cause analysis using the stack trace plus your repository’s code context, helping you move from “where it crashed” to “why it happened”.

Video

What’s changed

So that you can act faster, Copilot’s responses are now more structured in the following ways:

• What failed and where

• Why it failed and what assumption was violated

• The most likely root cause and where the invalid state was introduced

• Evidence from relevant code references

• A confidence level and suggested fix

• Next checks when verification is needed

Try it out

Paste a stack trace into GitHub Copilot Chat on the web and include the relevant repository or file context. If you have a repro step or input that triggers the error, add it for even faster root-cause analysis. This is available now to anyone using Copilot in github.com.

The post Better debugging with GitHub Copilot on the web appeared first on The GitHub Blog.