9341b37520
- Consider executable files as a valid case when returning a downloadURL for them. They are just regular files with the difference being the executable permission bit being set. - Not integration testing as it's not possible without adding adjusting the existing repositories to have a executable file. - Resolves https://codeberg.org/forgejo/forgejo/issues/1825 (cherry picked from commit ca32891d548c302b0f3b3072647058278ffb9cbf) (cherry picked from commit 72c9df8e457ea291f767e6edf2b3c8f9af15700f) (cherry picked from commit 0eae22d429a66f137daa200f559883a6b6a31de0) (cherry picked from commit d37d0773bc005df19f300f9ada03632ea9f97642) (cherry picked from commit de4532a96721ed4259aa36cb417bb49ed979f6e5) (cherry picked from commit f5b41300a86222308eb605c84945ed7c9770b04d) (cherry picked from commit d3be0480b78ec2edbd78c4c0685f097b2ee841d6) (cherry picked from commit c72307fd3bbb6b29cffe112dd71c70871595a0ce) (cherry picked from commit 71db59305787decb1beb817d399bb3ffc2b78566) (cherry picked from commit 568e668fb8d707b84ba0ba47c2ed9e2ef35df4c5) |
||
---|---|---|
.devcontainer | ||
.forgejo | ||
.gitea | ||
assets | ||
build | ||
cmd | ||
contrib | ||
custom/conf | ||
docker | ||
docs | ||
models | ||
modules | ||
options | ||
public | ||
releases/images | ||
routers | ||
services | ||
snap | ||
templates | ||
tests | ||
web_src | ||
.air.toml | ||
.changelog.yml | ||
.deadcode-out | ||
.dockerignore | ||
.editorconfig | ||
.eslintrc.yaml | ||
.gitattributes | ||
.gitignore | ||
.gitpod.yml | ||
.golangci.yml | ||
.ignore | ||
.markdownlint.yaml | ||
.npmrc | ||
.spectral.yaml | ||
.stylelintrc.yaml | ||
.yamllint.yaml | ||
BSDmakefile | ||
build.go | ||
CHANGELOG.md | ||
CODEOWNERS | ||
CONTRIBUTING.md | ||
DCO | ||
Dockerfile | ||
Dockerfile.rootless | ||
go.mod | ||
go.sum | ||
LICENSE | ||
main.go | ||
MAINTAINERS | ||
Makefile | ||
package-lock.json | ||
package.json | ||
playwright.config.js | ||
poetry.lock | ||
poetry.toml | ||
pyproject.toml | ||
README.md | ||
RELEASE-NOTES.md | ||
vitest.config.js | ||
webpack.config.js |
Welcome to Forgejo
Hi there! Tired of big platforms playing monopoly? Providing Git hosting for your project, friends, company or community? Forgejo (/for'd͡ʒe.jo/ inspired by forĝejo – the Esperanto word for forge) has you covered with its intuitive interface, light and easy hosting and a lot of builtin functionality.
Forgejo was created in 2022 because we think that the project should be owned by an independent community. If you second that, then Forgejo is for you! Our promise: Independent Free/Libre Software forever!
What does Forgejo offer?
If you like any of the following, Forgejo is literally meant for you:
- Lightweight: Forgejo can easily be hosted on nearly every machine. Running on a Raspberry? Small cloud instance? No problem!
- Project management: Besides Git hosting, Forgejo offers issues, pull requests, wikis, kanban boards and much more to coordinate with your team.
- Publishing: Have something to share? Use releases to host your software for download, or use the package registry to publish it for docker, npm and many other package managers.
- Customizable: Want to change your look? Change some settings? There are many config switches to make Forgejo work exactly like you want.
- Powerful: Organizations & team permissions, CI integration, Code Search, LDAP, OAuth and much more. If you have advanced needs, Forgejo has you covered.
- Privacy: From update checker to default settings: Forgejo is built to be privacy first for you and your crew.
- Federation: (WIP) We are actively working to connect software forges with each other through ActivityPub, and create a collaborative network of personal instances.
Learn more
Dive into the documentation, subscribe to releases and blog post on our website, find us on the Fediverse or hop into our Matrix room if you have any questions or want to get involved.
Get involved
If you are interested in making Forgejo better, either by reporting a bug or by changing the governance, please take a look at the contribution guide.