Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Adds chmod action to POST /projects/:id/repository/commits API | Jacopo | 2018-09-27 | 1 | -1/+35 |
| | | | | With this action the user can update the execute_filemode of a given file in the repository. | ||||
* | Guard against regressions in commit email specs | Nick Thomas | 2018-09-18 | 3 | -2/+5 |
| | |||||
* | Use the correct email address when committing via a file service | Nick Thomas | 2018-09-17 | 3 | -1/+30 |
| | |||||
* | Resolve "Rename the `Master` role to `Maintainer`" Backend | Mark Chao | 2018-07-11 | 4 | -4/+4 |
| | |||||
* | Make OperationService RPC's mandatory | Jacob Vosmaer (GitLab) | 2018-07-03 | 1 | -12/+0 |
| | |||||
* | Extract constant for LfsPointerFile::VERSION_LINE | James Edwards-Jones | 2018-03-16 | 2 | -4/+4 |
| | |||||
* | Use correct encoding with Lfs::FileTransfromer | James Edwards-Jones | 2018-03-15 | 1 | -10/+30 |
| | |||||
* | Multi-file upload and Commit API obey LFS filters | James Edwards-Jones | 2018-03-15 | 1 | -1/+33 |
| | | | | | | | | Updates Files::MultiService for the commits API which is in turn used by the multi-file upload web UI Ensures that files which should be in LFS are transformed into LFS pointers Uses Lfs::Transformer which then links LfsObjectProjects on success | ||||
* | File upload UI obeys LFS filters | James Edwards-Jones | 2018-02-06 | 1 | -0/+78 |
| | | | | | | | | | | | Uses Lfs::FileModificationHandler to coordinate LFS detection, creation of LfsObject, etc Caveats: 1. This isn't used by the multi-file editor / Web IDE 2. This isn't used on rename. We'd need to be able to download LFS files and add them to the commit if they no longer match so not as simple. 3. We only check the root .gitattributes file, so this should be improved to correctly check for nested .gitattributes files in subfolders. | ||||
* | Incorporate Gitaly's OperationService.UserCommitFiles RPCgitaly-user-commit-files | Alejandro Rodríguez | 2018-01-22 | 1 | -5/+7 |
| | |||||
* | Move git operations for multi_action into Gitlab::Git | Alejandro Rodríguez | 2018-01-05 | 1 | -2/+2 |
| | |||||
* | Replace '.team << [user, role]' with 'add_role(user)' in specs36782-replace-team-user-role-with-add_role-user-in-specs | blackst0ne | 2017-12-22 | 3 | -3/+3 |
| | |||||
* | Updates from last code review:38356-add-last_commit_sha-to-the-commit-api | Rubén Dávila | 2017-12-20 | 2 | -5/+118 |
| | | | | | | - Apply some refactoring for code reuse - Add file status validation for Files::DeleteService - Write additional specs | ||||
* | Check if file has been modified for each action provided. | Rubén Dávila | 2017-12-20 | 1 | -2/+43 |
| | | | | | | When commiting multiple files we're now checking if any of those files has been modified by another commit and we're rejecting the new commit in this case. | ||||
* | Add some initial specs for Files::MultiService class | Rubén Dávila | 2017-12-20 | 1 | -0/+54 |
| | |||||
* | Move GitHooksService to Gitlab::Git | Jacob Vosmaer | 2017-08-23 | 1 | -1/+1 |
| | |||||
* | Enable Style/DotPosition Rubocop :cop: | Grzegorz Bizon | 2017-06-21 | 1 | -2/+2 |
| | |||||
* | Refactor changing files in web UI | Douwe Maan | 2017-04-20 | 1 | -3/+3 |
| | |||||
* | Use `:empty_project` where possible in service specs | Robert Speicher | 2017-03-27 | 1 | -1/+1 |
| | |||||
* | Fix renaming | Lin Jen-Shin | 2017-01-07 | 1 | -2/+2 |
| | |||||
* | Add a test to make sure hooks are fire only once | Lin Jen-Shin | 2016-11-05 | 1 | -14/+15 |
| | | | | when updating a file to a different branch. | ||||
* | multi-file commit | Marc Siegfriedt | 2016-10-05 | 1 | -2/+2 |
| | | | | | | add docs and tests - add additional validation allow move without content updated response | ||||
* | Prevents accidental overwrites of commits from UI | Frank West | 2016-08-15 | 1 | -0/+84 |
Currently when a user performs an update of a file through the UI and there has already been a change committed to the file the previous commits will be overwritten without a check to see if the file has been changed. This commit uses the last commit sha at the time the user starts editing the file and compares it with the current sha of the file being edited to ensure they are the same before committing the file. If the shas do not match we throw an exception preventing the commit from the commit from occurring. Fixes #5857 |