Repository navigation
feat(create-release-branch): show actionable errors - #160
Draft
GuillaumeRx wants to merge 5 commits into
Draft
GuillaumeRx wants to merge 5 commits into
GuillaumeRx wants to merge 5 commits into
Conversation
3 of 4 tasks
GuillaumeRx
force-pushed
the
gr/crb-output-02-errors
branch
from
November 5, 2026 17:49
015b34d to
164387d
Compare
…nd align problem lines
This branch has not been deployed
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.
Explanation
Second step of the output revamp: errors tell the user what is wrong and how to fix it.
Caused by:lines. The stack trace only shows withDEBUG=create-release-branch:*.UserFacingErrorclass and describe themselves.{ packageName, problem, hint }. The texts are rewritten to say what to do next.References
Checklist