Hello, I noticed that there is a collision between the 2.20.3 branch, and the 2.20.3 release tag in Github. Is this expected? It is definitely not a good git practice.
For example it’s causing
to clone the branch head instead of the tag which has the commit that sets the non-snapshot version ( ).
Environment
None
Activity
Jody Garnett
April 8, 2022 at 9:40 PM
As this is a dev repo maintenance problem I am not assigning it a fixed-for date.
Jody Garnett
April 8, 2022 at 9:39 PM
Marking as resolved; but if we get a 2.20.4 branch and 2.20.4 tag created we will need to trouble shoot build scripts.
Jody Garnett
April 8, 2022 at 9:39 PM
That is not intensional, probably arguing with build scripts.
I have removed the branch after confirming it pointed to the exact same commit as the 2.20.3 tag.
Normally if someone is going to work on an emergency patch they would create a 2.20.3.x branch from the 2.20.3 tag; cherry-pick the fixes needed in, and make a 2.20.3-1 tag.
Hello, I noticed that there is a collision between the 2.20.3 branch, and the 2.20.3 release tag in Github. Is this expected? It is definitely not a good git practice.
For example it’s causing
to clone the branch head instead of the tag which has the commit that sets the non-snapshot version ( ).