- 29 Aug, 2019 1 commit
-
-
GitLab Release Tools Bot authored
Avoid exposing unaccessible repo data upon GFM post processing See merge request gitlab/gitlab-ee!1235
-
- 28 Aug, 2019 2 commits
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
- 27 Aug, 2019 4 commits
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
- 26 Aug, 2019 7 commits
-
-
Oswaldo Ferreira authored
When post-processing relative links to absolute links RelativeLinkFilter didn't take into consideration that internal repository data could be exposed for users that do not have repository access to the project. This commit solves that by checking whether the user can `download_code` at this repository, avoiding any processing of this filter if the user can't. Additionally, if we're processing for a group ( no project was given), we check if the user can read it in order to expand the href as an extra. That doesn't seem necessarily a breach now, but an extra check doesn't hurt as after all the user needs to be able to `read_group`.
-
GitLab Bot authored
-
Ash McKenzie authored
Bump ruby-prof to 1.0.0 See merge request gitlab-org/gitlab-ce!29588
-
Thong Kuah authored
Install Unleash Client Gem See merge request gitlab-org/gitlab-ce!32065
-
Jason Goodman authored
-
GitLab Bot authored
-
Ash McKenzie authored
Backport expired job artifact trait See merge request gitlab-org/gitlab-ce!32179
-
- 25 Aug, 2019 5 commits
-
-
GitLab Bot authored
-
Stan Hu authored
Add helpers to exactly undo cleanup_concurrent_column_rename See merge request gitlab-org/gitlab-ce!32183
-
Reuben Pereira authored
- Also add helper to undo rename_column_concurrently.
-
Stan Hu authored
Add helper to exactly undo cleanup_concurrent_column_rename See merge request gitlab-org/gitlab-ee!15614
-
Reuben Pereira authored
- Also add helper to undo rename_column_concurrently.
-
- 24 Aug, 2019 15 commits
-
-
Stan Hu authored
This is significant improvement over the previous releases: https://github.com/ruby-prof/ruby-prof/blob/master/CHANGES
-
Gabriel Mazetto authored
-
GitLab Bot authored
-
Fatih Acet authored
Resolve "Show the paths for groups in productivity analytics" Closes #13637 See merge request gitlab-org/gitlab-ee!15513
-
Martin Wortschack authored
- Add changelog entry - Add specs for displaying the full group path - Add selector to component
-
Stan Hu authored
Preload tags when loading Ci::Pipeline Closes #60925 See merge request gitlab-org/gitlab-ce!32149
-
GitLab Bot authored
-
Fatih Acet authored
Fix Serverless entry page layout Closes #64764 See merge request gitlab-org/gitlab-ce!32029
-
Fatih Acet authored
Moves container scanning logic to the backend Closes #13518 See merge request gitlab-org/gitlab-ee!15226
-
Sam Beckham authored
- Uses the baceng API to parse container scanning logic on the MR page. - Maps the slightly misaligned data in the vulnerabilities - Uses polling because the end point is a polling one - Adds an action for storing the endpoint in vuex - Adds a new action for calling the endpoint - Puts all the above behind a feature flag - Adds action tests - Adds mutation tests - Adds component tests - Fixes issues the tests brought up - - Text generation failed without a head or base path - - Report visibilty failed without a head or base path
-
GitLab Bot authored
-
Tim Zallmann authored
Enable line charts in dashbaord panels and embedded charts Closes #66073 See merge request gitlab-org/gitlab-ce!31920
-
GitLab Bot authored
-
Stan Hu authored
Delete rename trigger before creating to prevent error See merge request gitlab-org/gitlab-ce!32147
-
Reuben Pereira authored
- When renaming a column concurrently, drop any existing trigger before attempting to create a new one. When running migration specs multiple times (as it happens during local development), the down method of previous migrations are called. If any of the called methods contains a call to rename_column_concurrently, a trigger will be created and not removed. So, the next time a migration spec is run, if the same down method is executed again, it will cause an error when attempting to create the trigger (since it already exists). Dropping the trigger if it already exists will prevent this problem.
-
- 23 Aug, 2019 6 commits
-
-
GitLab Bot authored
-
Mayra Cabrera authored
Add migration to execute SelfMonitoring::Project::CreateService See merge request gitlab-org/gitlab-ce!31389
-
Reuben Pereira authored
Add to the service and migration both.
-
Mayra Cabrera authored
Migration to execute SelfMonitoring::Project::CreateService See merge request gitlab-org/gitlab-ee!15071
-
Reuben Pereira authored
- Add code of SelfMonitoring::Project::CreateService to the migration since our policy is not to rely on application code in migrations.
-
GitLab Bot authored
-