Bug: "Committing to tag" warning is not shown

19 views
Skip to first unread message

Dominik Gnthr

unread,
Aug 5, 2022, 10:14:17 AM8/5/22
to TortoiseSVN

Hi,

I recently stumbled upon a bug, when I found a user had committed to a tag.

Normally the function
CSVNProgressDlg::IsCommittingToTag checks if you're committing to a tag and warns you.

But if you include a file that is not inside a tag, then the warning isn't shown.

Example commit:
Changed /project/tags/test.txt
This shows the warning

Example commit with two files:
Changed /project/tags/test.txt
Changed /project/something.txt
This does not show the warning.

I'm using the newest version (TortoiseSVN 1.14.3, Build 29387 - 64 Bit) and have not found anything related to that in the documentation or the changelog.

It would be great if you could look into it.

Thank you and have a nice day, Dominik


Stefan

unread,
Aug 5, 2022, 12:35:00 PM8/5/22
to TortoiseSVN
On Friday, August 5, 2022 at 4:14:17 PM UTC+2 Dominik Gnthr wrote:

Hi,

I recently stumbled upon a bug, when I found a user had committed to a tag.

Normally the function
CSVNProgressDlg::IsCommittingToTag checks if you're committing to a tag and warns you.

But if you include a file that is not inside a tag, then the warning isn't shown.

Example commit:
Changed /project/tags/test.txt
This shows the warning

Example commit with two files:
Changed /project/tags/test.txt
Changed /project/something.txt
This does not show the warning.

I assume here that you've chosen /project as the root of your commit. In that case of course the check won't catch that you might be committing to a tag. Because while you see the files in the commit dialog, when the actual commit happens only /project is passed, and no paths inside that folder.

But honestly: it's very, very unusual to have a working copy checked out from the repo root. I mean you would have *all* tags and branches checked out as well. That's a huge waste of disk space.

check out from /trunk of a branch instead, and use "switch" to change between your branches and trunk. That's the recommended way.
 

Tony Rietwyk

unread,
Aug 6, 2022, 2:18:48 AM8/6/22
to TortoiseSVN
Stefan said "check out from /trunk of a branch instead..."
I assume that was meant to read "check out from /trunk OR a branch instead..."
Reply all
Reply to author
Forward
0 new messages