A Git service designed specifically for Scratch visual programming projects, based on Gitea.
BlockCommit is an exclusive Git designed specifically for Scratch visual programming projects. Adapt to Scratch project file formats, provide easy-to-use version tracking, submission, and collaboration capabilities, allowing Scratch developers to easily implement project version management.
Topics: git · backend · gitea · scratch · scratch3 · turbowarp
BlockCommit is based on Gitea and provides specialized support for Scratch/TurboWarp .sb3 project files:
- SB3 Project Support: Native support for Scratch 3.0 project files with visual diff display
- Block-Level Diff: Semantic diff visualization for Scratch blocks using ScratchBlocks syntax
- Multi-Language Support: Available in multiple languages for international Scratch communities
- Easy Collaboration: Seamless version control for Scratch projects
- Self-Hosted: Deploy your own BlockCommit instance for privacy and control
As BlockCommit is written in Go, it works across all the platforms and architectures that are supported by Go, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures.
- SB3 File Parsing: Automatic parsing and analysis of Scratch project files
- Visual Block Diff: Display block changes in an intuitive visual format
- Script Tracking: Track script additions, modifications, and deletions
- Asset Management: Track changes to costumes, sounds, and other assets
- Variable & List Diff: Monitor variable and list changes across versions
- Full Git integration with branch management, pull requests, and issue tracking
- Collaborative code review and discussion
- Wiki and project documentation
- CI/CD integration with GitHub Actions compatibility
- Team and organization management
From the root of the source tree, run:
TAGS="bindata sqlite sqlite_unlock_notify" make build
The build target is split into two sub-targets:
make backendwhich requires Go Stable, the required version is defined in go.mod.make frontendwhich requires Node.js LTS or greater and pnpm.
After building, a binary file named gitea will be generated in the root of the source tree by default. To run it, use:
./gitea web
Then access BlockCommit at http://localhost:3000 (default port).
When viewing diffs for .sb3 files, BlockCommit provides:
- Script Changes: Visual display of added, modified, and deleted scripts
- Block-Level Diff: Detailed view of individual block changes
- Summary Statistics: Quick overview of project changes (targets, scripts, blocks, variables, etc.)
- Asset Tracking: Changes to costumes, sounds, and other resources
Expected workflow is: Fork -> Patch -> Push -> Pull Request
Note
- YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
- If you have found a vulnerability in the project, please write privately to the maintainer.
- Maintainer: NeuronPulse
- Original Project: Gitea
This project is licensed under the MIT License. See the LICENSE file for the full license text.
BlockCommit is based on Gitea, a community-managed lightweight code hosting solution written in Go.
Thanks to:
- The Gitea community for the excellent codebase
- scratchblocks for block visualization
- parse-sb3-blocks for SB3 parsing utilities
The goal of this project is to make the easiest, fastest, and most painless way of setting up a self-hosted Git service.
As Gitea is written in Go, it works across all the platforms and architectures that are supported by Go, including Linux, macOS, and Windows on x86, amd64, ARM and PowerPC architectures. This project has been forked from Gogs since November of 2016, but a lot has changed.
For online demonstrations, you can visit demo.gitea.com.
For accessing free Gitea service (with a limited number of repositories), you can visit gitea.com.
To quickly deploy your own dedicated Gitea instance on Gitea Cloud, you can start a free trial at cloud.gitea.com.
You can find comprehensive documentation on our official documentation website.
It includes installation, administration, usage, development, contributing guides, and more to help you get started and explore all features effectively.
If you have any suggestions or would like to contribute to it, you can visit the documentation repository
From the root of the source tree, run:
TAGS="bindata" make build
or if SQLite support is required:
TAGS="bindata sqlite sqlite_unlock_notify" make build
The build target is split into two sub-targets:
make backendwhich requires Go Stable, the required version is defined in go.mod.make frontendwhich requires Node.js LTS or greater and pnpm.
Internet connectivity is required to download the go and npm modules. When building from the official source tarballs which include pre-built frontend files, the frontend target will not be triggered, making it possible to build without Node.js.
More info: https://docs.gitea.com/installation/install-from-source
After building, a binary file named gitea will be generated in the root of the source tree by default. To run it, use:
./gitea web
Note
If you're interested in using our APIs, we have experimental support with documentation.
Expected workflow is: Fork -> Patch -> Push -> Pull Request
Note
- YOU MUST READ THE CONTRIBUTORS GUIDE BEFORE STARTING TO WORK ON A PULL REQUEST.
- If you have found a vulnerability in the project, please write privately to security@gitea.io. Thanks!
Translations are done through Crowdin. If you want to translate to a new language, ask one of the managers in the Crowdin project to add a new language there.
You can also just create an issue for adding a language or ask on Discord on the #translation channel. If you need context or find some translation issues, you can leave a comment on the string or ask on Discord. For general translation questions there is a section in the docs. Currently a bit empty, but we hope to fill it as questions pop up.
Get more information from documentation.
We provide an official go-sdk, a CLI tool called tea and an action runner for Gitea Action.
We maintain a list of Gitea-related projects at gitea/awesome-gitea, where you can discover more third-party projects, including SDKs, plugins, themes, and more.
If you have questions that are not covered by the documentation, you can get in contact with us on our Discord server or create a post in the discourse forum.
Thank you to all our backers! 🙏 [Become a backer]
Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]
How do you pronounce Gitea?
Gitea is pronounced /ɡɪ’ti:/ as in "gi-tea" with a hard g.
Why is this not hosted on a Gitea instance?
We're working on it.
Where can I find the security patches?
In the release log or the change log, search for the keyword SECURITY to find the security patches.
This project is licensed under the MIT License. See the LICENSE file for the full license text.
