Repository navigation
chore: call the shared pi-review job instead of copying it - #124
Merged
Merged
Conversation
The workflow was a generated copy of the whole job, pinned to a commit of pi-extensions, so every improvement needed a re-pin and a commit here (AutumnsGrove/pi-extensions#34). It is now a small caller: triggers, path filter, concurrency, permissions, and `uses: .../pi-review-reusable.yml@main` with the settings path and the timeouts. The job body, the same-repo guard (which now runs first) and the token handling live once, in pi-extensions. Settings stay here and are read at run time, so the model, provider, tools and limits are unchanged. `pi.packageRef` is gone; an older value is ignored.
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.
Moves this repo's pi-review install to the shared reusable workflow (AutumnsGrove/pi-extensions#34): a small caller at
@maininstead of a generated copy of the whole job. Settings stay local and are read at run time;pi.packageRefis dropped. The job body, the same-repo guard (now first) and the App-token fallback live in pi-extensions.