.github

Organisation-level configuration for Lavder Enterprise. There is no product in here.

What is in it

Path	Effect
profile/README.md	The public landing page shown at github.com/Lavder-Enterprise, above the repository list. Rendered only while this repository is public.
profile/assets/	Images used by that page. Referenced with paths relative to profile/.
SECURITY.md	Default vulnerability disclosure policy.
CONTRIBUTING.md	Default contribution guide.
CODE_OF_CONDUCT.md	Default code of conduct.
SUPPORT.md	Default "where do I take this question" page.
.github/ISSUE_TEMPLATE/	Default issue templates and the chooser configuration.
.github/PULL_REQUEST_TEMPLATE.md	Default pull request template.
templates/issue-forms/	Not inherited. Opt-in copies, see below.

How the defaults work

Every repository in the organisation that does not contain its own copy of one of these files inherits the one here. A repository that does contain its own copy overrides it, file by file — it is not all or nothing.

Three things this cannot do:

• LICENSE is not inheritable. It has to live in each repository, so that it travels with a clone, a package or a download.
• The profile page needs this repository to stay public. Making it private removes the organisation landing page.
• YAML issue forms are not inherited. Only classic Markdown issue templates are. Tested here on 2026-07-27: with bug_report.yml in .github/ISSUE_TEMPLATE/, repositories inheriting from this one reported no issue templates at all; the same content as bug_report.md was picked up immediately, by public and private repositories alike. The forms therefore live in templates/issue-forms/ — copy them into an individual repository's own .github/ISSUE_TEMPLATE/ when you want the richer form UI there, and note that doing so overrides the defaults here for that repository.

Changing something

Edit it here and the change applies across the organisation on the next page load. There is no build step and nothing to publish.