chore: add scheduled branch cleanup report#90
Draft
aranhave wants to merge 3 commits into
Draft
Conversation
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
1 participant
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.
Summary
Adds the same scheduled branch cleanup report we started in
mobile-o11y-demo, adjusted forfaro-react-native-sdk.Reference: grafana/mobile-o11y-demo#67
This is still read-only. It does not delete branches. The goal is to make leftover branch cleanup easier to review without manually clicking through the branch list.
What changed
workflow_dispatchcreate_issueinput for one-off reports/testingNotes
The first local report found no merged-PR cleanup candidates, but it did surface no-PR and automation branches. That seems useful for this repo because those are categories GitHub's auto-delete setting does not cover.
I kept this as a draft so we can decide if we want this reporting pattern in the React Native SDK repo too, or keep it only in
mobile-o11y-demofor now.Testing
I checked this locally by running the audit script against
grafana/faro-react-native-sdkwith the 14-day settings and confirmed it generated the expected dry-run report. I also ran a basic syntax check on the script and checked the diff for formatting issues.