Conversation
Initial bundle for the plugwerk/.github org-config repo: - AGPL-3.0 LICENSE (matches plugwerk/plugwerk) - Repo-internal README explaining layout and override behavior - Renovate default.json — cross-cutting rules only (config:recommended, pinGitHubActionDigests, GitHub Actions/Dockerfile/npm grouping, npm major split, npm pin rangeStrategy). Java/Kotlin/Spring rules stay in plugwerk/plugwerk's per-repo override. - Renovate config validator workflow — runs npx renovate-config-validator --strict on default.json for every push and PR - SECURITY.md — real policy (private advisories primary, info@devtank42.de fallback), supported versions, best-effort SLA, AGPL-3.0 disclosure note - CODE_OF_CONDUCT.md — Contributor Covenant 2.1 with org contact email - CONTRIBUTING.md — generic org guide, defers to per-repo AGENTS.md / CLAUDE.md for project specifics, includes CLA reference - SUPPORT.md — discussions vs. issues guidance, no OSS support SLA - FUNDING.yml — empty (commented examples for future activation) - profile/README.md — public org landing page (Plugwerk overview, Phase 2 status, repo list, AGPL-3.0 + commercial) - ISSUE_TEMPLATE/ — structured YAML forms (bug, feature, config) with blank_issues_enabled: false and contact links to Discussions / Security Policy / commercial inquiries - PULL_REQUEST_TEMPLATE.md — generic version (no project-specific Liquibase rollback line; that override stays in plugwerk/plugwerk) Closes plugwerk/plugwerk#398
The 'Phase 2, alpha' framing is more appropriate per-repo (where the actual maturity differs) than on the org landing page.
This was referenced May 9, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bootstraps the new
plugwerk/.githuborg-config repo with the full set of org-wide defaults: Renovate config, community-health files, profile README, issue forms, PR template, and a Renovate-config validator workflow.Plans the org out of GitHub-default-placeholder territory: every repo in the org currently inherits an empty SECURITY.md, no community standards, and (for
examplesandwebsite) Renovate defaults rather than the considered config that lives inplugwerk/plugwerk/.github/renovate.json.Closes
What's in this PR
LICENSEplugwerk/plugwerkREADME.mddefault.json.github/workflows/renovate-config-validator.ymldefault.jsonon push/PR.github/SECURITY.md.github/CODE_OF_CONDUCT.md.github/CONTRIBUTING.mdAGENTS.md.github/SUPPORT.md.github/FUNDING.yml.github/PULL_REQUEST_TEMPLATE.md.github/ISSUE_TEMPLATE/{bug_report,feature_request,config}.ymlprofile/README.mdRenovate config split — what's here vs. what stays in plugwerk
The split keeps
examplesandwebsitefrom being polluted with Java/Kotlin/Spring rules they cannot use, while still giving them sensible cross-cutting defaults out of the box.Here in
default.json(cross-cutting):config:recommended+helpers:pinGitHubActionDigestsbefore 6am every weekday,Europe/Berlin)chore, concurrency limitsStays in
plugwerk/plugwerk/.github/renovate.json(per-repo override, follow-up PR):org.springframework.boot/security,io.spring.dependency-management)org.jetbrains.kotlin)tools.jackson+com.fasterxml.jackson)eclipse-temurinJava 21.x version pinThe follow-up PR in
plugwerk/plugwerkshrinksrenovate.jsontoextends: ["github>plugwerk/.github"]plus the Java-specificpackageRulesonly, and deletes the stale GitHub-default-placeholderSECURITY.md.Verification after merge
plugwerk/examplesandplugwerk/website; under "Detected dependencies" the resolved config should now include the rules from thisdefault.json. May take up to one Renovate run cycle (cron is 04:00 UTC weekdays).https://github.com/plugwerk/<any-repo>/communityshould show all checks green for the org-wide files.Follow-ups (separate PRs)
plugwerk/plugwerk: shrinkrenovate.jsonto inherit + override; delete staleSECURITY.md.Risks
examplesandwebsite: the new defaults add concurrency limits, pinning, and grouping these repos do not have today. Existing open Renovate PRs may be re-created with new branch names. Mitigation: review and merge or close the small set of currently-open Renovate PRs in those repos before merging this PR.plugwerk/.githubfor theextendsresolution to work everywhere; this is the case if the install is org-wide rather than per-repo whitelisted.AI Agent Disclosure