mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2026-10-07 16:01:11 +00:00
Copy of Forgejo intended to allow me to update major pages
https://forgejo.org
35d2a6245e
To begin addressing #7653 and #10363, this PR adds top-level headings to most public Repository pages, including:
- Issues (Open, Closed, All)
- Labels
- Milestones (Open, Closed)
- Pull requests (Open, Closed, All)
- Projects (Open, Closed)
- Releases
- Tags
- Packages
- Wiki (list with pages present)
- Activity (Pulse, Contributors, Code frequency, Recent commits)
- Actions (All workflows, Named workflow, No workflows)
The change adds some new translation strings, and new template logic on the relevant pages to display translatable text as headings. The re-used existing translation strings seem to have already been used elsewhere in similar contexts, and therefore seemed intuitive for inclusion as page headings as well.
The attached video `headings-first-go.webm` shows me slowly clicking through the new pages, with their headings, in the order listed above, navigating from the page "Open issues", to "Closed issues", to "All issues", to "Labels", to "Open milestones", etc. This video does not include Packages, Wiki, Activity, or Actions.
The additional attached videos show the Pulse page (the default repo Activity view), whose heading now reads "Activity between September 2, 2026 and September 9, 2026", then proceeding to the various other activity pages. Each page's load state has been lengthened to demonstrate the new heading layouts, including error states.
This PR only adds headings to Repository pages for now. Several other Forgejo webpages are also affected by #7653, and some pages might also do well with additional explanatory text, documentation links, etc. (What the heck is a "Milestone" anyway, to someone who hasn't seen the concept at another forge?) I can add such explainers in this PR if that is wanted, or we can save these for discussion later. I welcome feedback on this point.
## Testing these changes
1. Open Forgejo locally using `make build frontend && test-e2e-debugserver`
2. Navigate to the above-named pages
3. Look at headings, ensure consistency.
You may test most headings at any repository, many have all units enabled. For Actions, consider testing at `/user2/test_action_run_search/actions`. You may need to log in to `user2` first. (The password is `password`).
To test Activity failure states, consider adding `await sleep(4000)` to the start of the `fetchGraphData` method, just after `isLoading` is first set, in `web_src/js/components/Repo*.vue` as appropriate, then exit the devserver during the load state.
## Checklist
The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. All work and communication must conform to Forgejo's [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md). There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org).
### Compliance
- [x] I confirm that I make this contribution in accordance with [Forgejo's AI Agreement](
|
||
|---|---|---|
| .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.