From b257da3a6700b9ff9a2d10e190c50cfb7dd6cc47 Mon Sep 17 00:00:00 2001 From: Rick Staa Date: Wed, 20 May 2026 14:44:53 +0200 Subject: [PATCH] fix: keep retroactive grant notice inside the alert block The `> [!IMPORTANT]` callout in the bug and feature issue templates broke after line two because subsequent lines weren't prefixed with `>`, so the body of the notice rendered as plain text outside the alert. Prefix every line (including blanks) with `>` so the full notice stays inside the callout. Co-Authored-By: Claude Opus 4.7 (1M context) --- .github/ISSUE_TEMPLATE/bug-report.yml | 30 +++++++++++----------- .github/ISSUE_TEMPLATE/feature-request.yml | 30 +++++++++++----------- 2 files changed, 30 insertions(+), 30 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml index e90d4a94..0c26e544 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ b/.github/ISSUE_TEMPLATE/bug-report.yml @@ -115,19 +115,19 @@ body: > [!IMPORTANT] > Compensation cap: **[FILL IN AMOUNT]** - - Before picking this up, read the [Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. Key points: - - - **Not pay-for-delivery.** Compensation is based on demonstrated adoption and community impact — not on shipping. Real, named community contributors must use your work and publicly attest to it. Building in isolation, then asking for a grant, does not qualify. - - **Talk to the community first.** A public discussion (Discord or Forum) about the problem must precede the work, and evidence of it must be part of your application. No prior discussion, no tempcheck, no public signal = won't pass review. - - **Required steps before investing more time:** - 1. Read the [original Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. - 2. Start a public discussion (Discord or Forum). Get input. Confirm direction. - 3. Secure at least one community proof point — a Discord thread with positive signal, a Review Team acknowledgement, or evidence of active adoption. - 4. Identify, by name, who has this problem. - 5. Build, ship, and confirm it's actually being used. - 6. Apply with at least one named community contributor willing to publicly attest to your work's impact on the forum post. - - Skipping steps 2, 3, 4, or 6 will halt the application. Reach out to **jj.a.ss.o.nn_everestnode** on Discord before you start building. + > + > Before picking this up, read the [Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. Key points: + > + > - **Not pay-for-delivery.** Compensation is based on demonstrated adoption and community impact — not on shipping. Real, named community contributors must use your work and publicly attest to it. Building in isolation, then asking for a grant, does not qualify. + > - **Talk to the community first.** A public discussion (Discord or Forum) about the problem must precede the work, and evidence of it must be part of your application. No prior discussion, no tempcheck, no public signal = won't pass review. + > + > **Required steps before investing more time:** + > 1. Read the [original Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. + > 2. Start a public discussion (Discord or Forum). Get input. Confirm direction. + > 3. Secure at least one community proof point — a Discord thread with positive signal, a Review Team acknowledgement, or evidence of active adoption. + > 4. Identify, by name, who has this problem. + > 5. Build, ship, and confirm it's actually being used. + > 6. Apply with at least one named community contributor willing to publicly attest to your work's impact on the forum post. + > + > Skipping steps 2, 3, 4, or 6 will halt the application. Reach out to **jj.a.ss.o.nn_everestnode** on Discord before you start building. --> diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml index 783e7a2d..1614b996 100644 --- a/.github/ISSUE_TEMPLATE/feature-request.yml +++ b/.github/ISSUE_TEMPLATE/feature-request.yml @@ -46,21 +46,21 @@ body: > [!IMPORTANT] > Compensation cap: **[FILL IN AMOUNT]** - - Before picking this up, read the [Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. Key points: - - - **Not pay-for-delivery.** Compensation is based on demonstrated adoption and community impact — not on shipping. Real, named community contributors must use your work and publicly attest to it. Building in isolation, then asking for a grant, does not qualify. - - **Talk to the community first.** A public discussion (Discord or Forum) about the problem must precede the work, and evidence of it must be part of your application. No prior discussion, no tempcheck, no public signal = won't pass review. - - **Required steps before investing more time:** - 1. Read the [original Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. - 2. Start a public discussion (Discord or Forum). Get input. Confirm direction. - 3. Secure at least one community proof point — a Discord thread with positive signal, a Review Team acknowledgement, or evidence of active adoption. - 4. Identify, by name, who has this problem. - 5. Build, ship, and confirm it's actually being used. - 6. Apply with at least one named community contributor willing to publicly attest to your work's impact on the forum post. - - Skipping steps 2, 3, 4, or 6 will halt the application. Reach out to **jj.a.ss.o.nn_everestnode** on Discord before you start building. + > + > Before picking this up, read the [Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. Key points: + > + > - **Not pay-for-delivery.** Compensation is based on demonstrated adoption and community impact — not on shipping. Real, named community contributors must use your work and publicly attest to it. Building in isolation, then asking for a grant, does not qualify. + > - **Talk to the community first.** A public discussion (Discord or Forum) about the problem must precede the work, and evidence of it must be part of your application. No prior discussion, no tempcheck, no public signal = won't pass review. + > + > **Required steps before investing more time:** + > 1. Read the [original Retroactive Grants post](https://forum.livepeer.org/t/about-the-retroactive-grant-applications-category/3250/2?u=mehrdad) in full. + > 2. Start a public discussion (Discord or Forum). Get input. Confirm direction. + > 3. Secure at least one community proof point — a Discord thread with positive signal, a Review Team acknowledgement, or evidence of active adoption. + > 4. Identify, by name, who has this problem. + > 5. Build, ship, and confirm it's actually being used. + > 6. Apply with at least one named community contributor willing to publicly attest to your work's impact on the forum post. + > + > Skipping steps 2, 3, 4, or 6 will halt the application. Reach out to **jj.a.ss.o.nn_everestnode** on Discord before you start building. --> - type: markdown