Skip to content

Conversation

jeripeierSBB
Copy link
Contributor

Previously the message was not very clear about what happened if reading the warning. The new wording states that a project is skipped during migrations which should be clearer to users.

Previously the message was not very clear about what happened if reading the warning. The new wording states that a project is skipped during migrations which should be clearer to users.
@jeripeierSBB jeripeierSBB force-pushed the better-error-message branch from 3c5f81e to a07a536 Compare March 3, 2022 20:56
@jeripeierSBB jeripeierSBB requested a review from devversion March 3, 2022 21:01
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@devversion devversion added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release merge safe labels Mar 3, 2022
@amysorto amysorto merged commit 73008a4 into angular:master Mar 3, 2022
amysorto pushed a commit that referenced this pull request Mar 3, 2022
…24513)

Previously the message was not very clear about what happened if reading the warning. The new wording states that a project is skipped during migrations which should be clearer to users.

(cherry picked from commit 73008a4)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants