Repository navigation
docs: add org community-health files pointing at rossoctl/rossoctl - #129
Merged
Merged
Conversation
✅ Deploy Preview for animated-crumble-fb8862 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
GitHub serves community-health files from a `.github` repository to every
repo in the org that does not define its own -- but only for a specific
set of filenames, and only from a repo literally named `.github`. This
repo had the issue templates and PR template but none of the four
documents, so nothing was being inherited: `community/profile` reported
`code_of_conduct: null` and `security: null` for rossoctl/moca.
Adds the four as pointers, not copies, so rossoctl/rossoctl stays the
single source of truth and these cannot drift from it:
CODE_OF_CONDUCT.md -> org policy + where conduct reports go
SECURITY.md -> org policy, plus the do-not-open-an-issue
summary and the 48h/7d expectations inline
CONTRIBUTING.md -> org process + an index of all nine project
documents
SUPPORT.md -> where to ask what, and the licensing note
Two deviations from a pure pointer, both deliberate:
SECURITY.md tells a reporter to file the advisory against the repository
where they found the issue, rather than reproducing the org file's link
to rossoctl/rossoctl's advisory form. A vulnerability in moca should not
be reported against a different repo.
SUPPORT.md states that each repo carries its own LICENSE and asks
readers to report any repo missing one. A LICENSE in this repo would
NOT be inherited -- verified: moca, cortex and examples each have their
own real Apache-2.0 file -- so adding one here would imply an
inheritance that does not exist.
Root markdown is outside both the Docusaurus build (which sources docs/
and src/pages) and the link checker (which crawls the deployed site), so
these files do not affect the website. Links verified with lychee: 23 OK,
0 errors.
Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com>
Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
mrsabath
force-pushed
the
docs/org-community-health-pointers
branch
from
October 9, 2026 18:53
eccc3d5 to
7083e84
Compare
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
2 participants
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
GitHub serves community-health files from a
.githubrepository to every repo in the org that does not define its own. This repo had the issue templates and PR template, but none of the four documents — so nothing was being inherited.Verified before writing anything:
Adds the four as pointers, not copies, so
rossoctl/rossoctlstays the single source of truth and these cannot drift from it:CODE_OF_CONDUCT.mdSECURITY.mdCONTRIBUTING.mdSUPPORT.mdTwo deliberate deviations from a pure pointer
SECURITY.mdsends reporters to the repo they found the bug in, rather than reproducing the org file's hardcoded link to therossoctl/rossoctladvisory form. A vulnerability inmocashould not be reported against a different repository.SUPPORT.mdstates each repo carries its ownLICENSE. ALICENSEhere would not be inherited — verified:moca,cortexandexampleseach have their own real Apache-2.0 file. Adding one to this repo would imply an inheritance that does not exist.Website impact: none
Root markdown is outside both the Docusaurus build (which sources
docs/andsrc/pages) and the link checker (which crawls the deployed site URL, not repo files). The existingscripts/sync-docs.shbehaviour is untouched.Verification
mailto:address.rossoctl/repo-templatewas made public — it had 404'd while private, which would otherwise have shipped a broken link in a public file.Related
Pairs with
rossoctl/repo-template, which ships theLICENSEandCODEOWNERSthat GitHub cannot inherit.