feat(target): define Forge target default policy#151
Merged
barrettruth merged 1 commit 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
The new
:Forgecommand language could parse explicit repo and revision addresses, but it still had no canonical policy for omitted targets. That left alias order, collaboration repo defaults, CI repo defaults, and browse/create fallback behavior implicit.Solution
Add a dedicated target policy layer with configurable aliases and default repo settings, thread normalized default policy metadata through
forge.cmd, and pass resolved scope defaults into list/create/browse dispatch. This also documents the alias resolution order and default-vs-explicit override model in the help file.