Repository navigation
chore: keep templates on main and call the shared CI from this branch - #3
Merged
Merged
Conversation
- remove duplicated issue/PR templates: GitHub reads them from the default branch only - replace the inline workflow with a thin caller of main's build-reusable.yml - CONTRIBUTING/README: point global rules and templates at main - add Unix gradlew, use <mod_version> for the jar name, single-target testing docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
改了什么
目标分支
neoforge-mc1.21.1），不是mainmain，并说明需要 cherry-pick 到哪些版本分支fabric/、forge/、versions/）带进这个 PR自测
./gradlew build（Windows：.\gradlew.bat build）通过，默认目标 1.21.1-PmcTarget验证过build/、run*/、.ogg、本地配置、IDE 文件关联 Issue
Fixes #