Back to issue list Export

While using Nitpick I think it is committing the entire project from the root and not just limiting itself to the Nitpick database as it used to. This is using the svn VCS backend.

travisb 2013-08-13 19:47:19
hash: 6e1ca951d94a7688c410021a14cbd68194d06073ab6eebc44d8c89d515ef16ca
Date: 2013-08-13 19:47:19
User: travisb

This doesn't happen with just a plain Nitpick database, but does happen if you have an SVN foreign repository pointing to the same branch.

travisb 2013-08-13 19:54:51
hash: cf74b0ed3468120769204d484a2cef927fb8dc7949a691afb2516cd829c69da2
Date: 2013-08-13 19:54:51
User: travisb

Here's the situation. In subversion 1.6 if you were inside the .nitpick directory and the svn:external was in the project root (to avoid infinitely recursive externals) then the Foreign projects would still be marked as such. However, with subversion 1.7 this is no longer the case. Inside .nitpick 'svn stat' now shows a status of ? for the external instead of X.

travisb 2013-09-06 08:09:09
hash: 832dbdd383e609ce03fb97b3a050b5a07b748f970ba74885648ac8a59db6221f
Date: 2013-09-06 08:09:09
User: travisb

This is still broken in my meta repository.

travisb 2013-09-06 08:22:48
hash: 87ee190a8aa96b19cc7cddca7f8ecca303e7a73dcccc892a37826fa14ee4fb3c
Date: 2013-09-06 08:22:48
User: travisb

Looks to be because of a stray newline creating an empty foreign project.

Tracked by Nitpick