Skip to main content

Develop

The day-to-day surface for engineering work on fremforge. Most of these pages map one-to-one to a Forgejo concept; we call out where fremforge layers its own behaviour on top.

Pushing large changes

Git over HTTPS to https://frem.sh/<org>/<repo>.git is fronted by the CDN edge, which caps single requests at 4 MB. A git push whose pack file exceeds that returns 413 Payload Too Large.

For pushes over 4 MB use SSH instead:

git remote set-url origin git@frem.sh:<org>/<repo>.git
git push

SSH (port 22) connects directly to the Git origin and has no body cap — use it for large initial pushes, repos with big binary assets (LFS pointers aside), or git push --all on a long-lived branch with many objects. The standard clone via HTTPS still works at any size (only the push direction has the cap).

If SSH is blocked on your network and you’re hitting the cap regularly, contact support — we can grant you access to a direct-origin HTTPS hostname that bypasses the CDN for pushes.

What’s in here

  • Issues and PRs, the issue tracker, code review flow, mergeability rules.
  • Wiki and public docs, per-repo internal wiki and the opt-in public mirror at frem.sh/<org>/<repo>/wiki.
  • Packages, npm, Maven, container, generic. Quotas and overrides.
  • Releases, Git tag releases, attachments, signed checksums.
  • Dependency updates, the platform-wide Renovate bot, schedules, opt-outs.
  • Marketplace compat, which GitHub Actions work as-is, which need a thin wrapper.
  • AI, IDE assistant access, model picker, the agent-identity OAuth roadmap.