Repository navigation
chore: ready the repository for public visibility - #448
Merged
Merged
Conversation
Fork pull requests must never reach the workstation runners, and a fork branch named main must never deploy. Comments that cited a gitignored file or a local path now carry their own reason.
Contributor
🤖 MERGED
GitHub merged this pull request.
d602ec48-0899-4364-a8e3-d8904c9cbf4b Selected findings run after merge and open separate pull requests. |
The copy contract test rejects any root Markdown line that names a home path.
Contributor
There was a problem hiding this comment.
Harlan Agent Kit posted this automated review. AI open source policy.
Automated Review: READY.
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
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.
🔗 Linked issue
None.
❓ Type of change
📚 Description
This repository is about to go public. Two workflow paths would then let a stranger run code on the workstation or ship it to production:
Testruns every job on the self-hosted workstation pool for anypull_request. A fork's pull request would run its own code on that host.Deploy to Cloudflaredeploys any successfulTestrun whosehead_branchismain. A fork's branch namedmainmatches. The deploy then checks out the fork's commit and builds it with production secrets.Testnow runs each job only for a push or for a pull request from a branch in this repository. A fork's run skips every job, and a run of skipped jobs still concludessuccess. SoDeploy to Cloudflarenow also requires apushevent from this repository.Ten comments cited
GOOGLE_RECOVERY.md, which is gitignored, or a note under~/scratch. Nobody who clones the repository can read either. Each comment now states its own reason. TheAGENTS.mdtrap about those comments becomes a rule against such citations.