knadh

knadh / approve-pr-creation-from-issue

Public

A GitHub Action that forces potential contributors to receive an explicit approval from an Issue discussion before they can raise a PR.

11
0
100% credibility
Found Feb 20, 2026 at 10 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
JavaScript
AI Summary

A GitHub Action that automatically closes pull requests lacking a reference to a maintainer approval comment in a related issue discussion.

How It Works

1
🛡️ Discover the guard

You find a handy tool to protect your online project from unwanted change suggestions by requiring prior approval.

2
📋 Grab setup guide

Visit the tool's page and copy the simple instructions to get started.

3
⚙️ Turn on protection

Paste the instructions into your project's settings area and save – now it's active!

4
💬 Idea discussion starts

Someone opens a chat thread in your project to propose their helpful change.

5
👍 Give your okay

After reviewing the idea, you add a welcoming comment to approve them moving forward.

6
🔗 Link the approval

The person submits their change suggestion, including a direct pointer to your approval comment.

✅ All clear!

The tool checks everything, confirms the approval, and lets the good suggestion stay open.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 10 to 11 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is approve-pr-creation-from-issue?

This JavaScript GitHub Action enforces a pre-PR approval gate: contributors must open an issue, get a maintainer comment like `/pr-welcome @user`, then paste the comment URL into their PR body using `/pr-clearance {url}`. Without a valid reference, the PR auto-closes with a custom message. It cuts unsolicited PR spam in busy github repos, using github_token for API checks and github actions permissions like pull-requests: write.

Why is it gaining traction?

Unlike basic branch protections, it mandates issue discussions first, skipping checks for past contributors or small diffs via min_diff_files/lines. Drop it into pull_request workflows on ubuntu-latest runners, tweak strings and github actions environment variables, no need for github action matrix or cache setups. Devs dig the lightweight control over github actions marketplace contributions without github actions pricing hikes from junk traffic.

Who should use this?

Repo maintainers of mid-sized open-source github repos drowning in low-effort PRs from github copilot chat users. Solo devs or small teams enforcing quality via github actions variables and github_personal_access_token, especially alongside github desktop or github pages projects wanting fewer github script hacks.

Verdict

At 10 stars and 1.0% credibility, it's immature with no tests visible, but crisp docs and configurable inputs make it a low-risk experiment. Try it if spam PRs clog your github_workspace; skip for high-traffic repos needing battle-tested alternatives.

(198 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.