[ci] Added CI failure bot

[stktyagi]

Added caller workflow for CI failure bot

Checklist

• I have read the OpenWISP Contributing Guidelines.
• I have manually tested the changes proposed in this pull request.
• I have written new test cases for new code and/or updated existing tests for changes to existing code.
• I have updated the documentation.

Description of Changes

Added CI failure bot caller workflow

[coderabbitai]

Warning

Rate limit exceeded

@stktyagi has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 26 minutes and 52 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 44723f1e-9719-436b-9f88-2a0a7b01497c

📥 Commits

Reviewing files that changed from the base of the PR and between dd4bf4c and 5cade23.

📒 Files selected for processing (1)

• .github/workflows/bot-ci-failure.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/add-ci-failure-bot

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The CI failure bot workflow is well-structured and follows GitHub Actions best practices:

• ✅ Appropriate minimal permissions at workflow and job levels
• ✅ Proper concurrency configuration to prevent duplicate runs
• ✅ Multiple fallback strategies for PR detection (payload → API → scan)
• ✅ Secrets correctly passed to reusable workflow
• ✅ Variables sourced from trusted GitHub event context (not user input)
• ✅ Graceful error handling when PR cannot be found

Files Reviewed (1 file)

• .github/workflows/bot-ci-failure.yml - New workflow that triggers on CI build failures, finds the associated PR, and calls the reusable CI failure bot from openwisp-utils

---

_{Reviewed by kimi-k2.5-0127 · 76,959 tokens}

[nemesifier]

Verified against the documented spec in openwisp-utils (reusable-github-utils.rst, Automated CI Failure Bot section). LGTM.