Age | Commit message (Collapse) | Author | |
---|---|---|---|
2023-07-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-05-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-04-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-04-15 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-03-23 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-03-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2023-02-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-09-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-12-22 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-11-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-10-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-09-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-08-30 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-05-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-05-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-04-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-04-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-10-20 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-08-17 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-06-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-04-12 | Add frozen_string_literal to spec/services | Thong Kuah | |
Probably useful as we often move these files to "new" files. | |||
2019-04-05 | Fenced blockquotes to not change source line pos | Brett Walker | |
Replaces blockquote fences with \n, keeping the line numbering intact. | |||
2019-02-14 | Check issue milestone availability | Jarka Košanová | |
Add project when creating milestone in specs We validate milestone is from the same project/parent group as issuable -> we need to set project in specs correctly Improve methods names and specs organization | |||
2017-12-22 | Replace '.team << [user, role]' with 'add_role(user)' in specs | blackst0ne | |
2017-07-27 | Remove superfluous lib: true, type: redis, service: true, models: true, ↵ | Rémy Coutable | |
services: true, no_db: true, api: true Signed-off-by: Rémy Coutable <remy@rymai.me> | |||
2017-05-10 | Enable the Style/TrailingCommaInArguments cop | Rémy Coutable | |
Use the EnforcedStyleForMultiline: no_comma option. Signed-off-by: Rémy Coutable <remy@rymai.me> | |||
2017-04-05 | Fix specs | Douwe Maan | |
2017-04-05 | Add specs | Douwe Maan | |
2017-04-05 | Add option to start a new discussion on an MR | Douwe Maan | |
2017-03-28 | Use `:empty_project` where possible in service specs | Robert Speicher | |
2017-03-13 | Rename variable | Bob Van Landuyt | |
merge_request_for_resolving_discussions -> merge_request_to_resolve_discussions_of | |||
2017-03-13 | Correctly indent quotes in new issue description | Bob Van Landuyt | |
By using `>`-quote style instead of `>>>`. Also: Update documentation images. | |||
2017-03-13 | Always require MR-iid for resolving discussions | Bob Van Landuyt | |
And deduplicate the finding of MR's & discussions. Now the searching is done in the service, istead of the controller & the API. | |||
2017-03-13 | Delegate a single discussion to a new issue | Bob Van Landuyt | |
Delegate a discussion in a merge request into a new issue. The discussion wil be marked as resolved and a system note will be added linking to the newly created issue. | |||
2017-02-12 | fix issue creation from milestone doesn't assign the milestone | wendy0402 | |
2016-12-05 | Feature: delegate all open discussions to Issue | Bob Van Landuyt | |
When a merge request can only be merged when all discussions are resolved. This feature allows to easily delegate those discussions to a new issue, while marking them as resolved in the merge request. The user is presented with a new issue, prepared with mentions of all unresolved discussions, including the first unresolved note of the discussion, time and link to the note. When the issue is created, the discussions in the merge request will get a system note directing the user to the newly created issue. |