delta/gitlab/gitlab-ce.git/app/controllers/profiles, branch remove-require-context-users-bundle gitlab.com: gitlab-org/gitlab-ce.git Enable Style/ColonMethodCall 2017-02-23T15:31:57+00:00 Douwe Maan douwe@selenight.nl 2017-02-22T00:51:36+00:00 7ea641b6d0882fc782a7eb493daf8b66d076924b 






No more and/or
2017-02-21T22:31:14+00:00

Douwe Maan
douwe@selenight.nl

2017-02-21T22:31:14+00:00

f40716f48a25809d197ba2abf32ce150b7b73efa












Drop theme ID from users table
2017-02-15T19:31:18+00:00

Annabel Dunstone Gray
annabel.dunstone@gmail.com

2017-02-13T17:38:53+00:00

0667d1aa7f251f5bf11dd121fe2f696107d8103e












Add notified_of_own_activity to permitted attributes
2017-02-01T19:31:21+00:00

Richard Macklin
richard.github@nrm.com

2017-01-27T09:31:53+00:00

0a0207ea91fdbe869ac70c23178b876bcbeb3021

in Profiles::NotificationsController#update





in Profiles::NotificationsController#update







Merge branch '20492-access-token-scopes' into 'master'

2016-12-16T17:38:41+00:00

Rémy Coutable
remy@rymai.me

2016-12-16T17:38:41+00:00

ca6bf62ec14a37bf13f670ff7f62a4c12309fea5


Resolve "Add a doorkeeper scope suitable for authentication"

## What does this MR do?

- Add a single new scope (in addition to the `api` scope we've had) - `read_user`
- Allow creating OAuth applications and Personal access tokens with a scope selected
- Enforce scopes in the API

## What are the relevant issue numbers?

- Closes #20492 
- EE counterpart for this MR: gitlab-org/gitlab-ee!946

See merge request !5951





Resolve "Add a doorkeeper scope suitable for authentication"

## What does this MR do?

- Add a single new scope (in addition to the `api` scope we've had) - `read_user`
- Allow creating OAuth applications and Personal access tokens with a scope selected
- Enforce scopes in the API

## What are the relevant issue numbers?

- Closes #20492 
- EE counterpart for this MR: gitlab-org/gitlab-ee!946

See merge request !5951






Add GitLab host to 2FA QR and manual info
2016-12-16T14:37:40+00:00

Drew Blessing
drew@gitlab.com

2016-10-17T14:39:14+00:00

55f224e4e785d0e1515ac4a840e689cb6d9c7d24

The two factor authentication account string only had the user's
email address. This led to ambiguous entries in two factor
code generating apps. This adds the GitLab host to the account
string in the standard format (according to Google). No matter
the code generator this change disambiguates the entry.





The two factor authentication account string only had the user's
email address. This led to ambiguous entries in two factor
code generating apps. This adds the GitLab host to the account
string in the standard format (according to Google). No matter
the code generator this change disambiguates the entry.







Allow creating personal access tokens / OAuth applications with scopes.
2016-12-16T09:38:10+00:00

Timothy Andrew
mail@timothyandrew.net

2016-11-22T08:57:31+00:00

6c809dfae84e702f7a49d3fac5725745264e0ff9












Remove event caching code
2016-11-23T13:17:07+00:00

Yorick Peterse
yorickpeterse@gmail.com

2016-11-23T13:14:04+00:00

5371da341e9d7768ebab8e159b3e2cc8fad1d827

Flushing the events cache worked by updating a recent number of rows in
the "events" table. This has the result that on PostgreSQL a lot of dead
tuples are produced on a regular basis. This in turn means that
PostgreSQL will spend considerable amounts of time vacuuming this table.
This in turn can lead to an increase of database load.

For GitLab.com we measured the impact of not using events caching and
found no measurable increase in response timings. Meanwhile not flushing
the events cache lead to the "events" table having no more dead tuples
as now rows are only inserted into this table.

As a result of this we are hereby removing events caching as it does not
appear to help and only increases database load.

For more information see the following comment:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037





Flushing the events cache worked by updating a recent number of rows in
the "events" table. This has the result that on PostgreSQL a lot of dead
tuples are produced on a regular basis. This in turn means that
PostgreSQL will spend considerable amounts of time vacuuming this table.
This in turn can lead to an increase of database load.

For GitLab.com we measured the impact of not using events caching and
found no measurable increase in response timings. Meanwhile not flushing
the events cache lead to the "events" table having no more dead tuples
as now rows are only inserted into this table.

As a result of this we are hereby removing events caching as it does not
appear to help and only increases database load.

For more information see the following comment:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6578#note_18864037







Add chat_name partial
2016-11-17T13:58:03+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-11-17T13:58:03+00:00

1ddfc574ce1753ba783c5c1734efb6105f20f3d7












Fix code review
2016-11-17T13:02:14+00:00

Kamil Trzcinski
ayufan@ayufan.eu

2016-11-17T13:02:14+00:00

9b86a5e19d902771ce13f3ddffe89b804479fcbc