delta/gitlab/gitlab-ce.git/app/policies, branch 51470-webide-default-commit gitlab.com: gitlab-org/gitlab-ce.git Allow disabling group/project email notifications 2019-08-15T17:37:36+00:00 Brett Walker bwalker@gitlab.com 2019-08-15T17:37:36+00:00 3489dc3d7277bf478f68e1b3e0353b702f652acc - Adds UI to configure in group and project settings - Removes notification configuration for users when disabled at group or project level 
- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level
Merge remote-tracking branch 'dev/security-2873-restrict-slash-commands-to-users-who-can-log-in' 2019-08-14T18:11:04+00:00 John T Skarbek jskarbek@gitlab.com 2019-08-14T18:11:04+00:00 2b2efbc609a85093238ee3bec94358670021d0e5 






Add group level container repository endpoints
2019-08-05T20:00:50+00:00

Steve Abrams
sabrams@gitlab.com

2019-08-05T20:00:50+00:00

3dbf3997bbf51eca8a313c4e152c77c1b038fd5d

API endpoints for requesting container repositories
and container repositories with their tag information
are enabled for users that want to specify the group
containing the repository rather than the specific project.





API endpoints for requesting container repositories
and container repositories with their tag information
are enabled for users that want to specify the group
containing the repository rather than the specific project.







Remove code related to object hierarchy in MySQL
2019-07-25T07:35:06+00:00

Heinrich Lee Yu
heinrich@gitlab.com

2019-07-24T09:20:54+00:00

1ce5bcacdbf56682e05fa63875203bf4d10584bc

These are not required because MySQL is not
supported anymore





These are not required because MySQL is not
supported anymore







Add policy to allow maintainers to create subgroups when enabled
2019-07-19T18:55:46+00:00

Fabio Papa
fabtheman@gmail.com

2019-06-27T22:53:46+00:00

c96b503bfa05e9f1db727d5f03b0bc562bc69c11












Reset group policy to only allow >= owners to create subgroups
2019-07-19T18:55:45+00:00

Fabio Papa
fabtheman@gmail.com

2019-06-27T21:46:48+00:00

faa8b69f2b6dd4d6d9117a9988d1232f94c418f1












Update the group policy to allow >= maintainer to create subgroups
2019-07-19T18:55:45+00:00

Fabio Papa
fabtheman@gmail.com

2019-06-16T19:23:56+00:00

11f998d9f250bf63abdebc1e0934b39d62f349f6

All specs passing





All specs passing







Restrict slash commands to users who can log in
2019-07-19T09:32:06+00:00

Hordur Freyr Yngvason
hfyngvason@gitlab.com

2019-07-04T10:31:44+00:00

7b52cff4896c8f681aea34fb273209400cf3e06e












Allow use of legacy triggers with feature flag
2019-07-15T13:05:22+00:00

Fabio Pitino
fpitino@gitlab.com

2019-06-25T11:41:11+00:00

42d99460d3bbae88fdd9d8415970ecbfffc85a01

Keep feature flag disabled by default and turn off
all functionality related to legacy triggers.

* Block legacy triggers from creating pipeline
* Highlight legacy triggers to be invalid via the UI
* Make legacy triggers invalid in the model





Keep feature flag disabled by default and turn off
all functionality related to legacy triggers.

* Block legacy triggers from creating pipeline
* Highlight legacy triggers to be invalid via the UI
* Make legacy triggers invalid in the model







Refactor: model errors for multi cluster validation
2019-07-11T07:22:58+00:00

Dylan Griffith
dyl.griffith@gmail.com

2019-07-10T05:33:09+00:00

dacd0ee18b617f0c81c4a478a4d801b3c37e0c56

The current approach requires catching exceptions to handle these errors
and callers are already handling model validations so it seems more
appropriate.  Also it seemed to convoluted to add this logic directly to
the model since the model needs to check too many possible associations
to determine whether or not there are more than one cluster since the
model doesn't know what it's being created on. Additionally we only
wanted to validate during create to avoid the risk of existing models
becoming invalid by many different edge cases.





The current approach requires catching exceptions to handle these errors
and callers are already handling model validations so it seems more
appropriate.  Also it seemed to convoluted to add this logic directly to
the model since the model needs to check too many possible associations
to determine whether or not there are more than one cluster since the
model doesn't know what it's being created on. Additionally we only
wanted to validate during create to avoid the risk of existing models
becoming invalid by many different edge cases.