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.
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.