fix(scope): use subject repo for cross-repo actions#140
Merged
barrettruth merged 3 commits intomainfrom Apr 11, 2026
Merged
Conversation
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.
Problem
forge was still deriving repo and project ownership from the local checkout after a picker selected a PR, issue, run, or release from another subject repo. That broke cross-repo and cross-project flows like CI logs, review follow-ups, release actions, and edit/create operations.
Solution
Add a shared subject-scope module and thread explicit scope metadata through picker entries and nested actions. Update the GitHub, GitLab, and Forgejo/tea backends plus compose/completion flows to honor explicit repo or project overrides, and add regression coverage for the new scoped command shapes.