Development record
Nothing limits who may make a private lab or ideate verdict public: once a promote path exists, any account able to run it could move private material into the committed research store. A check inside abcd alone cannot hold, because a contributor controls their own machine and can copy the files by hand; the boundary that holds is the forge, where only an account with write access can merge. A contributor's pull request is also public the moment it is opened, before any review, so the forge keeps such material out of the project's record but cannot stop a contributor disclosing it there.
issueopenminoriss-2610290730539347
Nothing limits who may make a private lab or ideate verdict public: once a promote path exists, any account able to run it could move private material into the committed research store. A check inside abcd alone cannot hold, because a contributor controls their own machine and can copy the files by hand; the boundary that holds is the forge, where only an account with write access can merge. A contributor's pull request is also public the moment it is opened, before any review, so the forge keeps such material out of the project's record but cannot stop a contributor disclosing it there.
Grounds
- pursued: we expect write access as the maintainer test to keep promotion in maintainers' hands on any plan; a promotion completed by a Read or Triage account shows it wrong
Frontmatter
| id | iss-2610290730539347 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610290730539347-nothing-limits-who-may-make-a-private.md
open on GitHub ↗ · commit history ↗
References2
- iss-2610170717491755An idea judged private with abcd ideate cannot later be made public: the verb has only record, which writes once to the store chosen, so moving a private verdict into the repository means copying the file by hand, unchecked; and nothing lists a person's ideas with which are private and which public, since where a file sits is the only record of it.blocked by
- itd-2610290858115394A repository's maintainers hold its quality gate: a contributor's change waits for a maintainer's approval, and only a maintainer starts a release, adopts an intent or makes private work publicrelated
mentions3
- iss-2610290755587946abcd ahoy remote apply (itd-2610290746077716) reports a missing or partial CODEOWNERS file as advisory and does not write it. Whether a managed repository keeps a CODEOWNERS file at all is now part of the maintainer-gate record iss-2610290730539347, which is not yet on the default branch. A maintainer is anyone with Write access or above, and GitHub counts approvals only from those, so the approval gate does not depend on CODEOWNERS naming a team. <!-- record-lint: forward-looking -->
- itd-2610290746077716abcd audits and applies a repository's GitHub settings
- spc-2610290749113317abcd audits and applies a repository's GitHub settings