fix(ci): create the tracking label only when missing - #13
Merged
Conversation
|
Warning Review limit reached
Next review available in: 89 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
gkorland
added a commit
to FalkorDB/falkordb-ts
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-py
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-go
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-rs
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-php
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/JFalkorDB
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/NFalkorDB
that referenced
this pull request
Aug 13, 2026
Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the reusable scheduled-failure reporter workflow to avoid mutating an existing tracking label in the caller repository, and clarifies the note about Dependabot keeping uses: pins up to date.
Changes:
- Check for the tracking label via
gh apiand create it only if missing (removinggh label create --force). - Clarify that Dependabot-based pin updates depend on the caller repo having the
github-actionsecosystem enabled.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+91
to
+93
| # Create the label only when it is missing: `--force` would overwrite | ||
| # the colour and description of a pre-existing label of the same name. | ||
| if ! gh api "repos/$GH_REPO/labels/$LABEL" --silent 2>/dev/null; then |
gkorland
added a commit
to FalkorDB/falkordb-py
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-ts
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-go
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/NFalkorDB
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-php
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/JFalkorDB
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
gkorland
added a commit
to FalkorDB/falkordb-rs
that referenced
this pull request
Aug 13, 2026
* ci: use the shared report-scheduled-failure workflow Every official FalkorDB client carries a byte-identical copy of this job, so any change to the alert has to be made in eight places. Call the reusable workflow in FalkorDB/.github instead and keep only the gating that is specific to this repo. Behaviour is unchanged: the `github` context inside a called workflow belongs to the caller, so the repository, workflow name and run URL in the alert stay the same. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): pin the shared reporter and pass only its declared secret Review feedback: `secrets: inherit` combined with a mutable `@main` ref would let any later change to the shared workflow run with this repo's secrets. Pin to a reviewed commit SHA and map only DRIVERS_GOOGLE_CHAT_WEBHOOK_URL, which is the single secret the workflow declares. Pinning does not reintroduce the duplication this removed: Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, and it is already enabled here. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix(ci): bump shared reporter pin to include the label fix Picks up FalkorDB/.github#13, which creates the tracking label only when it is missing rather than overwriting a pre-existing label of the same name. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
Follow-up to review comments on #10.
gh label create --forceoverwrites the colour and description of a pre-existing label of the same name in the caller's repo. Create the label only when it is actually missing.github-actionsecosystem enabled (all seven clients currently do). Say so.Changes
gh api repos/$GH_REPO/labels/$LABELand create the label only on a miss; drop--force.Testing
Verified both paths against a temporary dispatch harness, with the webhook unset so the issue fallback runs:
color=ededed, original description), issue still labelled correctlyactionlintclean. Harness, label, test issues and runs cleaned up.Memory / Performance Impact
N/A — CI configuration only.
Related Issues
Follow-up to #5 and #10.