Skip to content

[ci] Update PR validation workflow - #659

Open
nemesifier wants to merge 1 commit into
masterfrom
ci/update-pr-validation-workflow
Open

[ci] Update PR validation workflow#659
nemesifier wants to merge 1 commit into
masterfrom
ci/update-pr-validation-workflow

Conversation

@nemesifier

Copy link
Copy Markdown
Member

Checklist

  • I have read the OpenWISP Contributing Guidelines and OpenWISP Anti AI Spam Policy.
  • N/A. This GitHub Actions caller-workflow change has no local manual execution path.
  • N/A. No application code changed.
  • N/A. No user-facing behavior or documentation changed.

Reference to Existing Issue

Related to openwisp/openwisp-utils#716

Description of Changes

Adds edited and ready_for_review pull request events so the shared workflow promptly revalidates changed descriptions. Makes the concurrency key PR-specific so newer events cancel outdated validation runs.

Screenshot

N/A. This is a GitHub Actions workflow-only change.

@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: cda22762-65a6-456b-971a-d3313405a0a2

📥 Commits

Reviewing files that changed from the base of the PR and between e079d31 and 4a3c579.

📒 Files selected for processing (1)
  • .github/workflows/bot-autoassign-pr-issue-link.yml
📜 Recent review details
⏰ Context from checks skipped due to timeout. (1)
  • GitHub Check: Kilo Code Review
🧰 Additional context used
🪛 zizmor (1.28.0)
.github/workflows/bot-autoassign-pr-issue-link.yml

[error] 7-7: overly broad permissions (excessive-permissions): issues: write is overly broad at the workflow level

(excessive-permissions)


[warning] 7-7: permissions without explanatory comments (undocumented-permissions): needs an explanatory comment

(undocumented-permissions)

🔇 Additional comments (1)
.github/workflows/bot-autoassign-pr-issue-link.yml (1)

4-10: LGTM!


📝 Walkthrough

Walkthrough

The pull request workflow now triggers for edited and ready_for_review events in addition to opened, reopened, and closed. Its concurrency group no longer includes the event action, so runs are grouped by repository and pull request number. Permissions and downstream job wiring are unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 8
✅ Passed checks (8 passed)
Check name Status Explanation
Title check ✅ Passed The title is descriptive, uses the required [ci] prefix, and matches the workflow-only change.
Description check ✅ Passed The description matches the template and covers checklist, changes, and screenshot, with only the issue reference using a PR link instead of Closes #.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Bug Fixes ✅ Passed Workflow-only GitHub Actions change; regression tests are impractical and no core user-facing bug fix is involved.
Features ✅ Passed Not a feature request: only a GitHub Actions workflow changed; no app/docs/UI/tests/screenshot requirements apply.
Changes ✅ Passed Workflow-only change updates trigger types and concurrency; no docs/UI/public API impacted, and no local test path exists.
General Rules ✅ Passed Workflow-only change is focused, has no obvious security/performance issues, and N/A items (tests/docs/manual path) are appropriately absent.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch ci/update-pr-validation-workflow

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant