git404hub

what is clanker-blocker fr?

highesttt/clanker-blocker — explained in plain English

Analysis updated 2026-05-18

2GoAudience · ops devopsComplexity · 2/5Setup · easy

tl;dr

A GitHub Action written in Go that blocks or closes issues and pull requests from users on community-curated bot and spam blocklists.

vibe map

mindmap
  root((clanker-blocker))
    What it does
      Blocks spam accounts
      Closes bad issues and PRs
    Tech stack
      Go
      GitHub Actions
      GitHub API
    Use cases
      Daily account blocking
      Auto close submissions
      Custom blocklists
    Audience
      Repo maintainers
      DevOps teams
    Features
      Multiple list formats
      Commit pinning
      Audit trail labels

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Automatically block known bot or spam accounts from opening issues or pull requests.

VIBE 2

Close and label submissions from blocklisted users while leaving a per-repository audit trail.

VIBE 3

Combine multiple community blocklists in table, bullet, or one-per-line formats.

VIBE 4

Pin an external blocklist to a specific commit hash to review changes before they take effect.

what's the stack?

GoGitHub ActionsGitHub API

how it stacks up fr

highesttt/clanker-blockeranomalroil/1keydanterolle/loqi
Stars222
LanguageGoGoGo
Last pushed2019-05-17
MaintenanceDormant
Setup difficultyeasymoderatemoderate
Complexity2/53/52/5
Audienceops devopsops devopsdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 30min

The daily account-block action needs a personal access token with block permissions since the default GitHub token cannot call that API.

License is not stated in the explanation.

in plain english

clanker-blocker is a GitHub Action written in Go that automatically blocks users from interacting with your repositories based on community-curated blocklists. Its default list is a publicly maintained Markdown file tracking known bot and spam accounts. When a listed user tries to open an issue or pull request, the action can either block them at the account level or close their submission immediately with a comment and a label. The project provides two independent actions. The first runs on a daily schedule and calls GitHub's block API to apply account-level blocks for all users on the configured lists, preventing blocked accounts from opening issues, pull requests, or comments across every repository where you have admin rights. This requires a personal access token with block permissions, since the built-in GitHub token cannot call the block API. The second action triggers when a new issue or pull request is opened, checks whether the author appears on any configured list, and if so closes the submission with a comment and optionally applies a label named "blocklisted." This version needs no special token and creates a per-repository audit trail. You can extend beyond the default list by pointing to additional Markdown files. Three parsers handle different formats: a table with usernames in the first column, a bulleted list, or one username per line. The README recommends pinning any external list to a specific commit hash rather than a branch if you want to manually review changes before they take effect, since each sync inherits the list maintainer's judgment about who belongs on it.

prompts (copy fr)

prompt 1
How do I set up clanker-blocker in my repository's GitHub Actions workflow?
prompt 2
Explain the difference between the account-level block action and the close-and-label action in clanker-blocker.
prompt 3
Show me how to add a custom Markdown blocklist file to clanker-blocker.
prompt 4
Help me set up a personal access token with the right permissions for clanker-blocker's daily block action.

Frequently asked questions

what is clanker-blocker fr?

A GitHub Action written in Go that blocks or closes issues and pull requests from users on community-curated bot and spam blocklists.

What language is clanker-blocker written in?

Mainly Go. The stack also includes Go, GitHub Actions, GitHub API.

What license does clanker-blocker use?

License is not stated in the explanation.

How hard is clanker-blocker to set up?

Setup difficulty is rated easy, with roughly 30min to a first successful run.

Who is clanker-blocker for?

Mainly ops devops.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.