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-06-19Force push is handled by Gitaly nowZeger-Jan van de Weg
Closes gitlab-org/gitaly#348
2018-06-19Eliminate N+1 queries in LFS file locks checks during a pushStan Hu
This significantly improves performance when a user pushes many references. project.path_locks.any? doesn't cache the output and runs `SELECT 1 AS one FROM "path_locks" WHERE project_id = N` each time. When there are thousands of refs being pushed, this can time out the unicorn worker. CE port for https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6159.
2018-06-06change wordingMark Chao
2018-04-05Add helper for accessing lfs_objects for projectBob Van Landuyt
This makes accessing LFS Objects for a project easier project.lfs_storage_project.lfs_objects` becomes project.all_lfs_objects This will make the refactor in https://gitlab.com/gitlab-org/gitlab-ce/issues/39769 easier to deal with.
2018-03-28Remove permanent redirectsBob Van Landuyt
Removes permanent redirects, this means that redirects will only be possible as long as the old route isn't taken by a new project/group.
2018-03-07Limit queries to a user-branch combinationBob Van Landuyt
The query becomes a lot simpler if we can check the branch name as well instead of having to load all branch names.
2018-03-07Allow maintainers to edit directly in a forkBob Van Landuyt
2018-02-19Merge branch 'jej/avoid-slow-file-lock-checks' into 'master'Sean McGivern
Avoid slow File Lock checks when not used Closes #43339 See merge request gitlab-org/gitlab-ce!17140
2018-02-19Avoid slow File Lock checks when not usedJames Edwards-Jones
Also avoid double commit lookup during file lock check by reusing memoized commits.
2018-02-15Only check LFS integrity for first branch in pushJames Edwards-Jones
2018-02-07Backport of LFS File Locking APIRubén Dávila
2018-02-06Merge branch 'master' into '26388-push-to-create-a-new-project'Douwe Maan
# Conflicts: # lib/gitlab/path_regex.rb
2018-02-06Moves project creationg to git access check for git pushTiago Botelho
2018-02-06Abstracts ProjectMoved and ProjectCreated into a BaseProjectTiago Botelho
2018-02-06Move new project on push logic to a serviceTiago Botelho
2018-02-06Add specsTiago Botelho
2018-02-06Adds remote messsage when project is created in a push over SSH or HTTPTiago Botelho
2018-02-02Refactor Gitlab::Git code related to LFS changes for Gitaly migrationAlejandro Rodríguez
We stop relying on Gitlab::Git::Env for the RevList class, and use Gitlab::Git::Repository#run_git methods inteaad. The refactor also fixes another issue, since we now top using "path_to_repo" (which is a Repository model method).
2018-01-23Backport changes to Gitlab::Checks::ChangeAccess from EEDouwe Maan
2017-12-25Disable redirect messages for anonymous clonesStan Hu
2017-12-25Fix Error 500s with anonymous clones for a project that has movedStan Hu
Closes #41457
2017-12-08Allow git pull/push on project redirectsMayra Cabrera
2017-11-09Handle forks in Gitlab::Checks::LfsIntegrityJames Edwards-Jones
2017-11-06Prevent git push when LFS objects are missingJames Edwards-Jones
2017-08-29replace `is_ancestor` with `ancestor?`Maxim Rydkin
2017-08-11Migrate force push check to GitalyAhmad Sherif
2017-06-05Remove GitAccessStatus (no longer needed)Michael Kozono
2017-06-05Refactor to let GitAccess errors bubble upMichael Kozono
No external behavior change. This allows `GitHttpController` to set the HTTP status based on the type of error. Alternatively, we could have added an attribute to GitAccessStatus, but this pattern seemed appropriate.
2017-06-05Fix Git over HTTP specMichael Kozono
* The spec has 7 failures at this point * Specify rendered error messages * Render the GitAccess message rather than “Access denied” * Render the Not Found message provided by GitAccess, instead of a custom one * Expect GitAccess to check the config for whether Git-over-HTTP pull or push is disabled, rather than doing it in the controller * Add more thorough testing for authentication * Dried up a lot of tests * Fixed some broken tests
2017-05-08Add confirm delete protected branch modalSam Rose
2017-04-10Don't pass `env` anymore to GitAccess, ChangeAccess, and ForcePushRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-04-10Retrieve Git-specific env in Gitlab::Git::RevList and add a new #new_refs methodRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2017-04-06Protected Tags backend review changesJames Edwards-Jones
Added changelog
2017-04-04Cleanup & tests for UserAccess#can_create_tag?James Edwards-Jones
2017-04-04Protected Tags prevents all updates instead of just force pushes.James Edwards-Jones
This only changes behaviour for masters, as developers are already prevented from updating/deleting tags without the Protected Tags feature
2017-04-03Clean up non TODO rubocop errorsJames Edwards-Jones
2017-04-03Moved Project#protected_branch? to ProtectedBranch, similar for tagsJames Edwards-Jones
2017-03-31Added ‘protected’ label and disabled delete button for tags index/showJames Edwards-Jones
2017-03-31Protected Tags enforced over gitJames Edwards-Jones
2017-03-13Backport changes from gitlab-org/gitlab-ee!1406Adam Niedzielski
2017-01-13Remove useless permission checks in Gitlab::Checks::ChangeAccessRémy Coutable
Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-12-20Merge remote-tracking branch 'upstream/master' into ↵Lin Jen-Shin
feature/1376-allow-write-access-deploy-keys * upstream/master: (538 commits) Reject blank environment vcariables in Gitlab::Git::RevList Add online terminal documentation Add changelog entry Add terminal UI and controller actions Fix specs Even out padding on plus button in breadcrumb menu Update font size of detail page header to 14px Update CHANGELOG.md for 8.13.10 Update CHANGELOG.md for 8.14.5 Fix Route#rename_children behavior Remove inline-block styling from status Add terminals to the Kubernetes deployment service Add a ReactiveCaching concern for use in the KubernetesService Add xterm.js 2.1.0 and a wrapper class to the asset pipeline Remove unnecessary hidden svg elements for icons. Fix consistent typo in environment.js Use a block to insert extra check for authenticate_build! Align milestone column header with count number Add Wiki import to BB importer Make CI badge hitboxes better match container ...
2016-12-16Implement final review comments from @rymai.Timothy Andrew
- `raise "string"` raises a `RuntimeError` - no need to be explicit - Remove top-level comment in the `RevList` class - Use `%w()` instead of `%w[]` - Extract an `environment_variables` method to cache `env.slice(*ALLOWED_VARIABLES)` - Use `start_with?` for env variable validation instead of regex match - Validation specs for each allowed environment variable were identical. Build them dynamically. - Minor change to `popen3` expectation.
2016-12-16Check the exit code while invoking git in the force push check.Timothy Andrew
Previously, we were calling out to `popen` without asserting on the returned exit-code. Now we raise a `RuntimeError` if the exit code is non-zero.
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-11-17We never check user privilege if it's a deploy keyLin Jen-Shin
2016-09-13Avoid protected branches checks when verifying access without branch namePaco Guzman
GitlabShell verify access sending ‘_any’ as the changes made on the git command, in those cases Gitlab::Checks::ChangeAccess won’t receive a branch_name so we don’t need to check for access to the protected branches on that repository. So we avoid some git operations in case the are not cached (empty_repo?) and some database lookups to get protected branches. These request is happening in every push.
2016-08-13Change the order of the access rules to check simpler first, and add specsAlejandro Rodríguez
2016-08-11api for generating new merge requestScott Le
DRY code + fix rubocop Add more test cases Append to changelog DRY changes list find_url service for merge_requests use GET for getting merge request links remove files rename to get_url_service reduce loop add test case for cross project refactor tiny thing update changelog
2016-07-19Limit git rev-list output count to one in forced push checkAhmad Sherif