- Dockerfile 100%
| .claude | ||
| .forgejo/workflows | ||
| doc | ||
| mod-nag | ||
| AGENTS.md | ||
| README.md | ||
workflows
This repository contains reusable Forgejo Actions workflows and the runner image definitions that support them. Downstream repositories reference these workflows with workflow_call instead of carrying local copies.
Available Workflows
| Workflow | Purpose | Guide |
|---|---|---|
mod-nag |
Annoying-by-design Go module vulnerability, deprecation, retraction, and update scanning. | mod-nag/README.md |
Repository Layout
.forgejo/workflows/contains reusable workflow definitions and example caller workflows.mod-nag/contains themod-nagrunner image, banner, and user/admin guide.doc/contains repository-level documentation assets.
Using a Workflow
Copy the caller workflow for the module you want into the consuming repository's .forgejo/workflows/ directory, then adjust only the documented inputs. Reusable workflows are referenced from this repository, for example:
jobs:
mod-nag:
uses: ius/workflows/.forgejo/workflows/mod-nag.yaml@master
Use a full URL when calling workflows across Forgejo instances. See the module guide for runner labels, branch inputs, and permissions.
Maintaining Workflows
Keep workflow-specific user and admin documentation in the matching module folder. Update this README when adding or removing a workflow from the repository catalog.
Use .yaml for workflow files, keep reusable workflow names stable, and document any required runner label or image change with the module that needs it.
License
Internal tooling — see your organisation's policies.