mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-10-21 08:56:28 +00:00
Beyond coding. We forge.
https://forgejo.org
- Go 81.7%
- go-html-template 10.3%
- TypeScript 2.8%
- JavaScript 2%
- CSS 1.8%
- Other 1.3%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
ea9ae1e174
Instead of hiding the Git LFS pointer as a binary file, it would be more interesting and informative to the user if we were to actually show the diff in a way that is not messed up and show a suitable information message for "Git LFS" that tells users to click on "View File" to view the actual contents. Every web endpoint displaying Git LFS pointers (e.g. commit, blame) or the contents thereof shall contain an explanation that i) a file is a Git LFS pointer; ii) the actual file contents are stored in Git LFS. The test coverage improvements (covering both cases) are the largest part of this change, and make up for the lack of coverage up until now. If LFS is disabled, 'View file' now redirects to the /raw/ link instead. "Stored in Git LFS" is shown in the 'Blame view' right now, but not in a very accurate way as described in ii), but that can be fixed in a larger refactor and that's part of a TODO. gitdiff should now use more code of the 'lfs' module; we created ReadPointerFromString to allow for that, and expect future improvements to ReadPointerFromBuf to help. This means that we don't e.g. only depend on the second line of a text file to establish whether it is a Git LFS pointer or not. Unit tests were adjusted appropriately (albeit in a bit of a paranoid manner). "Stored in Git LFS" is shown in the 'Blame view' right now, but not in a very accurate way as described in ii), but that can be fixed in a larger refactor and that's part of a TODO. This PR also covers use cases such as that requested in https://codeberg.org/forgejo/forgejo/pulls/14662#issuecomment-24732504. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/14559 Reviewed-by: Mathieu Fenniak <mathieu@fenniak.net> |
||
| .devcontainer | ||
| .forgejo | ||
| .semgrep | ||
| assets | ||
| build | ||
| cmd | ||
| contrib | ||
| custom/conf | ||
| docker | ||
| models | ||
| modules | ||
| options | ||
| public | ||
| release-notes | ||
| release-notes-published | ||
| releases/images | ||
| routers | ||
| services | ||
| templates | ||
| tests | ||
| tools | ||
| web_src | ||
| .air.toml | ||
| .deadcode-out | ||
| .dockerignore | ||
| .editorconfig | ||
| .envrc.example | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .gitpod.yml | ||
| .golangci.yml | ||
| .ignore | ||
| .mailmap | ||
| .markdownlint.yaml | ||
| .mockery.yml | ||
| .node-version | ||
| .npmrc | ||
| .release-notes-assistant.yaml | ||
| .spectral.yaml | ||
| .yamllint.yaml | ||
| BSDmakefile | ||
| CODEOWNERS | ||
| CONTRIBUTING.md | ||
| DCO | ||
| Dockerfile | ||
| Dockerfile.rootless | ||
| eslint.config.ts | ||
| flake.lock | ||
| flake.nix | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| manifest.scm | ||
| package-lock.json | ||
| package.json | ||
| playwright.config.ts | ||
| README.md | ||
| release-notes-assistant.sh | ||
| RELEASE-NOTES.md | ||
| shell.nix | ||
| stylelint.config.ts | ||
| tailwind.config.ts | ||
| tsconfig.json | ||
| vitest.config.ts | ||
| webpack.config.ts | ||
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 built-in 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.
License
Forgejo is distributed under the terms of the GPL version 3.0 or any later version.
The agreement for this license was documented in June 2023 and implemented during the development of Forgejo v9.0. All Forgejo versions before v9.0 are distributed under the MIT license.
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.