[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Feature request: Configure hooks for server repository path

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 21 Oct 2014 21:23:21 +0200

On 20.10.2014 23:08, Eugene Kotlyarov wrote:
> Hi
>
> Currently you have to configure hook scripts for each checked out
> repository copy, this is inconvenient when you checkout same
> repository twice, or checkout several branches.
>
> It would be nice to configure hook scripts for server repository path
> instead of local path, preferably with masks e.g. when hook is set
> for http://repository/* it will be called for all checked out copies
> that have server path below http://repository

See the docs:
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-propertypage.html#tsvn-dug-propertypage-tsvn-props

You can specify the path to the hook script like this:
%REPOROOT%/trunk/contrib/hook-scripts/client-side/checkyear.js

Instead of %REPOROOT% you can also specify %REPOROOT+%. The + is used to
insert any number of folder paths necessary to find the script. This is
useful if you want to specify your script so that if you create a branch
the script is still found even though the url of the working copy is now
different. Using the example above, you would specify the path to the
script as %REPOROOT+%/contrib/hook-scripts/client-side/checkyear.js.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3090257
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-10-21 21:23:04 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.