-
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
Add tags to the project #5
Comments
For my (local workstation) clone of my fork of the NASA repo (so my origin is freephile/meza), I added the enterprisemediawiki repo as a third remote, and fetched all the tags. Then I pushed the tags into my repo.
Then I could
But, the canonical (NASA) repo still needs new tags to represent the 35.x version as well as the pending 39.x version. |
Existing tag historyHere is partial output of the tag history (sorted)
And then, the details of the last tag
|
SolvedYou can now see the long list of tags I created for the 35.x series as well as a new tag for the beginning of the REL1_39 branch and milestone. [userx@localhost meza]$ I pushed these tags up into this repo.
|
Creating an issue to track this work.
|
The project is run by tags and releases. There have been no tags or releases since the project was cloned to the NASA organization. So, create a tag "35.0.0" for the GRC-ATF branch, then create a new tag 39.0.0 for the REL1_39 branch and create a release for the merged product.
We want tags on the development branch because
meza --version
looks for tags withsudo git --git-dir=/opt/meza/.git describe --tags
which is currently failing because there are zero tags. We can prevent the failure by using the--always
option (that would return the latest git hash) but we really need to start using tags and releases.The text was updated successfully, but these errors were encountered: