- Go 81%
- go-html-template 10.9%
- JavaScript 2.7%
- CSS 2%
- TypeScript 1.8%
- Other 1.5%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
eca48134a4
All checks were successful
NHN Build Rootless / build-and-push (push) Successful in 6m29s
When the branch/tag picker is nested inside another Fomantic dropdown (e.g. the workflow-dispatch "Use workflow from" menu), its popup is trapped inside the outer .ui.dropdown .menu's stacking context (will-change: transform, opacity) and z-index cannot lift it out. Teleport the menu to <body> while open, wrapped in a .ui.dropdown shell so Fomantic's descendant selectors keep matching, and position it with position: fixed driven by the trigger's getBoundingClientRect. Outside-click detection now also accepts the teleported menu. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
| .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.mjs | ||
| 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.js | ||
| tailwind.config.js | ||
| tsconfig.json | ||
| vitest.config.ts | ||
| webpack.config.js | ||
NHN Git
Built on Forgejo. Branded for Norsk helsenett.
This repository is a fork of Forgejo with branding, theme, and a small number of UI tweaks tailored to Norsk helsenett (NHN). The underlying git service, its features, and its codebase are Forgejo's — we have only changed visual identity, the home page, default theme, and a handful of cosmetic UI elements.
What's changed compared to upstream Forgejo:
- NHN brand palette (brandpad.io/norsk-helsenett) wired into three new themes (
nhn-auto,nhn-light,nhn-dark);nhn-autois the default. - Logo, favicon, default avatar, and the loading animation use the NHN "knytninger" symbol.
- Home page redesigned with an NHN-flavored hero ("Vi knytter koden sammen") and feature grid.
- Flat navbar (no fill, no divider) and a few minor template adjustments.
templates/base/head_navbar.tmpl: removed the link to forgejo.org docs (NHN users have internal documentation).
Everything else — repository hosting, issues, pull requests, Actions, packages, settings, APIs — comes straight from Forgejo and is documented at forgejo.org/docs.
License
Forgejo, and therefore this fork, is distributed under the terms of the GNU GPL version 3.0 or any later version. Our changes are licensed under the same terms. The original Forgejo per-file copyright headers and LICENSE file are preserved.
If you received a binary built from this fork and want the corresponding source, it is this repository — the commit at the tip of main corresponds to the running binary at the time it was built.
Trademarks
"Forgejo" and the Forgejo logo are property of the Forgejo project and are not used in this fork. The NHN word mark and "knytninger" symbol are property of Norsk helsenett SF and used here for an internal NHN deployment.
The original Forgejo project description follows.
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.