BookStack Has Migrated From GitHub to Codeberg

Dan Brown posted on the 28th of April 2026

I’m pleased to say that the project has now fully migrated management of all repositories from GitHub to Codeberg. The main BookStack project repository now lives here:

https://codeberg.org/bookstack/bookstack

Impact of This Change

There should be no impact to normal release version usage.

Care has been taken to ensure minimal impact to BookStack end users. The original GitHub repository is still staying around, and will essentially act as a mirror of the codebase on Codeberg, so any existing instances fetching updates from GitHub can continue to do so.

Production Deployment Usage

For production-level deployment using Git going forward, we’d suggest using https://source.bookstackapp.com/bookstack.git. This is our self-hosted Git mirror, which currently mirrors the Codeberg projects, but provides us control in the event we need to change platforms again in the future.

As said above, the GitHub repository will still be there, but if desired you could update an existing (standard/non-docker) installation to use this Git origin instead of GitHub by running the following from your BookStack install folder:

1

git remote set-url origin https://source.bookstackapp.com/bookstack.git

Watching & Following Releases

For those that have been following releases via our GitHub repository releases, we will still be publishing GitHub releases for a while, although eventually we will only create releases on Codeberg so it’s advised to watch/subscribe to them there instead:

• Releases Page
• RSS URL: https://codeberg.org/bookstack/bookstack/releases.rss

Contributions, Reporting Issues, Support etc…

We are no longer managing issues, feature requests, code contributions, support requests etc… via GitHub. This is now all managed via Codeberg. Any issues or pull requests raised on GitHub will be closed right away.

All existing open GitHub issues and pull requests have been closed, with links to their new home on Codeberg provided in a closing comment. All existing closed and open issues have been migrated into Codeberg under the same IDs, so everything’s in one place.

If you were following an issue/thread before, you will need to subscribe to the new equivalent Codeberg thread to continue to receive updates.

Developers

For those working with the BookStack codebase for development, it’s advised to get involved with the project on Codeberg, and update any existing repos using GitHub to instead point to Codeberg:

1

git remote set-url origin https://codeberg.org/bookstack/bookstack.git

Donations & Sponsors

For those donating or sponsoring the project via GitHub sponsors, there’s no urgent need to move these. Both BookStack’s account, and my personal account, will continue to be on GitHub, and I will continue to accept sponsors/donations via this route. If you want to move your sponsorship/donations regardless, we do also accept donations via KoFi. Further details can be found on our donations page.

Expecting A Little Turbulence

Over the last two days I’ve been going through many pre-planned steps to try to make the change a smooth one. This includes updating our CI processes (which were using GitHub actions), changing how we integrate with Crowdin for translation management, and creating scripts to manage old issues.

I’ve also been updating many references across our website, blog and codebases to now reference the new Codeberg home. It’s likely that there are many missed, and there are many more which are on external sites not under my control so it may be common to see the GitHub repo referenced across the internet for a while. That’s to be expected after being at that GitHub address for over a decade.

I’ll be putting together a BookStack patch release later this week which will be a good test of the new systems and processes in place. Hopefully it will all be smooth, but we’ll have to see.

Why The Move?

For deeper details you can check our planning here which goes back to 2023, but the main points are as follows:

• GitHub has been losing focus on being a good code management platform, and has instead been focused on pushing AI tooling in ways that I believe could be counterproductive, and a general hindrance to open source maintainership.
• I was unable to make changes to our website repository due to (Git-LFS) activity limits which could be consumed by any public person/actor (and therefore were completely out of our control).
• Codeberg, a non-profit community-led organization that’s providing a service using an open source solution, is much more aligned to the values that we want to support and portray in BookStack relative to Microsoft (GitHub’s owner).

Why Did it Take so Long?

I moved most of our repositories to Codeberg back in July of 2024, but was hesitant to move the main repository due to its more significant use and integration with various systems. Last year, after deciding there was never going to be a perfect time to migrate, I decided that I would migrate the core project right at the start of 2026.

Unfortunately, there were some technical issues when it came to migrating the core project. The high amount of issues and pull requests resulted in longer migration times, which increased the likelihood of running into issues. The specific issues faced can be found documented in the Codeberg community threads here and here.

Eventually, thanks to some great efforts by Codeberg & Forgejo maintainers (Shout out to @Gusted), along with starting the process at 3AM on a lucky quiet Sunday night/Monday morning, the migration finally completed.

Header Image Credits:  Photo by Vyacheslav Argenberg (CC-BY-4) - Image Modified