Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-03-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-05 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-03-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-27 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-16 | Add latest changes from gitlab-org/gitlab@masterogolowinski-master-patch-80898 | GitLab Bot | |
2019-12-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-12-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-26 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-15 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-11-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-30 | Merge dev.gitlab.org@master into GitLab.com@master | Yorick Peterse | |
2019-10-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-24 | Only assign merge params when allowed | Bob Van Landuyt | |
When a user updates a merge request coming from a fork, they should not be able to set `force_remove_source_branch` if they cannot push code to the source project. Otherwise developers of the target project could remove the source branch of the source project by setting this flag through the API. | |||
2019-10-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-18 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-07 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-10-03 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-09-12 | Fix create MR from issue using a tag as ref | 🙈 jacopo beschi 🙉 | |
Creating a MR from an issue using a tag as ref correctly creates the source branch starting from the tag. | |||
2019-09-11 | Enables Run Pipeline button to be rendered | Filipa Lacerda | |
In the Merge Request view, under pipelines tab the user can see a run pipeline button Adds axios post request to button click Adds the logic to handle the user click, refresh the table and disable the button while thee request is being made Updates UI for desktop and mobile Adds specs Regenerates potfile Follow-up after review Uses .finally to avoid code repetition | |||
2019-09-10 | Merge branch 'fj-62807-not-prefill-target-branch' into 'master' | Lin Jen-Shin | |
Avoid filling target branch when unknown and source is default branch Closes #62807 See merge request gitlab-org/gitlab-ce!32701 | |||
2019-09-10 | Avoid setting merge request target branch when source if default branch | Francisco Javier López | |
In case the source and the target project are the same, the source branch is the default branch, and the target branch is not present, we will avoid prefilling the target branch with the repository default branch. Letting the user decide. | |||
2019-09-04 | Support adding and removing labels w/ push opts | Christian Couder | |
MergeRequests::PushOptionsHandlerService has been updated to allow adding and removing labels to a merge request using git push options. To create a new merge request and add 2 labels to it: git push -u origin -o merge_request.create \ -o merge_request.label="My label 1" \ -o merge_request.label="My label 2" To update an existing merge request and remove a label while adding a different label: git push -u origin -o merge_request.label="My added label" \ -o merge_request.unlabel="My removed label" Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/64320 | |||
2019-08-26 | Add usage pings for merge request creating | Igor | |
Code Review Usage Ping for Create SMAU | |||
2019-08-15 | Only read rebase status from the model | Nick Thomas | |
Prior to 12.1, rebase status was looked up directly from Gitaly. In https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14417 , a DB column was added to track the status instead. However, we couldn't stop looking at the gitaly status immediately, since some rebases may been running across the upgrade. Now that we're in 12.3, it is safe to remove the direct-to-gitaly lookup. This also happens to fix a 500 error that is seen when viewing an MR for a fork where the source project has been removed. We still look at the Gitaly status in the service, just in case Gitaly and Sidekiq get out of sync - I assume this is possible, and it's a relatively cheap check. Since we atomically check and set `merge_requests.rebase_jid`, we should never enqueue two `RebaseWorker` jobs in parallel. | |||
2019-08-01 | Add exclusive lease to mergeability check process | Oswaldo Ferreira | |
Concurrent calls to UserMergeToRef RPC updating a single ref can lead to an opaque fail that is being rescued at Gitaly. So this commit adds an exclusive lease to the mergeability check process with the key as the current MR ID. |