-
- Downloads
post-receive: fire after locks release
This is a merge of change done on the stable branch, where it was restricted to Merge Request creations by pushvars to limit the risks. In all cases, it makes sense to send the post-receive only after new writes are permitted, because there's no telling what writes the Rails app would need to perform directly. As far as I understand, Git locking is weaker than Mercurial's, as it happens on a file-per-file basis. That's why the Rails app could easily grow new problematic writes that wouldn't be rejected by locks in the Git case.
Loading
Please register or sign in to comment