Skip to content
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

Improvements to tag/release process #91

Open
djjudas21 opened this issue May 17, 2022 · 0 comments
Open

Improvements to tag/release process #91

djjudas21 opened this issue May 17, 2022 · 0 comments

Comments

@djjudas21
Copy link

djjudas21 commented May 17, 2022

Describe the bug

I maintain a helm chart for this project over at https://github.com/djjudas21/charts/tree/main/charts/hammond.

I noticed that the README for this project announces a new version of the application in 05bb22f but that there is no corresponding tag for 2022.04.26.

I also noticed that the Docker image that was built for version 2022.04.26 is present on Docker Hub tagged as version 1.0.0.

It's quite hard to track and deploy the correct versions of this project without proper use of tags.

Expected behavior
If it is possible, I would like to see:

  1. Development taking place in branches, and merged to main when it is ready
  2. Tags/Releases made on the git repo to coincide with the same versions you list in the README
  3. Docker images available on Docker Hub tagged with the same versions as the tags on this repo

If you want any help with this, I'm a devops engineer so this is my bread and butter 😃 I can either assist as a maintainer, or show you how to do it. I'm also experienced with automation via Github Actions which can do a lot of this stuff for you, automatically. But I think consistent tagging will bring huge benefits for admins and users of this app. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant