Files
NEI-Integration/README.md
TDLM patch bot ced7fc2f5f
Build / build (push) Successful in 11m18s
Build / publish (push) Successful in 6m17s
chore: initial Stratum patch layer over GTNewHorizons/NEI-Integration
2026-11-15 23:14:59 +08:00

1.7 KiB

TDLM/NEI-Integration — patch layer over GTNewHorizons/NEI-Integration

This repository does not contain NEI-Integration's source. It contains:

Path What
upstream/ git submodule → GTNewHorizons/NEI-Integration, pinned to one commit
patches/ our changes, as ordered git format-patch files
settings.gradle.kts the layer's only build file: the Stratum version and stratum { }
.github/workflows/build.yml our CI: apply patches → build → publish to the TDLM registry
.github/workflows/upstream-sync.yml daily: bump upstream, re-apply patches, open a PR

The build never touches upstream/. ./gradlew applyPatches clones it into work/ (git-ignored), applies patches/*.patch with git am --3way, and Gradle runs inside work/.

Everyday commands

./gradlew applyPatches build                 # (re)create work/ = upstream + patches, then build
./gradlew upstream --tasks="runClient"       # any upstream task
./gradlew printVersion                       # the coordinate this commit publishes

Change or add a patch

./gradlew applyPatches
cd work
# edit, then: git commit --trailer "Co-authored-by: Cursor <[email protected]>" -am "what and why"   (one commit = one patch)
cd .. && ./gradlew exportPatches
git add patches && git commit --trailer "Co-authored-by: Cursor <[email protected]>"

Take new upstream changes

./gradlew updateUpstream

Policy

  • Upstream wins. Keep a patch only if upstream does not already have the behaviour.
  • Patches that are generally useful should be sent upstream and then dropped here.
  • Patches never carry publishing settings; Stratum owns the Maven identity and destination.