Explode yaml before merge #94
Merged
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
|
Would be awesome to get this PR merged. |
|
Thank you @bentastic27 and @pc-bob I wanted to iterate that this looks to be an issue with the Nevertheless, it is likely that CircleCI users use aliases and anchors in their config. As a support engineer with CircleCI, I encountered this issue for another customer. |
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.
Fixes:
#88
My change will resolve yaml aliases (exploding them?) before merging the yaml together. This solves the mentioned issue as well as another I faced where some aliases were rendered after the jobs/workflows they are used by in the resulting config file which causes errors.