All active development happens in our internal infrastructure. Public code is released through a two-mirror system: our internal repos are processed by SquashBot, published to CodeBerg as cleaned mirrors, and then mirrored again to GitHub.
👉 Primary public mirror (cleaned): Palace4Software on CodeBerg
🪞 Secondary mirror: Palace4Software on GitHub – synced from CodeBerg
🌐 Our Official Website: Visit Palace4Software
We use SquashBot to polish our public releases:
- Squashes commits per release – one clean commit per version tag
- Keeps things tidy - the public sees thoughtfully prepared releases
The workflow is:
Internal repo → SquashBot → CodeBerg (clean mirror) → GitHub (mirror of mirror)
This keeps our internal Git history separate from what you see publicly, while making sure our projects are easily accessible.
We're glad you're interested in what we're working on! 🚀

