Alan Pope b609a25014 Add logic to build stable and edge builds (#12052 ) This adds some logic to enable the snapcraft builds of the gitea snap to create both builds of the latest tip of master for edge channels, and stable releases. The logic simply looks for a new upstream release in github, and if that latest tagged release is not the same as the release in the candidate channel in the snap store, then it must be new, and so we checkout that tag and build that. If the current released tag is the same as what's in candidate, we build whatever is in git master. The process for using this is: Initially: When this lands, it will build the latest stable release of gitea and push to the edge channel in the snap store. Someone on the release team can go to https://snapcraft.io/gitea/releases and release that build to stable and candidate. Ongoing: The next build to be triggered will be a git master build, and can just sit in edge, nothing for the release team to do. On new release: The next build triggered will contain the stable release, and will be published to edge. Someone on the release team can login to the above URL and release that again to stable & candidate. Alternatively they can release to candidate, do some additional testing on that release before releasing to stable. Hope that all makes sense. Questions / comments welcome. I'm super keen to see stable releases of Gitea in the stable channel of the Snap Store. I'd like to promote it but I can't really until it's in stable. Co-authored-by: techknowlogick <techknowlogick@gitea.io>		4 years ago
.github	Improve stale message (#9920 )	5 years ago
assets	Direct SVG rendering (#12157 )	5 years ago
build	Update Octicons to v10 (#12240 )	4 years ago
cmd	Decrease the num_stars when deleting a repo (#11954 )	5 years ago
contrib	upgrade to use testfixtures v3 (#11904 )	5 years ago
custom/conf	Move EventSource to SharedWorker (#12095 )	5 years ago
docker	Fix missing CGO_EXTRA_FLAGS build arg for docker (#11782 )	5 years ago
docs	[Docs] Logging Configuration - Use `logrotate` Instead (#9930 )	4 years ago
integrations	Update Octicons to v10 (#12240 )	4 years ago
models	Update Octicons to v10 (#12240 )	4 years ago
modules	Update Octicons to v10 (#12240 )	4 years ago
options	[skip ci] Updated translations via Crowdin	5 years ago
public	Update Octicons to v10 (#12240 )	4 years ago
routers	models: fix xorm variable clobber (#12231 )	5 years ago
services	Fix Syntax highlight for token change in added/deleted code (#12238 )	4 years ago
snap	Add logic to build stable and edge builds (#12052 )	4 years ago
templates	Update Octicons to v10 (#12240 )	4 years ago
vendor	Upgrade xorm to v1.0.3 (#12210 )	5 years ago
web_src	Update Octicons to v10 (#12240 )	4 years ago
.changelog.yml	Changelog 1.11.0 (#10204 ) (#10211 )	5 years ago
.drone.yml	Alpine 3.12 (#11720 )	5 years ago
.editorconfig	Use custom SVGs for commit signing lock icon (#12017 )	5 years ago
.eslintrc	Update JS dependencies (#12181 )	5 years ago
.gitattributes	Rename scripts to build and add revive command as a new build tool command (#10942 )	5 years ago
.gitignore	Direct SVG rendering (#12157 )	5 years ago
.golangci.yml	Improve push update options (#10105 )	5 years ago
.ignore	Fonts rework (#12114 )	5 years ago
.lgtm	refactor: ignore LGTM from author of pull request. (#3283 )	7 years ago
.npmrc	add package-lock=true in .npmrc (#9736 )	5 years ago
.revive.toml	refactor: replace lint to revive (#5422 )	6 years ago
.stylelintrc	Enable stylelint's shorthand-property-no-redundant-values (#11436 )	5 years ago
BSDmakefile	Add BSDmakefile to prevent errors when `make` is called under FreeBSD (#4446 )	7 years ago
CHANGELOG.md	Frontport Changelog of v1.12.2 (#12216 )	5 years ago
CONTRIBUTING.md	Add link to owners election tickets, reorder to most-recent first (#11632 )	5 years ago
DCO	follow the advisor: add DCO and some improvements	8 years ago
Dockerfile	Fix missing CGO_EXTRA_FLAGS build arg for docker (#11782 )	5 years ago
LICENSE	Fix typo	8 years ago
MAINTAINERS	Add myself to MAINTAINERS (#11494 )	5 years ago
Makefile	Release docs as archive (#12253 )	5 years ago
README.md	Show drone status for master branch in README (#12248 )	5 years ago
README_ZH.md	update discord link (#10455 )	5 years ago
build.go	Add gitea-vet (#10948 )	5 years ago
go.mod	Upgrade xorm to v1.0.3 (#12210 )	5 years ago
go.sum	Upgrade xorm to v1.0.3 (#12210 )	5 years ago
main.go	Prevent support libraries from compiling into Gitea (#10964 )	5 years ago
package-lock.json	Update Octicons to v10 (#12240 )	4 years ago
package.json	Update Octicons to v10 (#12240 )	4 years ago
semantic.json	Move fomantic and jQuery to main webpack bundle (#11997 )	5 years ago
webpack.config.js	Direct SVG rendering (#12157 )	5 years ago

README.md

简体中文

Gitea - Git with a cup of tea

Purpose

The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service. Using Go, this can be done with an independent binary distribution across all platforms which Go supports, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. Want to try it before doing anything else? Do it with the online demo! This project has been forked from Gogs since 2016.11 but changed a lot.

Building

From the root of the source tree, run:

TAGS="bindata" make build

or if sqlite support is required:

TAGS="bindata sqlite sqlite_unlock_notify" make build

The build target is split into two sub-targets:

make backend which requires Go 1.12 or greater.
make frontend which requires Node.js 10.13 or greater.

If pre-built frontend files are present it is possible to only build the backend:

	TAGS="bindata" make backend

More info: https://docs.gitea.io/en-us/install-from-source/

Using

./gitea web

NOTE: If you're interested in using our APIs, we have experimental support with documentation.

Contributing

Expected workflow is: Fork -> Patch -> Push -> Pull Request

NOTES:

YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!

Further information

For more information and instructions about how to install Gitea, please look at our documentation. If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server, or forum!