check for versions (emba, git and docker) - #918
Merged
Conversation
m-1-k-3
requested changes
Nov 29, 2023
m-1-k-3
left a comment
m-1-k-3
left a comment
Member
There was a problem hiding this comment.
cool PR with valuable details regarding updates. Could you please check my comments?
m-1-k-3
reviewed
Nov 30, 2023
m-1-k-3
left a comment
m-1-k-3
left a comment
Member
There was a problem hiding this comment.
please merge the current master of EMBA to ensure everything will run smooth
Member
|
This looks really useful
|
m-1-k-3
approved these changes
Nov 30, 2023
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
It checks for the versions of emba, git and docker. It uses a new script to update the VERSION.txt file.
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)? If possible add a screenshot.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: