-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Versioning script #29
Conversation
When crossing the repository boundary, the script report the incorrect PRODUCT and VERSION values, instead relying on its own repository location. Given that readies is a utility repository, this yields incorrect values - since it is usually located within a repository as a submodule.
@chayim Can we please please please do |
Given that it's written in sh and not bash, I'd say don't change it. sh is available across the unixes we support (currently), including *sd, meaning we don't need to install anything special. If we add something bash specific, we can change the #!shebang - but currently it would be inaccurate. |
@chayim I'm aware of the advantages of using |
Helping with tooling, I totally get. I'm biased to lowest common denominator - so I'll continue writing SH compliant Bash whenever possible. #! change inbound. Let me know what you think of the function wrapper - and being forced to call the script with any argument (and ignoring it). The reason was to make the script itself sourceable - though we should yank that into shibumi. Personally - I need to call it as a script via make. |
@chayim Good news is that we probably can use
|
Totally. It's a style thing - I try to write most common denominator until I have no choice. |
Kudos, SonarCloud Quality Gate passed! |
As per our discussion on #22 this is the first part of versioning, as discussed.