Org-wide defaults for the FactoryGameFan organization.
The security policy GitHub shows on every repo in the org that has no SECURITY.md of its own.
It sends reporters to GitHub's private vulnerability reporting, which must be switched on in each
repo for the Report a vulnerability button to appear. The org's code security configuration
turns it on.
The shared Renovate preset. Every repo in the org that has dependencies pulls it in with:
{
"extends": ["local>FactoryGameFan/.github:renovate-config"]
}It holds the settings that are the same everywhere: the timezone, the weekly batch from noon
Sunday to noon Monday, automerge: false, the PR rate caps, the rule that security fixes skip
the weekly window, and the GitHub Actions grouping.
It deliberately does not hold release-age floors, lockfile maintenance, or package holds.
Those differ per repo and their reasoning is written next to them in each repo's own config.
FactorioMapWebUI and FactorioTools set opposite values for lockFileMaintenance, and both
are correct for their repo.
- Validate with
npx --package renovate -- renovate-config-validator renovate-config.json. Run it from outside a project root; a barenpxinside one can fail withEBADDEVENGINES. - A repo running with the app's "Require config file" setting does nothing, silently, if its config fails to resolve. A broken preset here reads as "no updates available", not as an error.
- This repo must stay ticked in the Renovate app installation, or no repo can read the preset.
| Repo | Managers |
|---|---|
FactorioMapWebUI |
pnpm, cargo, github-actions |
FactorioTools |
npm, github-actions |
factorio-blueprint-editor |
npm, cargo, github-actions |
factorio-oracle |
cargo, github-actions |
factorygamefan |
npm |
FactorioWikiDamageThresholds and the archived Factorio-Blueprints have no dependency
manifests, so Renovate has nothing to do in them.