Move configurations to files #29
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
brandoncc
force-pushed
the
move-configurations-to-files
branch
2 times, most recently
from
37e473e
to
95e0467
Compare
brandoncc
force-pushed
the
move-configurations-to-files
branch
from
95e0467
to
d9ef335
Compare
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.
Manually maintaining the configuration output for each stack was not user-friendly. That process has been integrated with the build process for each stack, so it is completely automatic. A nice side effect is that existing build information about unsupported stacks will now be automatically removed during each run of the build script (build.sh).