ci: publish PR screenshots to a ci-screenshots branch
A separate job with write access downloads the screenshots artifact and force-pushes it as a single commit, so screens can be reviewed with a plain git fetch. The build job keeps read-only permissions; forks are skipped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
This commit is contained in:
2 files changed
+24
No files matched your search
@@ -88,3 +88,4 @@ One line per decision: date · decision · alternative · reason.
|
||||
| 2026-10-02 | Automatic output stops at 4K UHD; no automatic stacking advice. | 8K / temporal-median denoise | 8K stays a manual choice; a median erases moving stars and stillness cannot be verified reliably. |
|
||||
| 2026-10-02 | Apply records a missing-data reason only where no advice exists; Optimise returns modules to Auto and only adds to the user's hero, exclusions, offset or output cap; a preset's own choices are stored as manual values, content-derived values stay Auto. | Overwrite | Manual values stay in force; re-analysis does not undo a chosen preset. |
|
||||
| 2026-10-02 | Advisor namespace is `Titano.Core.Advice` (class `Advisor`). | `Titano.Core.Advisor` | A class named like its namespace needed an alias in every `Titano.Core.*` caller. |
|
||||
| 2026-10-02 | CI also force-pushes each same-repository PR run's screenshots as one commit to the `ci-screenshots` branch (separate job, only it has `contents: write`). | Artifact only | Artifacts need an authenticated download; a branch can be fetched with plain git for visual review. The branch never merges and holds a single commit. |
|
||||
Reference in new issue
Block a user