b609a25014
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 | 4 years ago | |
| assets | 4 years ago | |
| build | 4 years ago | |
| cmd | 4 years ago | |
| contrib | 4 years ago | |
| custom/conf | 4 years ago | |
| docker | 4 years ago | |
| docs | 4 years ago | |
| integrations | 4 years ago | |
| models | 4 years ago | |
| modules | 4 years ago | |
| options | 4 years ago | |
| public | 4 years ago | |
| routers | 4 years ago | |
| services | 4 years ago | |
| snap | 4 years ago | |
| templates | 4 years ago | |
| vendor | 4 years ago | |
| web_src | 4 years ago | |
| .changelog.yml | 4 years ago | |
| .drone.yml | 4 years ago | |
| .editorconfig | 4 years ago | |
| .eslintrc | 4 years ago | |
| .gitattributes | 4 years ago | |
| .gitignore | 4 years ago | |
| .golangci.yml | 4 years ago | |
| .ignore | 4 years ago | |
| .lgtm | 7 years ago | |
| .npmrc | 4 years ago | |
| .revive.toml | 6 years ago | |
| .stylelintrc | 4 years ago | |
| BSDmakefile | 6 years ago | |
| CHANGELOG.md | 4 years ago | |
| CONTRIBUTING.md | 4 years ago | |
| DCO | 8 years ago | |
| Dockerfile | 4 years ago | |
| LICENSE | 8 years ago | |
| MAINTAINERS | 4 years ago | |
| Makefile | 4 years ago | |
| README.md | 4 years ago | |
| README_ZH.md | 4 years ago | |
| build.go | 4 years ago | |
| go.mod | 4 years ago | |
| go.sum | 4 years ago | |
| main.go | 4 years ago | |
| package-lock.json | 4 years ago | |
| package.json | 4 years ago | |
| semantic.json | 4 years ago | |
| webpack.config.js | 4 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 backendwhich requires Go 1.12 or greater.make frontendwhich 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!
Authors
Backers
Thank you to all our backers! 🙏 [Become a backer]
Sponsors
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
FAQ
How do you pronounce Gitea?
Gitea is pronounced /ɡɪ’ti:/ as in "gi-tea" with a hard g.
Why is this not hosted on a Gitea instance?
We're working on it.
License
This project is licensed under the MIT License. See the LICENSE file for the full license text.
Screenshots
Looking for an overview of the interface? Check it out!
 |
 |
 |
|---|---|---|
 |
 |
 |
 |
 |
 |
 |
 |
 |