Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2018-01-26Use Process::Status rather than an integerLin Jen-Shin
However keep backward compatibility
2018-01-26Fail static-analysis if there's output to stderrLin Jen-Shin
TODO: fix offenders
2016-12-16Accept environment variables from the `pre-receive` script.Timothy Andrew
1. Starting version 2.11, git changed the way the pre-receive flow works. - Previously, the new potential objects would be added to the main repo. If the pre-receive passes, the new objects stay in the repo but are linked up. If the pre-receive fails, the new objects stay orphaned in the repo, and are cleaned up during the next `git gc`. - In 2.11, the new potential objects are added to a temporary "alternate object directory", that git creates for this purpose. If the pre-receive passes, the objects from the alternate object directory are migrated to the main repo. If the pre-receive fails the alternate object directory is simply deleted. 2. In our workflow, the pre-recieve script (in `gitlab-shell) calls the `/allowed` endpoint, which calls out directly to git to perform various checks. These direct calls to git do _not_ have the necessary environment variables set which allow access to the "alternate object directory" (explained above). Therefore these calls to git are not able to access any of the new potential objects to be added during this push. 3. We fix this by accepting the relevant environment variables (GIT_ALTERNATE_OBJECT_DIRECTORIES, GIT_OBJECT_DIRECTORY) on the `/allowed` endpoint, and then include these environment variables while calling out to git. 4. This commit includes (whitelisted) these environment variables while making the "force push" check. A `Gitlab::Git::RevList` module is extracted to prevent `ForcePush` from being littered with these checks.
2016-09-13Fix Gitlab::Popen.popen thread-safety issueAhmad Sherif
Fixes #21842
2016-09-02Use 'git update-ref' for safer web commitsJacob Vosmaer
2016-08-06Enable Style/SpaceAroundEqualsInParameterDefault copGabriel Mazetto
2015-03-25Style/RedundantReturn enabledDmitriy Zaporozhets
2015-01-05Close standard input in Gitlab::Popen.popenJacob Vosmaer
2014-02-25Make it possible to call Gitlab::Popen.popenJacob Vosmaer
2014-02-25Make the Gitlab::Popen path argument optionalJacob Vosmaer
2014-02-25Change Gitlab::Popen to use arrays for commandsJacob Vosmaer
2013-10-08Whitespace fixes to patchDale Hamel
2013-10-08Ensure directory exists before changing in popenDale Hamel
If the directory does not exist, we want to ensure that it does. Forking repos will fail in some situations because of this issue.
2013-05-05Replace old hashes with new 1.9 ruby hashes (rebase)Andrey Kumanyaev
2013-01-28Do gitolite calls async. Remove satellite with project removeDmitriy Zaporozhets