aiforge

392 MB

Tree: 251129ed3e

Author	SHA1	Message	Date
Tamal Saha	033fe113c1	Use gitea forked macaron (#7933 ) Signed-off-by: Tamal Saha <tamal@appscode.com>	5 years ago
zeripath	7c0771973a	Fix #732 : Add LFS objects to base repository on merging (#7082 ) On merge we walk the merge history and ensure that all lfs objects pointed to in the history are added to the base repository. This switches from relying on having git-lfs installed on the server, (and in fact .gitattributes being correctly installed.)	6 years ago
zeripath	df6b18e11d	Improve git test (#7086 ) * Ensure that the lfs files are created with a different prefix * Reduce the replication in git_test.go	6 years ago
Lunny Xiao	45d0e05e14	Move sdk structs to modules/structs (#6905 ) * move sdk structs to moduels/structs * fix tests * fix fmt * fix swagger * fix vendor	6 years ago
zeripath	54b40cb52b	Fix ssh deploy and user key constraints (#1357 ) (#5939 ) 1. A key can either be an ssh user key or a deploy key. It cannot be both. 2. If a key is a user key - it can only be associated with one user. 3. If a key is a deploy key - it can be used in multiple repositories and the permissions it has on those repositories can be different. 4. If a repository is deleted, its deploy keys must be deleted too. We currently don't enforce any of this and multiple repositories access with different permissions doesn't work at all. This PR enforces the following constraints: - [x] You should not be able to add the same user key as another user - [x] You should not be able to add a ssh user key which is being used as a deploy key - [x] You should not be able to add a ssh deploy key which is being used as a user key - [x] If you add an ssh deploy key to another repository you should be able to use it in different modes without losing the ability to use it in the other mode. - [x] If you delete a repository you must delete all its deploy keys. Fix #1357	6 years ago

5 Commits (251129ed3ea6f6fc527b02f724c611202cb5fb26)