mirror of
https://github.com/nubenetes/awesome-kubernetes.git
synced 2026-07-20 22:01:16 +00:00
ci: add [skip ci] to 03.2/03.3 bot commits to stop the develop write-lock burst
The V2 pipeline is meant to advance only via its workflow_run chain (03.1 -> 03.2 -> 03.3 -> 04.1), which [skip ci] does not affect. But 03.2 and 03.3 committed data/inventory.yaml WITHOUT [skip ci], so their bot pushes also matched push: path triggers: 03.2 re-triggered itself (and 03.3 triggered it backward) on data/inventory.yaml, and data/inventory.sql woke 05.1. That redundant fan-out flooded the shared develop-git-write-lock group; with cancel-in-progress: false GitHub keeps only one pending run per group, so superseded runs were auto-cancelled (0 jobs, no logs) - e.g. run 29263339507. Every other develop-pushing stage (03.1, 04.1, 05.1, 09) already carries [skip ci]; this completes the pattern on the two stages that were missing it. The workflow_run chain, schedule, and workflow_dispatch entry points are unaffected. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
2
.github/workflows/03.2.agentic_v2_ai.yml
vendored
2
.github/workflows/03.2.agentic_v2_ai.yml
vendored
@@ -79,7 +79,7 @@ jobs:
|
||||
if git diff --staged --quiet; then
|
||||
echo "No changes in AI analysis to commit."
|
||||
else
|
||||
git commit -m "chore: update inventory AI analysis"
|
||||
git commit -m "chore: update inventory AI analysis [skip ci]"
|
||||
# Retry rebase+push to survive concurrent bot pushes to develop.
|
||||
for i in {1..5}; do
|
||||
git pull origin develop --rebase && git push origin develop && exit 0
|
||||
|
||||
2
.github/workflows/03.3.agentic_v2_videos.yml
vendored
2
.github/workflows/03.3.agentic_v2_videos.yml
vendored
@@ -89,7 +89,7 @@ jobs:
|
||||
if git diff --staged --quiet; then
|
||||
echo "No automated changes to commit."
|
||||
else
|
||||
git commit -m "docs: update Video Hub with high-fidelity metadata"
|
||||
git commit -m "docs: update Video Hub with high-fidelity metadata [skip ci]"
|
||||
# Retry rebase+push to survive concurrent bot pushes to develop.
|
||||
for i in {1..5}; do
|
||||
git pull origin develop --rebase && git push origin develop && exit 0
|
||||
|
||||
Reference in New Issue
Block a user