Skip to content

chore: add issues on parity report failures#6700

Merged
LesnyRumcajs merged 1 commit intomainfrom
add-issues-on-parity-report-failures
Mar 6, 2026
Merged

chore: add issues on parity report failures#6700
LesnyRumcajs merged 1 commit intomainfrom
add-issues-on-parity-report-failures

Conversation

@LesnyRumcajs
Copy link
Copy Markdown
Member

@LesnyRumcajs LesnyRumcajs commented Mar 6, 2026

Summary of changes

Changes introduced in this pull request:

The last one failed and we didn't get a notification. https://github.com/ChainSafe/forest/actions/workflows/rpc-parity-report.yml

Reference issue to close (if applicable)

Closes

Other information and links

Change checklist

  • I have performed a self-review of my own code,
  • I have made corresponding changes to the documentation. All new code adheres to the team's documentation standards,
  • I have added tests that prove my fix is effective or that my feature works (if possible),
  • I have made sure the CHANGELOG is up-to-date. All user-facing changes should be reflected in this document.

Outside contributions

  • I have read and agree to the CONTRIBUTING document.
  • I have read and agree to the AI Policy document. I understand that failure to comply with the guidelines will lead to rejection of the pull request.

Summary by CodeRabbit

  • Chores
    • Automated GitHub issue creation now enabled for RPC parity test failures on the main branch
    • Added issue template with instructions to access workflow logs and diagnostic information

@LesnyRumcajs LesnyRumcajs requested a review from a team as a code owner March 6, 2026 08:55
@LesnyRumcajs LesnyRumcajs requested review from hanabi1224 and sudo-shashank and removed request for a team March 6, 2026 08:55
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Mar 6, 2026

Walkthrough

Adds a GitHub issue template for RPC parity report failures and extends the rpc-parity-report workflow to construct a workflow URL and automatically create GitHub issues when failures occur on the main branch.

Changes

Cohort / File(s) Summary
GitHub Issue Template
.github/RPC_PARITY_REPORT_ISSUE_TEMPLATE.md
New issue template file with front matter specifying dynamic title with date placeholder and label, followed by Description section directing users to check logs via workflow URL.
Workflow Configuration
.github/workflows/rpc-parity-report.yml
Added two new steps: one to set and persist WORKFLOW_URL environment variable from GitHub context, and another to automatically create a GitHub issue on main-branch failures using the new template.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • hanabi1224
  • sudo-shashank
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: adding automatic issue creation when the RPC parity report workflow fails.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch add-issues-on-parity-report-failures

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

@LesnyRumcajs LesnyRumcajs enabled auto-merge March 6, 2026 08:56
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/rpc-parity-report.yml:
- Around line 53-58: Add an explicit job-level permission block granting write
access to issues by adding permissions: issues: write to the job that calls
JasonEtco/create-an-issue@v2 so the GITHUB_TOKEN can create issues even when
default workflow permissions are read-only; also verify that the label
referenced in .github/RPC_PARITY_REPORT_ISSUE_TEMPLATE.md (e.g., "Bug") exists
in the repo or create it to prevent issue-creation failures.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 2634077f-6478-4a8b-a602-1a43cc40e789

📥 Commits

Reviewing files that changed from the base of the PR and between b0bfaaa and a1851d1.

📒 Files selected for processing (2)
  • .github/RPC_PARITY_REPORT_ISSUE_TEMPLATE.md
  • .github/workflows/rpc-parity-report.yml

Comment thread .github/workflows/rpc-parity-report.yml
@LesnyRumcajs LesnyRumcajs added this pull request to the merge queue Mar 6, 2026
Merged via the queue into main with commit e84603e Mar 6, 2026
44 checks passed
@LesnyRumcajs LesnyRumcajs deleted the add-issues-on-parity-report-failures branch March 6, 2026 09:51
@coderabbitai coderabbitai Bot mentioned this pull request Apr 1, 2026
6 tasks
@coderabbitai coderabbitai Bot mentioned this pull request Apr 15, 2026
6 tasks
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.

2 participants