fix(2127): handle repoNames with tags - #2128
Merged
eddumelendez merged 2 commits intoJun 19, 2023
Merged
Conversation
Contributor
Author
|
@eddumelendez - could you kindly review this PR 🙏 |
Member
|
Thanks for your contribution, @setchy ! |
Contributor
Author
|
Thanks @eddumelendez for the speedy review. Greatly appreciated 🙏 |
Contributor
Author
|
@eddumelendez - to help with my internal sprint planning and stakeholder mgmt, can you educate my about the release cadence for |
Member
|
There is no release schedule but as soon there are many good improvement features we will do the release. Indeed, I'm just waiting for other PR to perform it. |
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
2 participants
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.
This update improved the handling for
resolveRepositoryNamewhen the image statement includes a registry and tags.Current behavior will throw the error as reported in the issue
Resolves: #2127 - confirmed by @leomao10