gitea.git - Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea

	Commit message (Collapse)	Author	Age	Files	Lines
*	Lock go to 1.21 on CI (#26433)	silverwind	2023-08-10	1	-1/+1
\| \| \| \| \| \| \|	To prevent unwanted surprises with new minor versions of go, lock the version to minor version using [semver tilde syntax](https://github.com/npm/node-semver#tilde-ranges-123-12-1). We were already getting 1.21.0 since yesterday, so use that version now as minimum.
*	Build nightly binaries with Actions (#25308)	techknowlogick	2023-06-16	1	-0/+1
\| \| \|	Co-authored-by: silverwind <me@silverwind.io>
*	Fix setup-go actions (#25167)	silverwind	2023-06-09	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The `setup-go` actions did not all have `check-latest` which means they use some cached version of go that currently still resolves to go1.20.4, as seen in a number of recent runs that currently fail at govulncheck because of it: ```` Run actions/setup-go@v4 Setup go version spec >=1.20 Attempting to resolve the latest version from the manifest... matching >=1.20... Resolved as '1.20.4' ```` Add the [check-latest](https://github.com/actions/setup-go#check-latest-version) option which should guarantee that this cache is skipped.
*	Don't run build and test if only docs changed (#24530)	Lunny Xiao	2023-05-16	1	-1/+1
\| \| \|	Co-authored-by: techknowlogick <techknowlogick@gitea.io>
*	GitHub Actions cleanups (#24620)	silverwind	2023-05-11	1	-9/+8
\| \| \| \| \| \| \| \| \| \|	- Remove actions name where command is descriptive enough - Use kebab-case instead of snake-case for step names - Use shorter job names because to make PR checks more readable - Remove duplicate `checks-backend` --------- Co-authored-by: Yarden Shoham <git@yardenshoham.com>
*	Use Actions for DB & E2E tests (#24494)	techknowlogick	2023-05-04	1	-2/+2
\| \| \| \| \| \| \| \| \| \|	following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
*	on schedule	techknowlogick	2023-04-25	1	-1/+1
\|
*	switch to use Actions from drone for cron (#24314)	techknowlogick	2023-04-25	1	-0/+28
	Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.