aiforge

Commit Graph

Author	SHA1	Message	Date
마누엘	5aa1237e26	routers/repo/release: Use correct branch reference (#3330 ) When calculating the current behind commit count the calculation should use the current release target to get the total commit count. Should the release target not exist anymore the calculation will return zero for the newest release on that target. Older releases on that target will then use that calculated commit count as reference. The only use case that is now somehow invalid is when the release target was merged / deleted after a tag on that release target: master 1 - - - - - - - 6 \ / branch 2 - 3 - 4 - 5 When `4` is the last tag on branch `branch` and the branch `branch` is not yet deleted the calculated numbers would be: 1 commits to branch since this release Now if the branch `branch` gets deleted the calculation function will not find the branch and use the commit count of the newest release (`4`) as reference resulting in: 0 commit to branch since this release This fixes #3326	9 years ago
Unknwon	3b42ab0e57	Refactor User.Id to User.ID	9 years ago
Unknwon	41c8e6c524	#3076 detect invalid tag name git error	9 years ago
Unknwon	574a4d69e8	Rename module: middleware -> context	9 years ago
Unknwon	10d7cf61bd	Remove duplicated of code	9 years ago
Unknwon	d398777e08	Make markdown as an independent module	9 years ago
Martin Hartkorn	727beb7d72	Removed HTTP 500 error on the release page when a user deleted their account	9 years ago
Unknwon	7c3baef786	move out git module and #1573 send push hook	9 years ago
Unknwon	caac2f9b19	fix #1829 and fix #890	9 years ago
Unknwon	a0a4125989	fix #1383	9 years ago
Unknwon	47d9cf7edf	repo sidebar active class	9 years ago
Unknwon	c0b841a766	fix #1958	9 years ago
Unknwon	12cad18886	rename fields	9 years ago
Unknwon	36fa23ed16	WIP: create PR - choose branch	10 years ago
Peter Smit	16bfbe24e7	Updating context and fixing permission issues The boolean flags in the repo context have been replaced with mode and two methods Also, the permissions have been brought more in line with https://help.github.com/articles/permission-levels-for-an-organization-repository/ , Admin Team members are able to change settings of their repositories.	10 years ago
Unknwon	bc8721fb6c	Finish new UI for release page	10 years ago
Unknwon	23eec25274	Fix #605 , fix #255 , fix #101	10 years ago
Unknwon	5c4bc3c848	Huge updates!!!!! Be careful to merge!!!!	11 years ago
Unknwon	8dd07c0ddd	New UI merge in progress	11 years ago
Unknown	314193029a	Use constants to name template file	11 years ago
Unknown	e07674bff1	Support edit release and save as draft	11 years ago
Unknown	fb0972afad	Fix #199	11 years ago
Unknown	9961f9a53c	Fix #197	11 years ago
slene	7d84cc96e8	update with git api	11 years ago
Unknown	2a9da4b8e5	Fix #92	11 years ago
Unknown	f644cefa86	Finish release	11 years ago
slene	52b4ab2aa5	update with new git	11 years ago
FuXiaoHei	3ede496383	add release-new route	11 years ago
Unknown	db66b8da72	Add release tmpl	11 years ago

29 Commits (5aa1237e26e0dedf4bcd95ebd1a80f64a9aedaff)