diff options
| author | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-10 23:58:30 +0300 |
|---|---|---|
| committer | Yuriy Andamasov <yuriy@vyos.io> | 2026-05-10 23:58:30 +0300 |
| commit | 2d56ca8f842c3902fdd5214de2447a1cf2393628 (patch) | |
| tree | 3607dc66e8b411491ef6bbe773e4eaf2118daf84 /docs/_static/css/linkButtons.css | |
| parent | be0085e6697de97de71a8d35855afb13309514f5 (diff) | |
| download | vyos-documentation-2d56ca8f842c3902fdd5214de2447a1cf2393628.tar.gz vyos-documentation-2d56ca8f842c3902fdd5214de2447a1cf2393628.zip | |
ci: gate skip-notice on opened/reopened only
CodeRabbit minor finding on the paired canonical PR
(VyOS-Networks/vyos-docs-opus-reviewer#14): the `Notify on PR (when
skipping)` step posts a fresh `gh pr comment` on every `synchronize`
event. On a fork PR to a repo where the AI-validation secrets are not
configured, every push during PR iteration would duplicate the skip
notice, flooding the conversation thread.
Gate the step to fire only on `opened`/`reopened` — those are the
moments where the PR author benefits from being told once that
validation is skipped. Further pushes add no new information; the
workflow-run-page `::notice::` annotation is still emitted on every run
for maintainers.
`concurrency.cancel-in-progress: true` alone is not sufficient — most
synchronize events would be cancelled before the notify step ran, but
any run that completed the notify step before the next push still
posts the comment.
Paired canonical commit: VyOS-Networks/vyos-docs-opus-reviewer@ea88567
Diffstat (limited to 'docs/_static/css/linkButtons.css')
0 files changed, 0 insertions, 0 deletions
