- 26 6月, 2019 1 次提交
-
-
由 Lin Jen-Shin 提交于
Copy inflections from EE See merge request gitlab-org/gitlab-ce!30041
-
- 25 6月, 2019 39 次提交
-
-
由 Marcia Ramos 提交于
Resolve "Docs feedback: revise operations dashboard" Closes #60697 See merge request gitlab-org/gitlab-ce!30038
-
由 Marcia Ramos 提交于
Add code comments development guide Closes #63132 See merge request gitlab-org/gitlab-ce!30043
-
由 Filipa Lacerda 提交于
(CE Port) Set project path on localStorage during onboarding See merge request gitlab-org/gitlab-ce!29989
-
由 Martin Wortschack 提交于
-
由 Filipa Lacerda 提交于
Resolve "Follow-up from "Use scoped routes for labels and milestones"" Closes #63177 See merge request gitlab-org/gitlab-ce!29983
-
由 Grzegorz Bizon 提交于
Pipeline must be present if "Pipeline must succeed" is set See merge request gitlab-org/gitlab-ce!29926
-
由 Filipa Lacerda 提交于
Move vuex action helper spec to Jest See merge request gitlab-org/gitlab-ce!29653
-
由 Mark Florian 提交于
This is largely a straight-forward copy of the Karma spec, with the usual Karma->Jest necessary changes. This also fixes a bug in the implementation that was causing the tests to fail, when run on Jest/node, whereby actions that return rejected promises would always fail the given test. This was due to those rejections not being caught in the same call stack in which they were created.
-
由 Marcia Ramos 提交于
Clarify that this.something is not available in Jest (docs) Closes #24809 See merge request gitlab-org/gitlab-ce!29887
-
由 Winnie Hellmann 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Robert Speicher 提交于
-
由 Marcia Ramos 提交于
Clarify that Jest does not use Webpack (docs) See merge request gitlab-org/gitlab-ce!30000
-
由 Winnie Hellmann 提交于
-
由 Achilleas Pipinellis 提交于
-
由 Bob Van Landuyt 提交于
Upgrade Gitaly to v1.49.0 Closes gitaly#1738 See merge request gitlab-org/gitlab-ce!29990
-
由 GitalyBot 提交于
The setup was wrong, and due to Gitaly being a bit more strict it had to match up. The test is now accurate and passing again.
-
由 Rémy Coutable 提交于
Silence backup warnings when CRON=1 in use Closes #63703 See merge request gitlab-org/gitlab-ce!30033
-
由 Achilleas Pipinellis 提交于
Mention what tools are not supported in Dependency Scanning See merge request gitlab-org/gitlab-ce!30030
-
由 Andreas Brandl 提交于
CE backport: Resolve "Make "Create an issue" default for Incident Management" See merge request gitlab-org/gitlab-ce!29747
-
由 Peter Leitzen 提交于
This reverts commit 51340f9b47e8339cdabce11d0a17ac724278bff0.
-
由 Rémy Coutable 提交于
Prevent EE backport migrations from running if CE is not migrated Closes #63612 See merge request gitlab-org/gitlab-ce!30002
-
由 Lin Jen-Shin 提交于
Improve Review Apps cleanup when previous deployment failed by only issuing an `helm delete` command Closes #63639 and #62161 See merge request gitlab-org/gitlab-ce!28661
-
由 Stan Hu 提交于
If CRON=1 is in use, we shouldn't generate any output or admins may be notified via e-mail about unnecessary warnings. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63703
-
由 Fabio Pitino 提交于
-
由 Stan Hu 提交于
If a user upgraded to any GitLab 11.x EE version but switched back to CE, it's possible the state of the EE tables are not in the right state for the EE backport migration to work properly. In particular, there were three tables that had trouble: * epics * geo_event_log * vulnerability_feedback The EE backport migration would fail while trying to add foreign key constraints because a key didn't exist in the table. This happens because any EE migration that add or removed columns between v11.0.0 and v11.11.3 are not guaranteed to be applied in an CE installation. The EE backport schema does not individually backport these migrations. We now check if certain columns are present to determine whether the backport migration is in the proper state. CE users are required to upgrade to v11.11.3 EE if they ever installed EE previously before they can go back to v12.x CE. Tested via: ``` git checkout -f v11.0.0-ee bundle exec rake db:reset git checkout .; git checkout -f v11.11.3 bundle exec rake db:migrate git checkout .; git checkout -f v12.0.0 bundle exec rake db:migrate <failure happens> ```
-
由 Achilleas Pipinellis 提交于
-
由 Kushal Pandya 提交于
Keep empty folders in the tree list Closes #60860 See merge request gitlab-org/gitlab-ce!29196
-
由 Lin Jen-Shin 提交于
Merge branch '62735-for-stable-branches-build-cng-images-from-corresponding-stable-branches-in-cng-mirror-project' into 'master' Pass branch name to the CNG pipeline for stable branches See merge request gitlab-org/gitlab-ce!29617
-
由 Kamil Trzciński 提交于
Update GitLab Runner Helm Chart to 0.6.0/12.0.0 See merge request gitlab-org/gitlab-ce!29982
-
由 Denys Mishunov 提交于
When removing the last file from a folder in WebIDE, do not remove the folder from the view. We keep those to give users possibility to re-upload files to the same folders. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60860
-
由 Kushal Pandya 提交于
Allow autocompleting labels using colons and spaces Closes #63343 and #56510 See merge request gitlab-org/gitlab-ce!29749
-
由 Martin Hanzel 提交于
The `:` key will no longer exit out of the autocomplete dialog, allowing auto-completion of labels with colons in them.
-
由 Kamil Trzciński 提交于
Add gem size information to metrics.txt in memory CI artifacts See merge request gitlab-org/gitlab-ce!29827
-
由 Nick Thomas 提交于
Use project depended feature flag for pages ssl and get certificates only for enabled domains See merge request gitlab-org/gitlab-ce!29609
-
由 Rémy Coutable 提交于
Refactor AfterCommitQueue.inside_transaction? See merge request gitlab-org/gitlab-ce!29903
-
由 Andrew Newdigate 提交于
This is a small change to move AfterCommitQueue.inside_transaction? to Gitlab::Database.inside_transaction? Since this change is required by different changes which may not arrive in sequence, it's easier to extract this change out on it's own.
-
由 Fabio Pitino 提交于
When a user sets only_allow_merge_if_pipeline_succeeds, also named as "Pipeline must succeed" project setting, we require the pipeline to be present. This solves race condition issues especially with external CI providers when a build is triggered externally but no pipelines are created in GitLab yet. Document that a head pipeline is expected when using "Pipeline must succeed" setting. Also explain limitations with the use of only/except where there may not be any jobs created and the merge request will not be allowed to be merged.
-
由 Rémy Coutable 提交于
Signed-off-by: NRémy Coutable <remy@rymai.me>
-