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

Should releases be a part of this project? #71

Open
ScottRobbins opened this issue Dec 29, 2021 · 2 comments
Open

Should releases be a part of this project? #71

ScottRobbins opened this issue Dec 29, 2021 · 2 comments

Comments

@ScottRobbins
Copy link
Owner

I keep thinking about how to create automatic versioning and make it work in a CI/CD system well. I keep coming back to the fact that I track what changes are a part of specific versions.

Automatically versioning would require some CI system to make commits and merge in git. This isn't impossible but always seems like friction that I wonder if it's possible to avoid somehow.

@ScottRobbins
Copy link
Owner Author

Just jotting down a random thought that I have put less than 10 seconds of consideration into:

Integrate more with git to get the version information from previous tags.

The thing I don't like is that editing or correcting change files for things that have released may not be possible w/o rewriting history. May not be worth it.

@ScottRobbins
Copy link
Owner Author

Maybe this is just an issue where I shouldn't be worried about making a bot automatically commit and merge. This tool is designed to avoid merge conflicts and so the rest is just a tooling problem with interacting with GitHub/GitLab

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