Tidy the script folder up
#3633
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
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
Signed-off-by: Antonio Gamez Diaz <agamez@vmware.com>
absoludity
approved these changes
Oct 22, 2021
|
Merging as the CI got green, but it wasn't reported back to Github (circle ci was experiencing some minor outages yesterday) |
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.
Description of the change
I was about to start fixing the create_release script (#3566) when I noticed this folder was kind of a mess. So this PR is to clean it up a little bit.
Also, I've updated the copyright headers; even if it is something we will have to thoughtfully check at some point, we better start having some uniform text so that it's easier for us later.
Benefits
ignore the vs code colors
Possible drawbacks
Even if I did my best checking further file appearances and renaming, perhaps I missed one. It will be something we'll discover when executing the different CI flows. The fix, if happen to be required, should be straighforward.
Applicable issues
publishCI workflow is not working #3566)Additional information
N/A