Beyond coding. We forge.
Find a file
Gusted da6a19ad16
[GITEA] Improve HTML title on repositories
- The `<title>` element that lives inside the `<head>` element is an important element that gives browsers and search engine crawlers the title of the webpage, hence the element name. It's therefor important that this title is accurate.
- Currently there are three issues with titles on repositories. It doesn't use the `FullName` and instead only uses the repository name, this doesn't distinguish which user or organisation the repository is on. It doesn't show the full treepath in the title when visiting an file inside a directory and instead only uses the latest path in treepath. It can show the repository name twice if the `.Title` variable also included the repository name such as on the repository homepage.
- Use the repository's fullname (which include which user the repository is on) instead of just their name.
- Display the repository's fullname if it isn't already in `.Title`.
- Use the full treepath in the repository code view instead of just the
last path.
- Adds integration tests.
- Adds a new repository (`repo59`) that has 3 depths for folders, which
wasn't in any other fixture repository yet, so the full treepath for
could be properly tested.
- Resolves https://codeberg.org/forgejo/forgejo/issues/1276

(cherry picked from commit ff9a6a2cda)
(cherry picked from commit 76dffc8621)
(cherry picked from commit ff0615b9d0)
(cherry picked from commit 8712eaa394)
(cherry picked from commit 0c11587582)
(cherry picked from commit 3cbd9fb792)

Conflicts:
	tests/integration/repo_test.go
	https://codeberg.org/forgejo/forgejo/pulls/1512
(cherry picked from commit fbfdba8ae9)

Conflicts:
	models/fixtures/release.yml
	https://codeberg.org/forgejo/forgejo/pulls/1550
(cherry picked from commit 8b2bf0534c)
(cherry picked from commit d706d9e222)
(cherry picked from commit 6d46261a3f)
(cherry picked from commit f864d18ad3)
(cherry picked from commit 80f8620d0d)

[GITEA] Improve HTML title on repositories (squash) do not double escape

(cherry picked from commit 22882fe25c)
(cherry picked from commit 63e99df3d1)
(cherry picked from commit b65d777bc7)
(cherry picked from commit 2961f4f632)
(cherry picked from commit f7f723628c)
(cherry picked from commit 9ed7915826)
(cherry picked from commit 8b9ead4608)
(cherry picked from commit 50eeaf1fbc)
(cherry picked from commit ee6f32820e)
(cherry picked from commit bf337bed35)
(cherry picked from commit 6be9501ec0)
(cherry picked from commit b39860570d)
(cherry picked from commit 3f30f486d5)
(cherry picked from commit 5680ecdbe9)
2023-12-25 13:30:06 +01:00
.devcontainer devpod use go1.21 (#26637) 2023-08-21 16:20:50 +00:00
.forgejo [CI] upload the forgejo under test as an artifact for end-to-end (squash) merge feature branches 2023-12-25 10:33:07 +01:00
.gitea [WORKFLOW] yaml issue templates 2023-12-25 11:00:50 +01:00
assets Update go dependencies (#28518) 2023-12-19 09:18:42 +08:00
build Use Set[Type] instead of map[Type]bool/struct{}. (#26804) 2023-08-30 06:55:25 +00:00
cmd [CLI] implement forgejo-cli 2023-12-25 10:25:16 +01:00
contrib Bump google/go-github to v57 (#28514) 2023-12-18 15:42:04 -06:00
custom/conf [GITEA] add option for banning dots in usernames 2023-12-25 13:30:06 +01:00
docker Dockerfile small refactor (#27757) 2023-10-29 09:44:06 +08:00
docs Make offline mode as default to no connect external avatar service by default (#28548) 2023-12-21 07:42:16 +00:00
models [GITEA] Improve HTML title on repositories 2023-12-25 13:30:06 +01:00
modules [GITEA] add option for banning dots in usernames 2023-12-25 13:30:06 +01:00
options [GITEA] add option for banning dots in usernames 2023-12-25 13:30:06 +01:00
public [API] Forgejo API /api/forgejo/v1 2023-12-25 11:00:49 +01:00
releases/images [DOCS] RELEASE-NOTES.md 2023-12-25 11:00:47 +01:00
routers [GITEA] Improve HTML title on repositories 2023-12-25 13:30:06 +01:00
services [SECURITY] Rework long-term authentication 2023-12-25 11:02:13 +01:00
snap set version in snapcraft yaml 2023-09-13 23:20:46 -04:00
templates [GITEA] Improve HTML title on repositories 2023-12-25 13:30:06 +01:00
tests [GITEA] Improve HTML title on repositories 2023-12-25 13:30:06 +01:00
web_src [API] Forgejo API /api/forgejo/v1 2023-12-25 11:00:49 +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 [DEADCODE] update deadcode-out (squash) update 2023-12-25 11:51:45 +01:00
.dockerignore Move public asset files to the proper directory (#25907) 2023-07-18 18:06:43 +02:00
.editorconfig Add markdownlint (#20512) 2022-07-28 09:22:47 +08:00
.eslintrc.yaml Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01:00
.gitattributes [META] Use correct language for .tmpl 2023-12-25 11:00:49 +01:00
.gitignore [DEVELOPMENT] added /local/ to .gitignore 2023-12-25 11:02:14 +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 Enable markdownlint no-duplicate-header (#27500) 2023-10-07 15:30:21 +02:00
.npmrc Upgrade to npm lockfile v3 and explicitely set it (#23561) 2023-03-18 19:38:10 +01:00
.spectral.yaml Add spectral linter for Swagger (#20321) 2022-07-11 18:07:16 -05:00
.stylelintrc.yaml Enable shorthands in declaration-strict-value linter (#27597) 2023-10-13 08:19:21 +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 2023-12-25 11:00:50 +01:00
CONTRIBUTING.md [DOCS] CONTRIBUTING 2023-12-25 10:58:10 +01:00
DCO Remove address from DCO (#22595) 2023-01-24 18:52:38 +00:00
Dockerfile [CI] Forgejo Actions based release process 2023-12-25 10:31:08 +01:00
Dockerfile.rootless [CI] Forgejo Actions based release process 2023-12-25 10:31:08 +01:00
go.mod Update go dependencies (#28518) 2023-12-19 09:18:42 +08:00
go.sum Update go dependencies (#28518) 2023-12-19 09:18:42 +08:00
LICENSE [DOCS] LICENSE: add Forgejo Authors 2023-12-25 11:00:49 +01:00
main.go [SEMVER] store SemVer in ForgejoSemVer after a database upgrade 2023-12-25 11:00:50 +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 2023-12-25 11:02:14 +01:00
package-lock.json Fix the scroll behavior for emoji/mention list (#28597) 2023-12-24 13:08:41 +08:00
package.json Update JS and PY dependencies (#28120) 2023-11-20 01:02:57 +01: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 (#28120) 2023-11-20 01:02:57 +01: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 (#28120) 2023-11-20 01:02:57 +01:00
README.md [DOCS] README 2023-12-25 10:58:10 +01:00
RELEASE-NOTES.md [DOCS] RELEASE-NOTES.md 2023-12-25 11:00:47 +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 2023-12-25 11:00:49 +01:00

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.