delta/gitlab/gitlab-ce.git/app/policies, branch 35942_api_binary_encoding

`current_application_settings` belongs on `Gitlab::CurrentSettings`

2017-08-31T12:38:33+00:00

The initializers including this were doing so at the top level, so every object
loaded after them had a `current_application_settings` method. However, if
someone had rack-attack enabled (which was loaded before these initializers), it
would try to load the API, and fail, because `Gitlab::CurrentSettings` didn't
have that method.

To fix this:

1. Don't include `Gitlab::CurrentSettings` at the top level. We do not need
   `Object.new.current_application_settings` to work.
2. Make `Gitlab::CurrentSettings` explicitly `extend self`, as we already use it
   like that in several places.
3. Change the initializers to use that new form.

replace `is_team_member?` with `team_member?`

2017-08-29T08:14:42+00:00

Improves subgroup creation permissions

2017-08-21T14:40:22+00:00

Allow logged in users to read user list under public restriction

2017-08-01T07:46:13+00:00

Merge branch '30634-protected-pipeline' into 'master'

2017-07-25T15:04:23+00:00

Implement "Block pipelines on protected branches"

Closes #30634, #34616, and #33130

See merge request !11910

Allow admin to read_users_list even if it's restricted

2017-07-25T08:49:26+00:00

Don't treat anonymous users as owners when group has pending invites

2017-07-24T15:58:04+00:00

The `members` table can have entries where `user_id: nil`, because people can
invite group members by email. We never want to include those as members,
because it might cause confusion with the anonymous (logged out) user.

Associate Issues tab only with internal issues tracker

2017-07-24T06:10:14+00:00

Rename :user_cannot_update to :protected_ref

2017-07-18T14:13:57+00:00

Rename can_push_or_merge_to_branch? to can_update_branch?

2017-07-18T13:56:28+00:00

Also make sure pipeline would also check against tag as well