fix: keep retroactive grant notice inside the alert block

[rickstaa]

Summary

• The > [!IMPORTANT] callout in bug-report.yml and feature-request.yml only wrapped the first two lines; blank lines closed the blockquote and the rest of the notice rendered as plain text.
• Prefix every line of the notice (including blank separators) with > so the entire retroactive-grant block stays inside the alert.

Test plan

• Open a draft issue with each template, uncomment the notice, and confirm the full block renders as a single GitHub IMPORTANT callout.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated GitHub issue templates with improved markdown formatting in contribution notices to enhance readability and presentation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
explorer-arbitrum-one	Ready	Preview, Comment	May 20, 2026 12:47pm

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2e8bdb6d-96bd-480d-85a4-f0f12ba22959

📥 Commits

Reviewing files that changed from the base of the PR and between f511594 and b257da3.

📒 Files selected for processing (2)

• .github/ISSUE_TEMPLATE/bug-report.yml
• .github/ISSUE_TEMPLATE/feature-request.yml

---

📝 Walkthrough

Walkthrough

GitHub issue templates for bug reports and feature requests have their "Retroactive Grant Notice" sections reformatted into block-quoted markdown, converting plain paragraphs and lists to lines prefixed with > characters while preserving all content.

Changes

Issue Template Notice Formatting

Layer / File(s)	Summary
Retroactive Grant Notice block-quote formatting .github/ISSUE_TEMPLATE/bug-report.yml, .github/ISSUE_TEMPLATE/feature-request.yml	Both issue templates reformat the Retroactive Grant Notice from plain markdown paragraphs and bullet lists into block-quoted style using > prefixes. Content and meaning remain unchanged; only markdown formatting is altered.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• livepeer/explorer#669: Introduces the "Retroactive Grant Notice" block itself in both issue templates, which this PR reformats into block-quoted markdown style.

Poem

🐰 A notice dressed in blockquote flair,
With > marks dancing through the air,
The content stays, the format gleams,
These templates now look crisp and clean! ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/retroactive-grant-alert-blockquote

---

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.}

[Copilot]

Pull request overview

This PR fixes GitHub issue form rendering so the full “Retroactive Grant Notice” stays within the > [!IMPORTANT] callout by ensuring every line (including blank separators) remains inside the blockquote.

Changes:

• Updated the retroactive grant notice in the feature request template to keep blank lines inside the IMPORTANT blockquote.
• Updated the retroactive grant notice in the bug report template to keep blank lines inside the IMPORTANT blockquote.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
.github/ISSUE_TEMPLATE/feature-request.yml	Ensures the retroactive grant notice renders as a single continuous IMPORTANT callout by blockquoting blank lines too.
.github/ISSUE_TEMPLATE/bug-report.yml	Applies the same blockquote formatting fix so the callout doesn’t break mid-notice.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.