Expand README with how to use some tools offline to maintain this repo
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 4
- Forks
- 10
- Avg merge
- 8h 5m
- Merged PRs (30d)
- 1
Description
We don't want to add more tools to this repo, as explained in the README under "This repository is minimal on purpose, for security reasons it contains only what is absolutely necessary. [...]". That includes no dependabot, no CodeQL, no zizmor, etc.
It'd be useful to expand a bit on that on how to use tools async (or possibly from another repo on a cron job) to perform regular maintenance and scanning for this repo. E.g.:
gha-updateor similar to bump all pins of actions (or is there a newer tool for that now?)zizmorto scan for common issues in workflow files- probably a custom script or an AI tool to go through the repo to check for anything else that isn't pinned
- anything else?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README section explaining that the repository is minimal, then inspect the workflow files. Research offline or external-repository approaches using gha-update, zizmor, and comparable tools, and document practical maintenance and scanning steps. Done means the README clearly explains how to run these checks without adding tools to this repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100