-
Notifications
You must be signed in to change notification settings - Fork 0
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
Modify version() and release() functions #77
Conversation
@teodora-aleksovska can you also provide case scenarios for both the |
@gocemitevski Certainly, I tested these commands on VMT, and after executing enabler platform version and enabler platform release <submodule_name> , I received these outputs: teodora@teodora-ThinkPad-T16-Gen-1:~/vmt-platform/enabler$ enabler platform version teodora@teodora-ThinkPad-T16-Gen-1:~/vmt-platform/enabler$ enabler platform release 2.1.7 /home/teodora/vmt-platform/platform/microservice-obr |
@teodora-aleksovska can you please document what is the expected output for both commands? Doesn't matter which project enabler is being used on. What is the expected output of the commands in general, not specifically on your machine. |
release: The release command releases the platform by tagging the platform repository and tagging all individual components (submodules) using their respective SHA that the submodules point to. version: The version command checks the versions of microservices in submodules. |
@teodora-aleksovska OK. Please add all relevant descriptions in the README as well for each command. https://github.com/keitaroinc/enabler?tab=readme-ov-file#commands. The changes in the README should also be included in this branch. |
This pull request contains resolved issues with version() and release() functions for the enabler platform command.