fix(export), fix output to show the exported lane in case no new snaps added #9175
Conversation
This file contains 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.
In some cases, the export doesn't bring any new component or snap/tag to the remote, but it does update the lane object. It happens for example in the following two cases:
Until now, it was showing "nothing to export" for both cases above. The first case actually didn't do any action and nothing was exported, the second case the message is misleading because the lane object itself was exported.
This PR fix both cases. The first case is now exporting the new lane to the remote and for both cases it shows the message "exported the lane xxx/yyy" in the output.