Repository navigation
Add CI to dry run repositories.yaml changes - #1097
Merged
Merged
Conversation
BenWu
force-pushed
the
benwu/dryrun-ci
branch
from
October 22, 2026 21:47
e425a67 to
1086e2f
Compare
Contributor
probe-scraper output diffChanges to the Glean metadata probe-scraper would publish with this PR, compared to the base branch. Metrics, pings and tags are not scraped, so the per-app No changes to probe-scraper output. Generated for c768276 by this workflow run at 2026-10-26 19:59 UTC. |
BenWu
marked this pull request as ready for review
October 26, 2026 20:05
badboy
approved these changes
Oct 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds CI workflow to diff dry run outputs for main and the PR branch when repositories.yaml is changed, and posts a single comment that gets updated on each commit.
The dry run runs for forked PRs but the comment does not, so you would need to go to the workflow run page to see the diff. It's likely fine to run for forks but this is easier to reason about the security so I would rather leave that out for now.