-
Notifications
You must be signed in to change notification settings - Fork 672
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
Change branch/versioning system #2815
Comments
For 4 how about creating a |
Nope, I think your instincts are right. We'll do the following: Branches
Version Info
We will use the E.g. for <PropertyGroup>
<VersionPrefix>1.15.10</VersionPrefix>
<VersionSuffix>pre.$([System.DateTime]::UtcNow.ToString("yyyyMMdd.HHmm"))</VersionSuffix>
</PropertyGroup> I'm still not sure how to update the build automatically. In other projects I used T4 templates. But I'd like to avoid that here. |
Isn't possible and enough only the commit id to track? |
Ok....
I'm backing away from using |
I've renamed the branches. Not sure this is going to work, but I gotta keep trying...
Sorry for any trouble this causes as I do this. |
I don't think my plan as stated will work. gitversion is just not flexible enough. I will need to revert back to having My next step is to try to use |
Ok, I've "fixed"
Now, I'm going to do a new release of v1 from I still don't know how to make this work for v2's branches. But I haz ideas. |
now... on 'main Will result in a And, if I'm right (fingers crossed), adding a tag ( I'll test this asap once the rest of the awaiting v1 PRs are merged. |
@tig I can't build the develop branch. Gives error because of the nuget packages.
|
Hmmmm.. ![]() Did you try a |
You may need to clear your nuget cache? dotnet nuget locals all -list
dotnet nuget locals all --clear Kill all instances of |
I'm not sure because once I needed to add others source mapping but I've gotten issues with others projects and I removed all and only keep the |
Right now we use Git Flow.
main
always represents the most recent release ofv1
develop
is thev1
working branchv2_develop
is thev2
working branchmain
forv2
4 and 5 are problematic for maintaining multiple versions of T.Gui over time (v1 and v2 etc...).
6 makes it hard to determine what version of T.Gui is in use when doing local dev.
Here's my thoughts on addressing this. I've spent a bunch of time digging into this, but am still quite confused anď unclear on the right approach. This Issue is my attempt to write it all down to drive more clear thinking. Help appreciated.
The text was updated successfully, but these errors were encountered: