scoopinstaller/githubactions — explained in plain English
Analysis updated 2026-07-25 · repo last pushed 2026-05-21
Automatically detect new app versions and submit updates to your Scoop bucket.
Auto-fix broken download links and hash mismatches reported by users without manual intervention.
Validate incoming pull requests to ensure app files are correct JSON with required fields and working hashes.
Organize and deduplicate user bug reports to keep your issue queue manageable.
| scoopinstaller/githubactions | gmyxds/claude-desktop-zh-simple | refrainwww/codex-windows-computer-use | |
|---|---|---|---|
| Stars | 33 | 31 | 31 |
| Language | PowerShell | PowerShell | PowerShell |
| Last pushed | 2026-05-21 | — | — |
| Maintenance | Maintained | — | — |
| Setup difficulty | moderate | — | moderate |
| Complexity | 3/5 | — | 3/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires an existing Scoop bucket repository and familiarity with GitHub Actions workflow configuration.
Scoop is a popular command-line tool for Windows that lets people install software from curated lists called "buckets." Each bucket is essentially a repository full of small files describing where to download a given app, what version is current, and how to verify the download hasn't been tampered with. Running one of these buckets manually gets tedious fast, app versions change, download links break, and file hashes need updating. This project, GithubActions for Scoop buckets, automates that maintenance work so bucket maintainers can focus on bigger decisions instead of chasing routine fixes. The project provides a handful of automated actions that run on GitHub's servers. One action, called Excavator, periodically checks every app in the bucket for new versions and submits updates on its own. Another handles incoming bug reports from users. For example, if someone reports a broken download link, the action tries downloading the file itself and posts a comment on the issue with the results. If a user reports a hash mismatch, which happens when the downloaded file doesn't match the expected signature, the action can verify the problem, check whether someone already submitted a fix, and if not, automatically create a new pull request with the corrected hashes. It even labels and deduplicates issues to keep the queue organized. On the pull request side, whenever someone submits a change or types /verify in a comment, the action runs a series of validation checks. It confirms the app file is valid JSON, makes sure required fields like the license and description are present, verifies that download hashes are correct, and tests whether the auto-update mechanism works. If anything fails, the maintainer sees the results immediately. This project is aimed squarely at people who maintain Scoop buckets. If you run a bucket with dozens or hundreds of apps, these actions save you from manually testing every submission and writing the same fixes over and over. It trades a bit of setup complexity for a large ongoing reduction in repetitive work.
Automated GitHub Actions that maintain Scoop buckets for Windows by checking for new app versions, fixing broken downloads, updating file hashes, and validating user-submitted changes.
Mainly PowerShell. The stack also includes PowerShell, GitHub Actions.
Maintained — commit in last 6 months (last push 2026-05-21).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.