- 09 Nov, 2021 40 commits
-
-
Natalia Tepluhina authored
Enable on-demand scans index page See merge request gitlab-org/gitlab!73944
-
Paul Gascou-Vaillancourt authored
-
Thong Kuah authored
Experiment: Add user invitation in-product marketing email See merge request gitlab-org/gitlab!72470
-
Eugie Limpin authored
Update group create service to enqueue a background job to send an invite team email 20 minutes after a root group is created. Update EmailCampaignsController to handle CTA clicks from invite team emails. Changelog: added
-
Fiona Neill authored
Add basics for reporting snippets as spam See merge request gitlab-org/gitlab!72810
-
Amy Qualls authored
-
Adam Hegyi authored
Add indexes to aggregated VSA tables See merge request gitlab-org/gitlab!73427
-
Marcel Amirault authored
Updated executor info See merge request gitlab-org/gitlab!74028
-
Suzanne Selhorn authored
-
Kati Paizee authored
Rotate a documentation deployment diagram See merge request gitlab-org/gitlab!74034
-
Adam Hegyi authored
This change adds DB indexes to the new, aggregated value stream analytics tables. Changelog: added
-
Ash McKenzie authored
Make it easier to use Snowplow Micro in development See merge request gitlab-org/gitlab!72838
-
Dylan Griffith authored
The `use_model_load_balancing` results in a wrong sticking context used See merge request gitlab-org/gitlab!73949
-
Ash McKenzie authored
Enable gitlab-docs project in GDK for Gitpod environments See merge request gitlab-org/gitlab!73916
-
Kushal Pandya authored
Adds tracking to create file button in widget See merge request gitlab-org/gitlab!73762
-
Alex Pooley authored
Use allowlist for importing project attributes See merge request gitlab-org/gitlab!72457
-
Marcel Amirault authored
Update the sidekiq multi-process/concurrency docs See merge request gitlab-org/gitlab!73698
-
Craig Miskell authored
-
Heinrich Lee Yu authored
Shift the user's contribution calendar based on their timezone setting See merge request gitlab-org/gitlab!72938
-
Evan Read authored
Add & update security considerations for PATs See merge request gitlab-org/gitlab!73696
-
Nick Malcolm authored
-
Mark Chao authored
Reset GitlabSubscription seats when starting a new term See merge request gitlab-org/gitlab!73078
-
Ezekiel Kigbo authored
Add IaC scanning to Security Configuration page See merge request gitlab-org/gitlab!73155
-
Tiger Watson authored
feat: Set PersonalAccessToken default prefix See merge request gitlab-org/gitlab!73314
-
Krasimir Angelov authored
Fix fake connection leaking for Ci::ApplicationRecord See merge request gitlab-org/gitlab!74032
-
Evan Read authored
Add another error message to SAML troubleshooting section See merge request gitlab-org/gitlab!73157
-
Asmaa Hassan authored
-
Ash McKenzie authored
Add UX reviewer/maintainer to Danger bot See merge request gitlab-org/gitlab!51127
-
Thong Kuah authored
Fix merge requests not importing for older projects See merge request gitlab-org/gitlab!74031
-
Evan Read authored
-
Stan Hu authored
This restores the merge request commit user fields in import_export.yml for the import case. https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73307 dropped these YAML fields because supposedly the import would fail if the database columns didn't exist, but I haven't found that to be the case. I tested with an import with: 1. Project generated in v13.12 that had these columns. 2. Project generated with the latest nightly build. The import works in either case because we call `MergeRequestDiffCommit.new` with the sanitized attributes in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73307. Based on the discussion in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72219, these attributes are needed for **import** but excluded for **export**. I think Yorick might have assumed that since the code in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73307 manually removed these fields, we wouldn't need them anymore. However, without these attributes, imports were failing to import with an older GitLab version (e.g. v13.12) because the attributes were sanitized before the importer got a chance to use them. Changelog: fixed
-
Ash McKenzie authored
-
Austin Regnery authored
-
Austin Regnery authored
-
Austin Regnery authored
-
Austin Regnery authored
-
Austin Regnery authored
-
Austin Regnery authored
Changelog: changed
-
Austin Regnery authored
-
Thong Kuah authored
After the example has run, the Ci::ApplicationRecord#connection_specification_name remained stuck as "Ci::ApplicationRecord" instead of reverting back to "ActiveRecord::Base". We call model.remove_connection to fix this. Also, there is no need to setup a (fake) ci connection, if we already have one
-