Best way to use git to maintain support for multiple MC versions?

• ModMenu

  7 460 7.6 Java

  A menu for, you guessed it, mods!

  

I'm getting started with modding and right now I'm really struggling to understand how to use git to maintain support for multiple versions of Minecraft for my mod. What many mods do is have every edition its own branch, like https://github.com/TerraformersMC/ModMenu/branches. However, this seems overkill when it's literally only one line of difference between 1.19.2 and 1.19.3. This answer seems to explain why I'm having so many issues getting this to work: Because that's not how git is supposed to be used. It's not meant to have half a dozen different similar but different projects maintained, it's meant to have one project worked on and maintained, with branches used to temporarily store changes before merging into main, not as permanent housing for separate versions. But I can't think of any better way to manage the different versions of my mod. I'm new to git and maybe that's why it's so confusing to me, and it'd make more sense once I have more experience. But all I really want is to have a main branch with the project, and a "branch" that says "this branch is always identical to main, except this FileName.java is different and doesn't reflect main's version of FileName.java." Is there any way for me to do that?

• InfluxDB

  www.influxdata.com featured

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

Suggest a related project