Gate American English, and record what a file gate cannot reach - #30
Merged
Conversation
This repo is public. Its README, issue forms and issue bodies are the pages an external reviewer reads before they read anything else we have written, so it gets the same gate as the product repos -- edgent-lms (#460), vforce-lakehouse (#2366), cockpit (#680), Flow (#645), quantumflight (#129). The tracked files were already clean; this is prevention, not repair. Nothing is excluded, because nothing here is vendored, quoted or fixture data: every file in this repo is ours and is read by outsiders. The two British spellings this repo actually carried were in ISSUE BODIES, which live in GitHub rather than in git. Both said "enrolment"; both were corrected through the API alongside this change, each with a comment recording that the edit was spelling only and changed nothing about what is tested or how it is graded. That gap is written into the script's header rather than left implicit: CI can gate files, and in this repo the substance of the UAT plan is not in a file. An issue body here is a published page, and keeping it in American English stays a review habit. Closes #29
The job sat queued indefinitely on vforce360-arc. The rest of the estate uses the ARC runner because the org is capped at $0 on GitHub-hosted minutes for PRIVATE repos -- but this repo is public, public repos get GitHub-hosted minutes free, and the org runner group does not serve public repos, so no runner was ever going to pick it up. The reason is written into the workflow so the next person does not copy the private-repo pattern here again.
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
1 participant
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.
Gate American English, and record what a file gate cannot reach
This repo is public. Its README, issue forms and issue bodies are the pages an
external reviewer reads before they read anything else we have written, so it
gets the same gate as the product repos -- edgent-lms (#460),
vforce-lakehouse (#2366), cockpit (#680), Flow (#645), quantumflight (#129).
The tracked files were already clean; this is prevention, not repair. Nothing
is excluded, because nothing here is vendored, quoted or fixture data: every
file in this repo is ours and is read by outsiders.
The two British spellings this repo actually carried were in ISSUE BODIES,
which live in GitHub rather than in git. Both said "enrolment"; both were
corrected through the API alongside this change, each with a comment recording
that the edit was spelling only and changed nothing about what is tested or how
it is graded.
That gap is written into the script's header rather than left implicit: CI can
gate files, and in this repo the substance of the UAT plan is not in a file. An
issue body here is a published page, and keeping it in American English stays a
review habit.
Closes #29