Org-wide defaults for the qnophq GitHub
organization. GitHub loads files from this repository automatically for every
repository under qnophq/* that does not provide its own override.
| Path | Purpose |
|---|---|
default.json |
Renovate config consumed via extends: ["github>qnophq/.github"]. |
.github/workflows/renovate.yml |
Reusable Renovate trigger; consumer repos call it via uses: with their own schedule + permissions. |
.github/workflows/renovate-config-validator.yml |
Validates default.json on every push and PR. |
.github/ISSUE_TEMPLATE/ |
Default issue forms (bug report, feature request) + config.yml (issue chooser, contact links). |
.github/PULL_REQUEST_TEMPLATE.md |
Default pull-request template. |
.github/CODE_OF_CONDUCT.md |
Contributor Covenant 2.1; enforcement contact info@devtank42.de. |
.github/SECURITY.md |
Security policy and private vulnerability-reporting channels. |
This repository is public so that Renovate can resolve the
github>qnophq/.github preset using each consumer repo's own
repository-scoped GITHUB_TOKEN — no PAT or GitHub App is required, and so
that GitHub applies the default community health files (issue / PR templates)
to every repo in the org, including private ones such as qnophq/qnop. The
file contains no secrets.
A file in a specific repo's .github/ directory always overrides the
corresponding file here. A repo that ships its own .github/ISSUE_TEMPLATE/ or
PULL_REQUEST_TEMPLATE.md uses those instead of these defaults. For Renovate,
per-repo renovate.json files extend github>qnophq/.github and add their own
packageRules for project-specific stacks (e.g. the Java/Gradle and frontend
groupings live in qnophq/qnop/.github/renovate.json, not here).
qnophq runs its own Renovate via GitHub Actions (renovatebot/github-action),
not the Mend-hosted GitHub App. The renovatebot/github-action SHA pin and run
conventions live once in this repo's reusable workflow; consumer repos add a
short stub. Minimal stub for a consumer repo's .github/workflows/renovate.yml:
name: Renovate
on:
schedule:
- cron: "0 4 * * 1-5"
workflow_dispatch:
inputs:
logLevel:
description: "Log level"
type: choice
default: info
options: [info, debug]
jobs:
renovate:
uses: qnophq/.github/.github/workflows/renovate.yml@main
permissions:
contents: write
pull-requests: write
issues: write
with:
logLevel: ${{ inputs.logLevel || 'info' }}Each caller's GITHUB_TOKEN is scoped to its own repo, so the call is
single-repo by design — the reusable workflow adds no cross-repo write access.
Changes to default.json affect every repo in the org. Treat them as
cross-cutting and let the renovate-config-validator workflow validate the
config before merging.