This issue is blocked until we have the org-level .github repo.
After #3, we should delete community health files from individual repos that don't require differences from the shared versions.
📣 Discussion Topic: 📣 The above is pretty clear for magic GitHub files like issue and PR templates, but non-magical files like CONTRIBUTING and CODE_OF_CONDUCT can also be inherited. This is nice since they inevitably are full of identical boilerplate that are a pain to keep up-to-date across repos, but also means the files won't appear in the individual repo file browsers or be included in repo downloads/clones. The introduction blog post says:
While the file itself won’t appear in the file browser or Git history for each repository, it will be surfaced throughout developers’ workflows, such as when opening a new issue or when viewing the Community Profile, just as if it were committed to the repository directly.
slifty
commented
4 years ago 
This issue is blocked until we have the org-level
.githubrepo.After #3, we should delete community health files from individual repos that don't require differences from the shared versions.
📣 Discussion Topic: 📣 The above is pretty clear for magic GitHub files like issue and PR templates, but non-magical files like CONTRIBUTING and CODE_OF_CONDUCT can also be inherited. This is nice since they inevitably are full of identical boilerplate that are a pain to keep up-to-date across repos, but also means the files won't appear in the individual repo file browsers or be included in repo downloads/clones. The introduction blog post says:
Is it sufficient that those sort of things show up only in the not entirely discoverable Community section?