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

Document Best Practices for application versioning #7

Open
tacman opened this issue Dec 4, 2024 · 0 comments
Open

Document Best Practices for application versioning #7

tacman opened this issue Dec 4, 2024 · 0 comments

Comments

@tacman
Copy link

tacman commented Dec 4, 2024

Can you document how you use this tool for managing versions in an application using github? It'd make a great medium article, too.

I have a 'main' branch, which is simply the latest code. Each developer has their own branch, or (someday), we'll create branches that fix a particular issue.

I think I want to have a 1.x branch for the current release, and a 2.x branch for the beta release. We only deploy to one place, a dokku server, but I'd like to be able to deploy the latest release (e.g 1.1.4) and a beta release (2.1.1-beta), or something like that.

For example, I just used this bundle to push a 1.0.1 tag to https://github.com/survos/kidpanalley and now I'm trying to deploy a release to dokku. Should I have a 1.x branch? I'm confused about the relationship between tags and branches, how do I associate the latest version with a particular branch?

Thanks for considering this. I imagine you're an expert in versioning, many of us are just plodding along copying and pasting from examples.

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