docs: recommend the @v1 release tag for reusable-workflow consumers #12

Merged
steve merged 2 commits from docs/recommend-v1 into main 2026-06-28 04:17:19 +00:00
Showing only changes of commit 09d04de619 - Show all commits
+4 -3
View File
@@ -6,7 +6,7 @@
# jobs: # jobs:
# review: # review:
# if: ... # actor gate for the comment trigger # if: ... # actor gate for the comment trigger
# uses: steve/gadfly/.gitea/workflows/review-reusable.yml@<sha> # uses: steve/gadfly/.gitea/workflows/review-reusable.yml@v1
# secrets: # forward ONLY what the reviewer needs # secrets: # forward ONLY what the reviewer needs
# OLLAMA_CLOUD_API_KEY: ${{ secrets.OLLAMA_CLOUD_API_KEY }} # OLLAMA_CLOUD_API_KEY: ${{ secrets.OLLAMA_CLOUD_API_KEY }}
# CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }} # CLAUDE_CODE_OAUTH_TOKEN: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
@@ -25,8 +25,9 @@
# #
# Advisory only — never blocks a merge. The image is pinned to an immutable # Advisory only — never blocks a merge. The image is pinned to an immutable
# :sha- tag here (act_runner caches :latest); bump it per Gadfly release. # :sha- tag here (act_runner caches :latest); bump it per Gadfly release.
# Consumers should likewise pin `uses: ...@<sha>` (not @main) so a push to this # Consumers should pin `uses: ...@v1` — a curated release tag moved on deliberate
# repo can't silently change the code that runs with their forwarded secrets. # releases, so central tuning here propagates without per-consumer edits — or a
# full `@<sha>` for an immutable pin. Avoid `@main` (moves on every push).
name: Gadfly review (reusable) name: Gadfly review (reusable)