| Commit message (Collapse) | Author | Age | Files | Lines |
| |\ |
|
| | |
| |
| |
| |
| | |
Issue: https://gitlab.com/gitlab-org/gitlab-ce/issues/12785
Merge Request: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3514
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
use ! rather than # for merge request references
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/15278
See merge request !3740
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Sanitize branch names for confidential issues
- When creating new branches for confidential issues, prefer a branch name like `issue-15` to `some-sensitive-issue-title-15`.
- The behaviour for non-confidential issues stays the same.
Closes #14566
See merge request !3671
|
| | | | |
| | | |
| | | |
| | | | |
`<id>-confidential-issue`.
|
| | |\ \ \
| | | | |
| | | | |
| | | | | |
14566-confidential-issue-branches
|
| | | | | | |
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | | |
14566-confidential-issue-branches
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Test the case where we have a referenced merge request that's being
- excluded as a "related branch"
- This took a while to figure out, especially the
`create_cross_references!` line.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Previously, the controller held the logic to calculate
related branches, which was:
`<branches ending with `issue.iid`> - <branches with a merge request referenced in the current issue>`
- This logic belongs in the `related_branches` method, not in the
controller. This commit makes this change.
- This means that `Issue#related_branches` now needs to take a `User`.
When we find the branches that have a merge request referenced in the
current issue, this is limited to merge requests that the current user
has access to.
- This is not directly related to #14566, but is a related refactoring.
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
At this point this is being handled by GitLab Runner and we need to
introduce this as a separate merge request.
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | |_|_|_|/
|/| | | | |
|
| |\ \ \ \ \
| | |_|_|/
| |/| | | |
|
| | | | | | |
|
| | |\ \ \ \
| | |_|_|/
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
Escape the query argument provided to `git grep` by `search_files`
Closes #14963.
See merge request !3633
|
| | | |/ /
| | | |
| | | |
| | | | |
Closes #14963.
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Start with iid on branch creation
After the discussion it in #3886 it was decided the iid should be in the beginning of the branch name.
See merge request !3708
|
| | | | | | |
|
| | |/ / /
| | | |
| | | |
| | | | |
Closes #13574
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix a bug with trailing slash in bamboo_url
Also, improve specs for BambooService
Similar to !3679.
See merge request !3680
|
| | | |/ /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Also, improve specs for BambooService
Similar to https://gitlab.com/gitlab-org/gitlab-ce/issues/3515
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix trailing slash in teamcity_url
Originally opened at !2309 by @ctmay4.
As described in #3515, if you have trailing spaces in the the Teamcity server name, the service
will not work properly. Switching from `URI.parse` to `URI.join` fixes it so that it works with
or without a trailing slash.
Fixes #3515.
See merge request !3679
|
| | | |/ /
| | | |
| | | |
| | | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
empty repo
To reproduce:
1. Create a project with some content
2. Rename the project
3. Create a new project with the same name.
4. Boom - 404.
After step 2, the branch and tag counts were not being cleared. This would
cause `repository.has_visible_content?` to erroneously return `true`
for the newly-created project.
Closes #13384
|
| | |\ \
| | |/ |
|
| | | |
| | |
| | |
| | | |
Closes #14961
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| | | |
| | |
| | |
| | |
| | | |
GitHub Pull Requests importer handle with the repository while
importing data, we need to make sure that the cached values are valid.
|
| | | |
| | |
| | |
| | |
| | | |
This will help us to avoid posible merge conflicts when merging
gitlab-ce to gitlab-ee
|
| | | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'master'
Allow temp-oauth-email as notification email
Closes #14559
/cc @dblessing @rymai
See merge request !3477
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I’ve removed everything related to the feature based on this commit:
ce08f919f34fd8849834365
Resolves #10857.
|
| | | |/ |
|
| | | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Destroy related todos when an Issue/MR is deleted
Closes #14550
Closes #14598
See merge request !3376
|
| | | | | |
|
| | | |\ \
| | | | |
| | | | |
| | | | |
| | | | | |
Expire the exists cache before deletion to ensure project dir actually exists
See merge request !3413
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Closes #14659
|
| | | | |/
| | |/| |
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | | | |
| | | |
| | | |
| | | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
It will hold notification setting per group or per project. It will
allow get rid of notification level stored in Member model
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Ensuring Merge Request API returns boolean values for work_in_progress
Fixes #14692.
See merge request !3432
|
| | | |/
| | |
| | |
| | | |
Fixes #14692
|