Open Jehreg opened 13 years ago
Which version of Redmine are you using? I am wondering if the "subproject of" selector is blank on the settings page (because of a bug in Redmine)? This would explain that behavior. I just tried this, incidentally, and it seems to work fine with version 1.2.2 of Redmine...
Note that update_git_repo_for_new_parent is set up as a ":before_filter", so gets called on every project update (regardless of whether or not the parent changes); the internals of the routine decides whether or not a change actually happened....
ChiliProject, commit id b43bf18
Do you know which version this corresponds to? (I am more familiar with the svn numbers from the redmine site)?
At any rate, more important is my other question: is the "subproject of" selector blank on the settings page? (rather than pointing to the parent project)?
Please try my master branch. It has a bunch of fixes to make movement of parents for repositories much more stable. Please give it a try:
The admin goes to check the Project settings and saves the page. One second later the following appears in the auth.log:
So, somehow, the function update_git_repo_for_new_parent in ./lib/git_hosting/patches/projects_controller_patch.rb gets called even when the project parent doesn't get changed.
This is plugin commit 1101f5d and Chili commit b43bf18
Anyone else seen this ? Anyone else using sub-projects that are at least 2 deep ?