| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
| |
This reverts merge request !26481
|
| |
|
|
| |
spec/features/groups/group_page_with_external_authorization_service_spec to EE
|
| |
|
|
|
| |
Backports https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10161
(code out of ee/ folder).
|
| |
|
| |
This reverts merge request !26823
|
| |
|
|
| |
spec/features/groups/group_page_with_external_authorization_service_spec to EE
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/59777.
In earlier iterations of our implementation of Git object deduplication
we thought we would be making extensive use of Git remotes in pool
repositories in the future, and that we should manage these remotes
carefully from the start. We now expect we only care about one remote,
namely the source project. The other remotes are there only for forensic
purposes.
Before this MR we tried to also remove pool remotes when member projects
got deleted, with the UnlinkRepositoryFromObjectPool RPC. This is
fragile when there are race conditions (see
https://gitlab.com/gitlab-org/gitaly/issues/1568#note_153955926). We
have spent some time making this RPC less fragile in
https://gitlab.com/gitlab-org/gitaly/merge_requests/1151 but looking at
this problem again, I think we should just stop calling it.
|
| | |
|
| |
|
|
|
|
| |
If the requested visibility levels contains only public and/or internal,
omitting private, then we can skip the EXISTS query to search for
private projects for the user.
|
| |
|
|
|
|
|
|
|
|
| |
Previously when a user requested a list of projects,
`Project#public_or_visible_to_user` would search all authorized projects
and public/internal projects as well. However, when a user requests a
specific `visibility_level` (e.g. private), that should reduce the
search space, and we shouldn't need to load public/internal projects.
Improves https://gitlab.com/gitlab-org/gitlab-ce/issues/59329
|
| |
|
|
|
|
|
|
| |
This changes the repository type from a binary `wiki?` to a type. So
we can have more than 2 repository types.
Now everywhere we called `.wiki?` and expected a boolean, we check
that type.
|
| |\
| |
| |
| |
| |
| |
| | |
Refresh commit count after repository head changes
Closes #59346
See merge request gitlab-org/gitlab-ce!26473
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Refactor groups and projects boards actions
See merge request gitlab-org/gitlab-ce!25568
|
| | | |
| | |
| | |
| | | |
We already check max boards in the create service. This is not used.
|
| |/ / |
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
- Includes instance methods on Group model to detect when a group has
AutoDevOps explicitly/implicitly enabled/disabled.
- Includes migration to add a new column to namespaces table
- Add UI necessary modifications
- Add service and controller to update auto devops
related instances
- Updates project and groups auto devops badges
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/52447
|
| |
|
|
|
| |
This style change enforces `return if ...` instead of
`return nil if ...` to save maintainers a few minor review points
|
| |
|
|
|
|
| |
This makes code to support encrypted runner tokens.
This code also finished previously started encryption
process.
|
| |
|
|
|
| |
Moved to HashedStorage namespace, and added them to the
`:hashed_storage` queue namespace
|
| |
|
|
|
|
|
| |
We are adding sidekiq workers and service classes to allow to rollback
a hashed storage migration. There are some refactoring involved as well
as part of the code can be reused by both the migration and the rollback
logic.
|
| |\
| |
| |
| |
| |
| |
| | |
Resolve "Project fetch statistics API (HTTP only)"
Closes #42086
See merge request gitlab-org/gitlab-ce!23596
|
| | |
| |
| |
| |
| |
| | |
The API get projects/:id/traffic/fetches allows user with write
access to the repository to get the number of clones for the
last 30 days.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Revert "Merge branch 'revert-82d7b5a0-ce' into 'master'"
Closes #57857 and #50747
See merge request gitlab-org/gitlab-ce!25559
|
| | | |
| | |
| | |
| | |
| | | |
Fix misspellings in app/spec comments
See merge request gitlab-org/gitlab-ce!25517
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Added YouTrack integration
Closes #42595
See merge request gitlab-org/gitlab-ce!25361
|
| | | |/
| |/|
| | |
| | | |
Fixes gitlab-org/gitlab-ce#42595
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Support merge ref writing (without merging to target branch)
Closes #47110
See merge request gitlab-org/gitlab-ce!24692
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds the ground work for writing into
the merge ref refs/merge-requests/:iid/merge the
merge result between source and target branches of
a MR, without further side-effects such as
mailing, MR updates and target branch changes.
|
| | |_|/
|/| | |
|
| |/ /
| |
| |
| |
| | |
This reverts commit 9202bbd129537a698b986e6295d0c783b5a84815, reversing
changes made to 4b282e9ce1ae246c4538b3ede18d1380ea778029.
|
| |\ \
| | |
| | |
| | |
| | | |
Delegate last_pipeline to Project
See merge request gitlab-org/gitlab-ce!25422
|
| | |/ |
|
| | |
| |
| |
| |
| |
| | |
Pipeline status was showing failed on projects when CI was disabled.
This checks to see if the feature is enabled before showing the status.
|
| |/
|
|
| |
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| | |
|
| | |
|
| |
|
|
| |
This makes it easier to access other project arguments in the future.
|
| |
|
|
|
|
|
| |
When hashed storage is in use, it's helpful to have the project
name associated with the request.
Closes https://gitlab.com/gitlab-org/gitaly/issues/1394
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Group guests will only be displayed merge requests to
projects they have a access level to, higher than Reporter.
Visible projects will still display the merge requests to Guests
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Reduce amount of locks needed for GitHub importer
Closes #54270 and #51817
See merge request gitlab-org/gitlab-ce!24102
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
After the import has finished, we flush (delete) the InternalId records
related to the project at hand. This means we're starting over with
tracking correct internal id values, a new record will be created
automatically when the next internal id is generated.
The GitHub importer assigns iid values by using supplied values from
GitHub. We skip tracking internal id values during the import in favor
of higher concurrency. Deleting any InternalId records after the import
has finished is an extra measure to guarantee consistency.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54270.
|
| |/ |
|
| |\
| |
| |
| |
| | |
Refactor checking personal project limits
See merge request gitlab-org/gitlab-ce!24396
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This refactors the code used for checking if a user has exceeded the
personal projects limit. As part of this refactor the method has been
renamed from Project#check_limit to "check_personal_projects_limit", as
this name makes it much more clear what the purpose of the method is.
Standalone unit tests have also been added, as before we only had a
single generic validation test that did not cover all cases.
The old implementation of the refactored method also included a `rescue`
statement. This code would only run when a project creator was not set.
The error that would be added wasn't super useful, especially since
there would already be errors for the creator not being present. As none
of the other code in the "check_personal_projects_limit" raises, it has
been removed.
|
