Age | Commit message (Collapse) | Author |
|
Document how to enable/disable Auto DevOps at the instance level
Closes #49820
See merge request gitlab-org/gitlab-ce!21139
|
|
|
|
|
|
|
|
|
|
The pngquant tool was used https://pngquant.org, and particularly, the
following command:
/usr/bin/pngquant -f --skip-if-larger --ext .png --speed 1 image.png
Before: 47584K
After : 34924K
|
|
|
|
|
|
Closes #49733
|
|
Add /-/health basic health check endpoint
See merge request gitlab-org/gitlab-ce!20456
|
|
These checks were a no op on Cloud native environments, and the checks
were migrated as part of:
https://gitlab.com/gitlab-org/gitaly/merge_requests/767
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/49725
|
|
|
|
The previous implementation would hit the database each time
and provide a dummy response. If the database goes down, this
means all application workers would be taken out of service.
Simplify this check by using a Rails middleware that intercepts
this endpoint and returns a 200 response.
|
|
|
|
|
|
When a user checks the `accept` checkbox, we will track that
acceptance as usual. That way they don't need to accept again after
they complete the registration.
When an unauthenticated user visits the `/-/users/terms` page, there
is no button to accept, decline or continue. The 'current-user menu'
is also hidden from the top bar.
|
|
|
|
|
|
This enforces the terms in the web application. These cases are
specced:
- Logging in: When terms are enforced, and a user logs in that has not
accepted the terms, they are presented with the screen. They get
directed to their customized root path afterwards.
- Signing up: After signing up, the first screen the user is presented
with the screen to accept the terms. After they accept they are
directed to the dashboard.
- While a session is active:
- For a GET: The user will be directed to the terms page first,
after they accept the terms, they will be directed to the page
they were going to
- For any other request: They are directed to the terms, after they
accept the terms, they are directed back to the page they came
from to retry the request. Any information entered would be
persisted in localstorage and available on the page.
|
|
|
|
Resolve "Allow HTTPS cloning by Runners if it is disabled for users"
Closes #44389
See merge request gitlab-org/gitlab-ce!18021
|
|
|
|
Fix https://gitlab.com/gitlab-org/gitlab-ee/issues/4474
Conflicts:
db/schema.rb
ee/app/controllers/ee/admin/application_settings_controller.rb
ee/app/helpers/ee/application_settings_helper.rb
ee/app/models/ee/application_setting.rb
ee/app/models/license.rb
ee/app/views/layouts/service_desk.html.haml
ee/app/views/notify/approved_merge_request_email.html.haml
ee/app/views/notify/service_desk_new_note_email.text.erb
ee/app/views/notify/service_desk_thank_you_email.text.erb
ee/app/views/notify/unapproved_merge_request_email.html.haml
ee/lib/ee/api/entities.rb
ee/spec/controllers/admin/application_settings_controller_spec.rb
ee/spec/models/application_setting_spec.rb
ee/spec/requests/api/settings_spec.rb
lib/api/settings.rb
spec/mailers/previews/notify_preview.rb
|
|
|
|
This reverts merge request !17257
|
|
|
|
|
|
[skip ci]
|
|
|
|
|
|
|
|
+ fix typos, and capitalization
+ point configuration to `gitlab.rb` as well
|
|
|
|
as deprecated
|
|
|
|
|
|
|
|
|
|
|
|
Setting `usage_ping_enabled` to false in `gitlab.yml`:
1. Disables the usage ping, regardless of the value stored in the database.
2. Prevents the usage ping from being enabled through the admin panel. It can
only be enabled by either removing the line from `gitlab.yml` and configuring
through the admin panel, or setting it to true in `gitlab.yml`.
|
|
|
|
|
|
|
|
|
|
|
|
We needed to clarify what inactive users are.
|
|
|
|
|
|
|
|
|