Is there any way to help avoid accidental commits to svn:externals in TortoiseSVN?
I am on a development team with some members who have accidentally committed changes to svn:externals. If the externals in question are from a different repo, they get handled better in TortoiseSVN, with a clear visual separation in TortoiseSVN (see below), along with not being checked by default:
But if they're from the same repo (different projects in different areas of a large common repo) there is no visual indication that the files to be committed are any different.
Aside from server-side features like commit hooks, is there any way to prevent commits to externals? This is really causing some problems.
svn svn-externals
add a comment |
I am on a development team with some members who have accidentally committed changes to svn:externals. If the externals in question are from a different repo, they get handled better in TortoiseSVN, with a clear visual separation in TortoiseSVN (see below), along with not being checked by default:
But if they're from the same repo (different projects in different areas of a large common repo) there is no visual indication that the files to be committed are any different.
Aside from server-side features like commit hooks, is there any way to prevent commits to externals? This is really causing some problems.
svn svn-externals
add a comment |
I am on a development team with some members who have accidentally committed changes to svn:externals. If the externals in question are from a different repo, they get handled better in TortoiseSVN, with a clear visual separation in TortoiseSVN (see below), along with not being checked by default:
But if they're from the same repo (different projects in different areas of a large common repo) there is no visual indication that the files to be committed are any different.
Aside from server-side features like commit hooks, is there any way to prevent commits to externals? This is really causing some problems.
svn svn-externals
I am on a development team with some members who have accidentally committed changes to svn:externals. If the externals in question are from a different repo, they get handled better in TortoiseSVN, with a clear visual separation in TortoiseSVN (see below), along with not being checked by default:
But if they're from the same repo (different projects in different areas of a large common repo) there is no visual indication that the files to be committed are any different.
Aside from server-side features like commit hooks, is there any way to prevent commits to externals? This is really causing some problems.
svn svn-externals
svn svn-externals
asked Nov 14 '18 at 20:59
Jason SJason S
107k135486817
107k135486817
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Never mind, I wasn't using the latest version of TSVN. Recent versions have the BlockPeggedExternals
feature
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about theBlockPeggedExternals
feature then.
– Jason S
Nov 15 '18 at 17:38
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308617%2fis-there-any-way-to-help-avoid-accidental-commits-to-svnexternals-in-tortoisesv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Never mind, I wasn't using the latest version of TSVN. Recent versions have the BlockPeggedExternals
feature
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about theBlockPeggedExternals
feature then.
– Jason S
Nov 15 '18 at 17:38
add a comment |
Never mind, I wasn't using the latest version of TSVN. Recent versions have the BlockPeggedExternals
feature
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about theBlockPeggedExternals
feature then.
– Jason S
Nov 15 '18 at 17:38
add a comment |
Never mind, I wasn't using the latest version of TSVN. Recent versions have the BlockPeggedExternals
feature
Never mind, I wasn't using the latest version of TSVN. Recent versions have the BlockPeggedExternals
feature
answered Nov 14 '18 at 21:52
Jason SJason S
107k135486817
107k135486817
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about theBlockPeggedExternals
feature then.
– Jason S
Nov 15 '18 at 17:38
add a comment |
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about theBlockPeggedExternals
feature then.
– Jason S
Nov 15 '18 at 17:38
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
The feature was available like since 2013. :)
– bahrep
Nov 15 '18 at 15:33
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about the
BlockPeggedExternals
feature then.– Jason S
Nov 15 '18 at 17:38
really? Huh, I guess it's been awhile. Was it enabled by default? I installed 1.9.7.27907 in 2017 and the behavior changed when I used 1.11.0.28416. I was running 1.9.7 yesterday before I upgraded, and I was able to select pegged externals for commit... but I didn't know about the
BlockPeggedExternals
feature then.– Jason S
Nov 15 '18 at 17:38
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308617%2fis-there-any-way-to-help-avoid-accidental-commits-to-svnexternals-in-tortoisesv%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown