An error occurred fetching the project authors.
- 10 Mar, 2021 1 commit
-
-
James Fargher authored
This reverts commit 644e74d8.
-
- 03 Mar, 2021 1 commit
-
-
Kyle Wiebers authored
This reverts merge request !53803
-
- 02 Mar, 2021 3 commits
-
-
James Fargher authored
Running the admin form off of the hstore directly should allow us to synchronise the database more easily with any storage config changes.
-
James Fargher authored
-
James Fargher authored
-
- 01 Mar, 2021 1 commit
-
-
Douglas Barbosa Alexandre authored
Revert https://gitlab.com/gitlab-org/gitlab/-/merge_requests/50824 but keep the application handling both versions.
-
- 17 Feb, 2021 1 commit
-
-
Guillaume Grossetie authored
- Add excalidraw as a supported diagram https://github.com/Mogztter/asciidoctor-kroki/releases/tag/ruby-v0.3.0
-
- 11 Feb, 2021 2 commits
-
-
charlie ablett authored
- remove _raw from places - Add tiny test helper method - Downcase upon storage and comparison
-
Eugenia Grieff authored
- Add new column to applicaton_settings table - Use the new settings value in rate limit checks
-
- 09 Feb, 2021 1 commit
-
-
Eugenia Grieff authored
- Add creation limit to notes controller - Add creation limit to notes API endpoint - Add new column to application settings - Add new settings to Network template - Add specs Add rate limit to GraphQL endpoint
-
- 03 Feb, 2021 1 commit
-
-
Tan Le authored
We would like to use a more neutral tone when specifying a list of allowed asset proxies. This change renames the `asset_proxy_whitelist` column in `application_settings` table to `asset_proxy_allowlist`. The ApplicationSettings API is still backward-compatible with the old field.
-
- 12 Jan, 2021 1 commit
-
-
George Koltsov authored
- Change `max_import_size` from 50 to 0 so it is unlimited, instead of being too big of a restriction by default
-
- 11 Jan, 2021 1 commit
-
-
Alex Buijs authored
And remove feature flag
-
- 01 Jan, 2021 1 commit
-
-
Sean McGivern authored
When a request exceeds a rate limit configured in the admin panel, we default to returning a 429 response with a plain-text body of 'Retry later'. This change allows the response body to be customised - although it must still be plain text - which allows, for example, GitLab.com to provide a link to GitLab.com-specific rate limiting documentation.
-
- 15 Dec, 2020 1 commit
-
-
Max Wittig authored
This feature makes it easier to spot GitLab tokens by adding a prefix, which makes easier to identify and revoke them. Similar to how AWS does it with their access keys, e.g. AKIAIOSFODNN7EXAMPLE
-
- 07 Dec, 2020 1 commit
-
-
Joern Schneeweisz authored
-
- 25 Nov, 2020 2 commits
-
-
Guillaume Grossetie authored
-
Guillaume Grossetie authored
-
- 16 Nov, 2020 1 commit
-
-
Serena Fang authored
Rebase with master Add changelog entry Change column default from false to true Add stub require admin approval false Stub setting before all Test new context Not ready for review just saving Remove extra spaces Stub application setting in the right place Add new spec for admin approval true Add specs for require admin approval true Not quite ready for review, will rearrange tests Stub application setting Change some specs Reword some spcs Remove extra new user signups cap Rerun db migrate Change settings spec Use with lock retries Remove extra new line Rearrange db structure Readd deleted migration Remove with lock retries
-
- 10 Nov, 2020 1 commit
-
-
Doug Stull authored
- follow our diversity and inclusion guidelines.
-
- 29 Oct, 2020 1 commit
-
-
Doug Stull authored
- more inclusive language.
-
- 26 Oct, 2020 1 commit
-
-
David Fernandez authored
By using a limited capacity worker and dedicated database column on container repositories to mark them as: * cleanup_scheduled: waiting for a worker pickup (happens after a cleanup policy execution) * cleanup_ongoing: worker cleaning up this repository * cleanup_unfinished: worker cleaned part of the repository but had to stop * cleanup_unscheduled: nothing to do
-
- 15 Oct, 2020 1 commit
-
-
Manoj M J authored
This change allows admins to approve pending users via the Admin UI
-
- 05 Oct, 2020 1 commit
-
-
Vasilii Iakliushin authored
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/32328 * Add `help_page_documentation_base_url` to `application_settings` table * Add missing locales and refresh graphql schema * Add a feature flag for documentation redirects * Hide documentation URL field when feature flag is disabled
-
- 16 Sep, 2020 1 commit
-
-
Cornelius Ludmann authored
- Introduces :gitpod feature flag - A later MR will handle adding to the MR page https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37985
-
- 09 Sep, 2020 1 commit
-
-
Alper Akgun authored
-
- 02 Sep, 2020 1 commit
-
-
David Fernandez authored
The duration used for the timeout is the new application setting `container_registry_delete_tags_service_timeout` Add UI for this setting Add the relevant documentation change This change is gated behind a feature flag: `container_registry_expiration_policies_throttling` (see https://gitlab.com/gitlab-org/gitlab/-/issues/238190)
-
- 21 Aug, 2020 1 commit
-
-
Magdalena Frankiewicz authored
Remove analytics icon from top nav bar Move Cohorts and DevOps Score pages to Admin panel under Analytics submenu Keep old paths but redirect to new pages under /admin Make sure that Cohorts and DevOps Score are visible only to Admin, remove a toggle that was enabling instance statistics to be seen by not admin user Ignore instance_statistics_visibility_private column as the first step to drop it, remove obsolete condition from global policy and ignored application setting
-
- 04 Aug, 2020 3 commits
-
-
Uday Aggarwal authored
-
Nicolas Dular authored
This removes the frontend and backend that is related to the namespace storage limit setting. For the MVC we initially thought that the limit will be instance wide, this requirement changed though and it is now based on the plan of a namespace. To remove the column from the db, we for now ignore the column and will do the actual removal of the column the next release.
-
Uday Aggarwal authored
-
- 31 Jul, 2020 1 commit
-
-
Tyler Amos authored
Puts application settings in alphabetical order for defaults and api documentation. These were mostly in order already but this fixes the exceptions. Sorted using VSCode's "Sort Lines Ascending" command palette feature.
-
- 21 Jul, 2020 1 commit
-
-
John Cai authored
When modifying repository_storages_weighted through the api, the value gets passed as a string, so we need to coerce it into an integer. repository_storages is also a deprecated field, so this MR also removes repository_storages and makes repository_storages_weighted a visible field.
-
- 17 Jul, 2020 1 commit
-
-
Markus Koller authored
This adds a new validation to restrict the maximum size of a wiki page, which is only enforced when the content is updated, and only when using the GitLab UI or API (not for Git pushes yet). The default limit is 50MB, and can be changed through the Rails console or the API.
-
- 07 Jul, 2020 1 commit
-
-
George Koltsov authored
- Change hard coded Project/Group Import/Export rate limits to configurable application limits in order to give admins an ability to tighten or loosen these rate up
-
- 01 Jul, 2020 1 commit
-
-
Kerri Miller authored
-
- 19 Jun, 2020 1 commit
-
-
Drew Blessing authored
Add a global setting to allow known sign-in feature to be enabled/disabled by a GitLab administrator.
-
- 15 Jun, 2020 1 commit
-
-
John Cai authored
Modify the logic for picking a new repository storage to use the weighted values in repository_storages_weighted instead of the array in repository_storages.
-
- 09 Jun, 2020 1 commit
-
-
Roger Meier authored
Closes #216938
-
- 25 May, 2020 1 commit
-
-
John Cai authored
Add repository_storages_weighted field to the ApplicationSetting model. repository_storages_weighted is like repository_storages, except it allows a value per storage that will be used to store a weight from 0 to 100.
-