The best way to combine git with. Net in version control
I'm currently working on a project (just me), and I already know how to handle versioning on it. I'm using the classic
<major>.<minor>.<build or patch>.
The problem I have is that I want to have tags in some of my commits pointing to the corresponding versions, but I don't want to do it manually.
Now I'm currently doing:
- If I'm going to release the
v0.2.13, I change the
AssemblyInfo.csand set that version
- Commit the changes on Git
- Add tag
v0.2.13(manually) on Git
- Build the project
- Create a
.zipfile (not all time time) and name it like
Am I doing it wrong?
I could easily create an script to do the last step automatically, but I'm wondering if there is a good practice about automating the other part?
Leave a Reply
- version control - Replace in Git remote.origin.url What's the best way to do it?
- git - Dockerfile version control best practices
- What is the best way to version control JSON objects
- Version control - git workflow best practices
- .net - What is the best way to use assembly version control properties?
- More similar questions >>