Organisation-wide defaults for the cloudops GitHub organisation.
GitHub applies the files in this repository to every repository in the organisation that does not have its own copy of that file. An edit here changes behaviour across the whole organisation at once, so treat changes accordingly.
Important
This repository must stay public. GitHub ignores private .github repositories, and every default below silently stops applying.
| Path | What it does |
|---|---|
PULL_REQUEST_TEMPLATE.md |
The default pull request description, used by any repository without its own template. |
SECURITY.md |
How to report a security vulnerability. Rendered in the Security tab of any repository without its own policy. |
profile/README.md |
The public organisation profile rendered at github.com/cloudops. |
- A default applies only where the repository has no file of that type. Add your own and yours wins.
- Defaults are rendered by GitHub rather than copied. They do not appear in the consuming repository's file tree, history, clones, packages, or downloads.
- Issue templates must live in
.github/ISSUE_TEMPLATE/. Every other supported file can sit at the root, in.github/, or indocs/. - If a repository has anything of its own in
.github/ISSUE_TEMPLATE/, none of the defaults here are used for that repository.
GitHub supports these as organisation-wide defaults and we do not use them yet:
CODE_OF_CONDUCT.md, CONTRIBUTING.md, SUPPORT.md, GOVERNANCE.md, FUNDING.yml, issue templates, and discussion category forms.
Only the file types on GitHub's supported list are shared. This is not a mechanism for distributing configuration or automation:
- Dependabot – a
dependabot.ymlhere configures this repository alone. It was added and then removed for that reason (see commit9ef41da). Add adependabot.ymlto each repository that needs one. - GitHub Actions – workflows are not inherited. Publish them as reusable workflows and call them from each repository.