Skip to content

fix(ci): create the tracking label only when missing #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gkorland merged 1 commit into from
Aug 13, 2026
Merged

fix(ci): create the tracking label only when missing #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 11 additions & 4 deletions .github/workflows/report-scheduled-failure.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,11 @@
#
# Pin to a full commit SHA rather than a branch: `secrets: inherit` and mutable
# refs together would let any later change here run with the caller's secrets.
# Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, so the
# clients still get changes made here without hand-editing eight workflows.
# Dependabot's github-actions ecosystem updates `jobs.<id>.uses` pins, so where
# the calling repo has it enabled (all the clients currently do), the pin is
# kept current automatically and the clients still get changes made here without
# hand-editing eight workflows. Without such an updater, the pin is yours to
# bump.
#
# The `github` context always belongs to the caller, so the repository, workflow
# name and run URL below are the calling repo's without being passed in.
Expand Down Expand Up @@ -85,8 +88,12 @@ jobs:
"$RUN_URL" \
"" \
"Set the \`DRIVERS_GOOGLE_CHAT_WEBHOOK_URL\` secret to receive this in Google Chat instead.")
gh label create "$LABEL" --force \
--color d93f0b --description "Nightly CI run against falkordb/falkordb:edge is failing"
# 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
Comment on lines +91 to +93
gh label create "$LABEL" \
--color d93f0b --description "Nightly CI run against falkordb/falkordb:edge is failing"
fi
# Find the issue by label rather than `--search`: the search index is
# only eventually consistent, so two failures in quick succession
# would each open their own issue. Label filtering goes through the
Expand Down