Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Add latest changes from gitlab-org/gitlab@14-10-stable-eev14.10.0-rc42 | GitLab Bot | 2022-04-20 | 1 | -0/+11 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@13-2-stable-ee | GitLab Bot | 2020-07-20 | 1 | -1/+1 |
| | |||||
* | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | 2020-01-13 | 1 | -0/+8 |
| | |||||
* | Persist tmp snippet uploads | Oswaldo Ferreira | 2019-06-17 | 1 | -2/+11 |
| | | | | | | | | | | It persist temporary personal snippets under user/:id namespaces temporarily while creating a upload record to track it. If an user gets removed while it's still a tmp upload, it also gets removed. If the tmp upload is sent, the upload gets moved to personal_snippets/:id as before. The upload record also gets updated to the new model type as well. | ||||
* | Remove the `comment_personal_snippet` permissionremove-comment-personal-snippet-permission | Sean McGivern | 2019-05-02 | 1 | -0/+22 |
This is now entirely handled by `create_note`: 1. Project snippets prevent `create_note`. 2. Uploads already only support routing for personal snippets. This simplifies some policies and access checks, too! |