sciwhiz12
commented
6 months ago If we split MDKs for each version into their own branches, there needs to be some considerations made:
- GitHub is only capable of creating repositories from template repositories based on the default branch (with an option to copy all other branches), even if you're viewing the repository from another branch. To reduce confusion, we'd have to convert the MDK repo into a regular repository -- not a template repository.
- We'd have to address how to direct users to the appropriate branch of the MDK repository for their version. Perhaps the default branch can be a blank branch, with a README that points to all extant version-branches in a table (with quick links for downloading the MDK as a ZIP)?
- We'd also consider how best to manage changes in NG7+ that affect multiple MC versions. Perhaps some form of automation which can backport (marked) PRs automatically?
BaKYCoder
Lots of people go to the MDK and look for an MDK for their specific MC version. Currently, people are confused on the 1.20.4 MDK and thinking it doesn't apply to 1.20.2.
A solution is to have a branch for each mc version so people can go to the MDK they specifically want and can just clone and run it without needing to change any versions.
(Was originally posted to Website repo https://github.com/neoforged/websites/issues/23. Oops. Moving to here properly)