On Oct 12, 2020, at 02:21, Jonas Hahnfeld <hah...@hahnjo.de> wrote: > > Am Sonntag, den 11.10.2020, 12:12 -0400 schrieb Dan Eble: >> On Oct 11, 2020, at 10:33, Jonas Hahnfeld <hah...@hahnjo.de> wrote: >>> 2.21.7 has already been built and tagged (see git), the commits will >> >> I need a little more help than "see git". > > I was referring to the new tag in the repository, which gives a pretty > noticeable line on git fetch / pull (in my opinion): > * [new tag] release/2.21.7-1 -> release/2.21.7-1
I never see this in the GUI I use. >> I can see, after the fact, a merge from release/unstable into master that >> updated the version. I guess I need to check the release/unstable branch >> before I merge an MR with new regression tests to master. Is that right? > > Yes, . . . Is there any possibility to tweak this process so that regular contributors to master don't have to monitor a separate branch? — Dan
