Update/merge 12 into 13 (!208) · Merge requests · SMASCH / scheduling-system

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Carlos Vega requested to merge update/merge_12_into_13 into master Jan 08, 2019

I think this should be merged after !206 (merged) and !200 (merged) It would probably be conflicts after those two are merged or viceversa. I will fix them should it be needed.

Admin message

Update/merge 12 into 13

Merge request reports