A change that breaks one Minecraft version, such as a missed or bad port, is only noticed when someone builds that version, or in the ~18-minute release workflow after tagging.
Proposal
A Gitea Actions workflow, .gitea/workflows/check.yml, that runs on every pull request (and on pushes to master) and compiles all versions (./gradlew compileJava), with the common submodule checked out. The PR can't be merged green if any version fails to compile.
It's compile-only, so it's faster than the release build, which also remaps and packages every jar.
It uses the same runner and Java 21 setup as the release workflow.
Related: #8 (closed in favour of keeping separate version modules, with this tooling).
## Problem
A change that breaks one Minecraft version, such as a missed or bad port, is only noticed when someone builds that version, or in the ~18-minute release workflow after tagging.
## Proposal
A Gitea Actions workflow, `.gitea/workflows/check.yml`, that runs on every pull request (and on pushes to `master`) and compiles **all** versions (`./gradlew compileJava`), with the `common` submodule checked out. The PR can't be merged green if any version fails to compile.
- It's compile-only, so it's faster than the release build, which also remaps and packages every jar.
- It uses the same runner and Java 21 setup as the release workflow.
Related: #8 (closed in favour of keeping separate version modules, with this tooling).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
A change that breaks one Minecraft version, such as a missed or bad port, is only noticed when someone builds that version, or in the ~18-minute release workflow after tagging.
Proposal
A Gitea Actions workflow,
.gitea/workflows/check.yml, that runs on every pull request (and on pushes tomaster) and compiles all versions (./gradlew compileJava), with thecommonsubmodule checked out. The PR can't be merged green if any version fails to compile.Related: #8 (closed in favour of keeping separate version modules, with this tooling).