| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| | |
Remove Users.support_bot column
See merge request gitlab-org/gitlab-ce!32554
|
| | |
| |
| |
| |
| |
| |
| | |
This column is not present in `db/schema.rb` and hence needs to be
removed conditionally.
See https://gitlab.com/gitlab-org/gitlab-ce/issues/66901 for background
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
Modified schema via migrations.
Added one-to-one relationship between the two models.
Added changelog file
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adjusts the partial condition for an index. The index is intended
to be used when counting active users with `ghost IS NOT TRUE AND
bot_type IS NULL`.
With the current index, this wasn't working as the partial condition
didn't match the query: `ghost <> TRUE` is not semantically equivalent
to `ghost IS NOT TRUE` (null semantics).
The reason we add an index particularly intended for EE is that the EE
query is going to have the additional part `AND bot_type IS NULL`
whereas the CE query doesn't. Logically, it'd be enough to have an index
for `ghost IS NOT TRUE`. However, on GitLab.com, the query planner makes
poor choices when the additional `AND bot_type IS NULL` part is present:
It goes for the index on `bot_type` and doesn't use the partial index.
Note the existing index isn't being used at all according to GitLab.com
index statistics. Hence we can first remove it and don't have to worry
about the window of time without an index.
Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/66770
|
| |
|
|
|
|
| |
Since migrations are not run by new instances, add a production
fixture that should ensure that the self-monitoring project is created
for new instances as well.
|
| |
|
|
|
| |
Rename epic column state to state_id to be consistent with
issues and merge requests
|
| | |
|
| |\ |
|
| | |\
| | |
| | |
| | |
| | |
| | |
| | | |
Use image proxy to mitigate stealing ip addresses
Closes #2812
See merge request gitlab/gitlabhq!2926
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
User images and videos will get proxied through
the Camo server in order to keep malicious
sites from collecting the IP address of users.
|
| | |\ \
| | | |
| | | |
| | | |
| | | | |
Require a captcha after unique failed logins from the same IP
See merge request gitlab/gitlabhq!3270
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add method to store session ids by ip
Add new specs for storing session ids
Add cleaning up records after login
Add retrieving anonymous sessions
Add login recaptcha setting
Add new setting to sessions controller
Add conditions for showing captcha
Add sessions controller specs
Add admin settings specs for login protection
Add new settings to api
Add stub to devise spec
Add new translation key
Add cr remarks
Rename class call
Add cr remarks
Change if-clause for consistency
Add cr remarks
Add code review remarks
Refactor AnonymousSession class
Add changelog entry
Move AnonymousSession class to lib
Move store unauthenticated sessions to sessions controller
Move link to recaptcha info
Regenerate text file
Improve copy on the spam page
Change action filter for storing anonymous sessions
Fix rubocop offences
Add code review remarks
|
| | |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Introduce JobActivity limit for alive jobs
Closes gitlab-ee#376
See merge request gitlab/gitlabhq!3339
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is a port from EE changes where
we introduce a new limit for Plan model.
https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/1182
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Now we have cluster_id, state index, we don't the cluster_id index as
well.
|
| | | | | |
| | | | |
| | | | |
| | | | | |
For Environment.deployed_to_cluster
|
| | | | | |
| | | | |
| | | | |
| | | | | |
Persists if a board list is collapsed for each user.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
A new param with_security_reports was added to
GET /groups/:id/projects API and the code to
support this logic in GroupProjectsFinder and
Project model. Also, a DB index was added to
ci_job_artifacts table to speed up the search
of security reports artifacts for projects
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This change sets NOT NULL constraint to users.private profile.
closes https://gitlab.com/gitlab-org/gitlab-ce/issues/57538
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Added migrations to make token column accepting null values and to add
encrypted token column.
|
| |/ / / /
| | | |
| | | |
| | | | |
Removed unused method for name setter method
|
| | |_|/
|/| |
| | |
| | | |
- Also add helper to undo rename_column_concurrently.
|
| | | |
| | |
| | |
| | | |
Add to the service and migration both.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
This cop will analyze migrations that add columns with string, and
report an offense if the string has no limit enforced
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/64505
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds a time series component for line and area charts.
Displays new charts in the dashboard.
- Use dynamic components for line/area swapping
- Add new line charts to dashboard in 2 panels
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Sorting preference functionality has been extracted
from `IssuableCollections` to a new `SortingPreference`
concern in order to reuse this functionality in projects
(and groups in the future).
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adding, destroying and toggling emoji previously lacked services and
instead were performed through methods called on Awardable models.
This led to inconsistencies where relevant todos would be marked as done
only when emoji were awarded through our controllers, but not through
the API. Todos could also be marked as done when an emoji was being
removed.
Behaviour changes
- Awarding emoji through the API will now mark a relevant Todo as done
- Toggling an emoji off (destroying it) through our controllers will no
longer mark a relevant Todo as done
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63372
|
| | |
| |
| |
| | |
These will be moved to the EE codebase.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In order to save user preferences regarding
user emails allowed to be invited to group
Add foreign_key and down method
Change adding foreign key
Add partial call to view
Add changelog entry
Fix schema
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
To index notes, we exclude system notes and use `find_in_batches` to
load them in batches for submission to the ES bulk import API.
These queries often result in DB timeouts because the usage of
`ORDER BY id` results in the `notes_pkey` index being used.
This adds an optimized partial index, and removes the unused index
`index_notes_on_noteable_type` which is already covered for our
usage by the existing `index_notes_on_noteable_id_and_noteable_type`.
Newer versions of PostgreSQL (at least 11) are smarter about this and
use `index_notes_on_project_id_and_noteable_type` instead, so we might
be able to remove the partial index again in the future.
|
| | |
| |
| |
| |
| |
| |
| | |
This change lays the foundation for customizable cycle analytics stages.
The main reason for the change is to extract the event definitions to
separate objects (start_event, end_event) so that it could be easily
customized later on.
|
| | |
| |
| |
| |
| |
| | |
- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14943
See merge request gitlab-org/gitlab-ce!31406
|
| | | |
| | |
| | |
| | | |
Docker Registry Replication
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'13208-epicissue-has-an-unexpected-default-relative-position-ce' into 'master'
[CE] Remove default `relative_position` from `epic_issues`
See merge request gitlab-org/gitlab-ce!31514
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This makes `epic_issues` consistent with other tables
using our `RelativePositioning` class
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'4221-board-milestone-should-persist-any-none-properly-ce' into 'master'"
This reverts merge request !30613
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Remove KubernetesService integration
See merge request gitlab-org/gitlab-ce!31365
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Creating new records has been disabled, and all
existing records been migrated to clusters as of
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28534
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | | |
- This will make it easy to identify the project even if admins change
the name of the project or move it.
|
