Conversation
Signed-off-by: Pieter Viljoen <ptr727@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR refactors GitHub Actions workflow steps to simplify single-command run syntax, improving readability and reducing unnecessary multi-line blocks in build-related tasks.
Changes:
- Simplified single-command
run: |blocks into single-linerun:commands. - Fixed/standardized YAML indentation for steps in the executable artifact upload job.
Reviewed changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/build-library-task.yml | Simplifies the zip step command into a single-line run. |
| .github/workflows/build-executable-task.yml | Normalizes step indentation and simplifies the zip step to a single-line run. |
| .github/workflows/build-datebadge-task.yml | Simplifies the date output command into a single-line run. |
Uh oh!
There was an error while loading. Please reload this page.
ptr727 added a commit
that referenced
this pull request
Aug 5, 2026
…e cross-repo issue refs Both from the Copilot review on #571. The escalation about a downstream repo holding its own audit report claimed the two files sit at the same relative path. They do not. The hub's is `reports/blog/audit.md` and the downstream one is `reports/Blog/audit.md`, differing in the case of one directory, so the claim overstated the collision it was raising. The review read this as a typo in the citation and asked for the lowercase form. That fix would have been wrong in the other direction, because the downstream path really is capital-B and lowercasing the citation would misquote the repo being audited. What was actually wrong was the sentence around it, so the escalation now names the case difference and says why it makes the confusion worse rather than better: it is invisible on a case-insensitive filesystem, and a reader takes it for a typo rather than for a boundary. The matrix abbreviated two of three cross-repo issue references to bare `#28` and `#29` after a qualified `ptr727/Blog#27`. In a hub document a bare reference is a hub reference, which is the file's own convention for #339, #456, and #558. The ambiguity is concrete rather than theoretical: ProjectTemplate #27, #28, and #29 all exist, so the bare forms rendered as links to unrelated merged pull requests in this repo. All three are fully qualified now. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ptr727 added a commit
that referenced
this pull request
Aug 5, 2026
…571) The 2026-08-03 report graded Blog as source-only against a hub that had no static-site type, and recorded that it was due a re-run once the deploy existed. This is that run, replacing the file in whole per AUDIT.md section 8. Run stamp `audit run 2026-08-05T21:57:38Z | hub 01507a0`, read at Blog `main@2b132e4`. Verdict operational, no defect. All nine `hugo.*` checks are judged for the first time and pass, each cited to file:line. The three deviations the first run recorded are closed: ptr727/Blog#27 (the remote release tree was never pruned), #28 (the vendored theme recorded no upstream ref), and #29 (the generator pin was duplicated across two workflows). Two drift classes stay open, both the hub having advanced past what the repo carries: seven stale verbatim units and 17 prose findings. One needs sequencing, since the `Closes #N` rule moved out of Release Model into Branching Model in #563, so a re-vendor taking the new Release Model without the new Branching Model drops the rule rather than leaving it stale. The run also surfaced a hub defect. `spec/audit.py` flags a carried file naming the hub anywhere in it, with no exemption for the byte-locked AGENTS.md "Fleet Bootstrap" section, whose first sentence must name the hub because saying where the canonical rules live is that section's function. The finding is unclearable by construction and fires on any repo carrying the current canonical, so it spreads with the carry. Recorded as escalation 1 with the fix; not applied here, since it changes the runner rather than a report. The matrix takes the run's date and findings. Ten clause-joining semicolons and three spaced hyphens elsewhere in the file are fixed in the same pass. The 17 remaining `dash` findings are deliberately left: every one is a `| - |` empty-table-cell placeholder, the notation the file's own header documents, so they are a prose_lint.py exemption gap rather than divergent content, systemic across 46 cells in 8 report files. Copilot review closed over two rounds, second covering the head. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 freeto 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.
Signed-off-by: Pieter Viljoen ptr727@users.noreply.github.com