Building instructions #9

Closed
opened 2025-09-08 19:12:39 +00:00 by Minecon724 · 0 comments
Owner

You should follow the official Forgejo Contributor Guide. However it lacks a few useful things, below you can find.

It's recommended to use the devcontainer.

Building

To build, the official instructions generally suffice

Build a single image for multiple architectures:

podman build --platform linux/amd64,linux/arm64 --manifest user/repo:tag .

Replace the tag. You can add more architectures, if you wish.

Live reload

TAGS='sqlite sqlite_unlock_notify' make watch

Merge

Make sure you checked out the branch to merge to.

  1. git remote add upstream https://codeberg.org/forgejo/forgejo.git
    
  2. git fetch --no-tags upstream
    
  3. git merge upstream/$BRANCH
    

Tag a release

git tag $TAG
git push origin tag $TAG
You should follow the official [*Forgejo Contributor Guide*](https://forgejo.org/docs/next/contributor). However it lacks a few useful things, below you can find. It's recommended to use the devcontainer. ### Building To build, [the official instructions generally suffice](https://forgejo.org/docs/next/contributor/from-source/) Build a single image for multiple architectures: ```bash podman build --platform linux/amd64,linux/arm64 --manifest user/repo:tag . ``` Replace the tag. You can add more architectures, if you wish. ### Live reload ```bash TAGS='sqlite sqlite_unlock_notify' make watch ``` ### Merge Make sure you checked out the branch to merge to. 1. ```bash git remote add upstream https://codeberg.org/forgejo/forgejo.git ``` 2. ```bash git fetch --no-tags upstream ``` 3. ```bash git merge upstream/$BRANCH ``` ### Tag a release ``` git tag $TAG git push origin tag $TAG ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: git724/forgejo#9
No description provided.