MirrorHub/forgejo
0
0
Fork 0
mirror of https://codeberg.org/forgejo/forgejo.git synced 2024-11-25 22:52:43 +01:00
Code Issues Projects Releases Packages Wiki Activity
No description
17274 commits 11 branches 235 tags 600 MiB
Go 73.9%
go-html-template 11.3%
JavaScript 5%
Roff 4.7%
CSS 3.2%
Other 1.7%
Find a file
Gergely Nagy 2924fcf814
[GITEA] services: Gracefully handle missing branches 
services: in loadOneBranch, return if CountDivergingCommits fail

If we can't count the number of diverging commits for one reason or
another (such as the branch being in the database, but missing from
disk), rather than logging an error and continuing into a crash (because
`divergence` will be nil), return an error instead.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit 8266105f24)

services: Gracefully handle missing branches

When loading branches, if loading one fails, log an error, and ignore
the branch, rather than returning and causing an internal server error.

Ideally, we would only ignore the error if it was caused by a missing
branch, and do it silently, like the respective API endpoint does.
However, veryfing that at this place is not very practical, so for the
time being, ignore any and all branch loading errors.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit e552a8fd62)

tests: Add a testcase for missing branches

This tests the scenario reported in Codeberg/Community#1408: a branch
that is recorded in the database, but missing on disk was causing
internal server errors. With recent changes, that is no longer the case,
the error is logged and then ignored.

This test case tests this behaviour, that the repo's branches page on
the web UI functions even if the git branch is missing.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit e20eb7b385)

tests: More testing in TestDatabaseMissingABranch

In the `TestDatabaseMissingABranch` testcase, make sure that the
branches are in sync between the db and git before deleting a branch via
git, then compare the branch count from the web UI, making sure that it
returns an out-of-sync value first, and the correct one after another
sync.

This is currently tested by scraping the UI, and relies on the fact that
the branch counter is out of date before syncing. If that issue gets
resolved, we'll have to adjust the test to verify the sync another way.

Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
(cherry picked from commit 8c2ccfcece)
(cherry picked from commit 439fadf563)
(cherry picked from commit 44dd80552c)
(cherry picked from commit 37b91fe6f2)
2024-02-05 16:09:42 +01:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] Forgejo Actions based CI for PR & branches (squash) install git >= 2.42 2024-02-05 13:33:59 +01:00
.gitea [WORKFLOW] issues & pr templates (squash) fix link to CONTRIBUTING.md 2024-02-05 15:08:04 +01:00
assets [GITEA] Use maintained gziphandler 2024-02-05 16:09:40 +01:00
build [I18n] tooling and process 2024-02-05 15:08:04 +01:00
cmd [CLI] implement forgejo-cli 2024-02-05 13:33:58 +01:00
contrib [GITEA] fix VSCode settings 2024-02-05 16:09:41 +01:00
custom/conf [GITEA] Add support for shields.io-based badges 2024-02-05 16:09:42 +01:00
docker Dockerfile small refactor (#27757) 2023-10-29 09:44:06 +08:00
docs [GITEA] notifies admins on new user registration 2024-02-05 16:09:28 +01:00
models [FEAT] Repository flags 2024-02-05 16:09:42 +01:00
modules [GITEA] POST /repos/{owner}/{repo}/pulls/{index}/reviews/{id}/comments 2024-02-05 16:09:42 +01:00
options [I18n] Translations update from Weblate (5 February) 2024-02-05 15:11:42 +01:00
public [API] Forgejo API /api/forgejo/v1 2024-02-05 14:44:32 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2024-02-05 14:44:32 +01:00
routers [GITEA] Fix panic in canSoftDeleteContentHistory 2024-02-05 16:09:42 +01:00
services [GITEA] services: Gracefully handle missing branches 2024-02-05 16:09:42 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [GITEA] POST /repos/{owner}/{repo}/pulls/{index}/reviews/{id}/comments 2024-02-05 16:09:42 +01:00
tests [GITEA] services: Gracefully handle missing branches 2024-02-05 16:09:42 +01:00
web_src [GITEA] Use vertical tabs on issue filters 2024-02-05 16:05:50 +01:00
.air.toml Reduce verbosity of dev commands (#24917) 2023-05-24 20:11:04 +00:00
.changelog.yml Adapt .changelog.yml to new labeling system (#27701) 2023-10-20 00:22:00 +02:00
.deadcode-out [GITEA] Enable mocked HTTP responses for GitLab migration test 2024-02-05 16:09:41 +01:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.editorconfig
.eslintrc.yaml Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
.gitattributes [META] Use correct language for .tmpl 2024-02-05 14:44:33 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2024-02-05 15:08:04 +01:00
.gitpod.yml Add Github related extensions in devcontainer (#25800) 2023-07-14 15:58:02 +08:00
.golangci.yml Remove go versions from .golangci.yml (#27953) 2023-11-07 22:03:27 +01:00
.ignore Add /public/assets to .ignore (#26232) 2023-07-30 12:34:20 +02:00
.markdownlint.yaml Update JS dependencies (#28537) 2023-12-30 05:29:03 +00:00
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml
.stylelintrc.yaml Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
.yamllint.yaml fully replace drone with actions (#27556) 2023-10-11 06:39:32 +00:00
BSDmakefile Fix build errors on BSD (in BSDMakefile) (#27594) 2023-10-13 15:38:27 +00:00
build.go User/Org Feed render description as per web (#23887) 2023-04-04 04:39:47 +01:00
CHANGELOG.md Fix release link in changelog for v1.21.0 2023-11-14 15:03:49 +01:00
CODEOWNERS [META] Add CODEOWNERS files 2024-02-05 14:44:33 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2024-02-05 14:44:32 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process 2024-02-05 13:33:59 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2024-02-05 13:33:59 +01:00
go.mod [GITEA] Use existing error functionality 2024-02-05 16:09:40 +01:00
go.sum [GITEA] Use maintained gziphandler 2024-02-05 16:09:40 +01:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2024-02-05 14:44:32 +01:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2024-02-05 14:44:33 +01:00
MAINTAINERS Apply to become a maintainer (#27522) 2023-10-08 10:36:40 -04:00
Makefile [SEMVER] 7.0.0+0-gitea-1.22.0 2024-02-05 15:08:04 +01:00
package-lock.json Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
package.json Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
playwright.config.js Update JS dependencies and eslint config (#21388) 2022-10-10 20:02:20 +08:00
poetry.lock Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
poetry.toml Clean up pyproject.toml and package.json, fix poetry options (#25327) 2023-06-18 18:13:08 +00:00
pyproject.toml Update JS and PY dependencies, build for es2020 browsers (#28977) 2024-02-02 09:36:32 +00:00
README.md [DOCS] README 2024-02-05 14:44:32 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md (squash) v1.21.5-0 (squash) go-git 2024-02-05 15:11:35 +01:00
vitest.config.js Use vitest globals (#27102) 2023-09-27 04:37:13 +00:00
webpack.config.js [API] Forgejo API /api/forgejo/v1 2024-02-05 14:44:32 +01:00

README.md

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.