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

Automate versioning and releases on merge to master using GitHub Actions. #46

Open
mmarquezs opened this issue Aug 26, 2021 · 3 comments
Assignees

Comments

@mmarquezs
Copy link
Owner

Automate versioning somehow.

@mmarquezs mmarquezs self-assigned this Aug 26, 2021
@mmarquezs mmarquezs changed the title Automate versioning somehow. Automate versioning and releases on merge to master using GitHub Actions. Dec 18, 2021
@rix1337
Copy link
Contributor

rix1337 commented Jun 14, 2022

@mmarquezs I should be able to help with that

Take a look at https://github.com/rix1337/MyJD-API/blob/master/.github/workflows/CreateRelease.yml

That's how I automatically build python packages on pushes to master.

@mmarquezs
Copy link
Owner Author

mmarquezs commented Jul 1, 2022

Thanks for the info, although I had a different thing on mind. I already use a similar thing to what you shared, although when I manually create a release.
My idea was different here, in a work project I have a setup that basically takes the version from git, the branch and tags.

So if you create the branch: release/1.17
The first merged there is 1.17.0 and any subsequent merges are 1.17.1 etc.... it's automatic.
Until you create a new branch for 1.18 for example.

That goes together with the releasing system that tracks those branches pulls that version tag and creates a release setting that version on it.

So to create a new version I do not need to modify the code to change the version in a file. Just pushing it to the specific release branch and it will automatically increase the version number and do a release.

@rix1337
Copy link
Contributor

rix1337 commented Jul 2, 2022

Ah, that sounds like a super helpful feature.
Maybe there is an existing GitHub action for this.

I'll update this issue if I find anything.

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

2 participants