shared-workflows v0.24.0 - Automatic Copilot reviews for Go
OpenTelemetry shared-workflows v0.24.0, published on October 26, 2026, enables automatic Copilot reviews for Go repositories. The release also changes how Copilot feedback passes back to authors, makes pull request authors easier to identify, and skips the FOSSA check in forks.
The full release notes are on the GitHub release page. GitHub does not mark v0.24.0 as a prerelease.
Automatic Copilot reviews and author replies
The Go review change makes Copilot review automatic for Go repositories covered by this workflow. For maintainers, that changes how automated feedback enters the review process. If your repository uses this setup, review activity is the first place to check when adopting v0.24.0.
Copilot feedback also moves to normal author reply handoffs. This matters after the review arrives: the author reply follows the usual handoff process. The two changes address separate parts of review work, starting a review and handling the author’s response. Teams using Copilot during pull request review should look at both when assessing the release.
A useful check follows one pull request through both steps: when Copilot adds feedback, then what happens when the author responds. That checks the behavior the release notes call out in a real review.
Human authors and dashboard badges
Human authors now appear for Copilot draft pull requests. A draft involving Copilot can still need a person to answer questions or explain intent. Showing the human author gives reviewers that context while they decide what needs attention.
The pull request dashboard also gains author badges. These put another author cue into the dashboard itself, where maintainers scan multiple pull requests.
For a busy review queue, these changes are useful at different moments. Human attribution helps when looking at a Copilot draft; badges help while scanning the dashboard. Both changes concern the information available to the person choosing what to review next.
FOSSA skips runs in forks
The FOSSA check now skips running in forks. A skipped check on a fork is therefore expected behavior with this release.
When comparing CI results between a fork and upstream, account for this difference before treating the skipped FOSSA run as a workflow failure. This change is most relevant to contributors testing changes in their own forks and maintainers inspecting those runs.