Minecraft mods+ Github?

[whitephoenix]

I uploaded my first mod to Github, after some difficulty. I only uploaded the SRC folder, there isn't anything outside that that I am forgetting is there?

 

Also I want to know how to contribute to other people's mods on Github. What is the setup process?

[larsgerrits]

A standard modding github should look like this: https://github.com/Larsg310/MineTech

[whitephoenix]

A standard modding github should look like this: https://github.com/Larsg310/MineTech

Okay thank you. I'll upload the rest soon.

[Draco18s]

I uploaded my first mod to Github, after some difficulty. I only uploaded the SRC folder, there isn't anything outside that that I am forgetting is there?

 

The build.gradle file.

 

Which is why I dislike the project setup for Forge Gradle.  Changing from one mod to another either requires that I duplicate a large portion of common files or moving around a bunch of stuff.  And makes setting up a git repo annoying, because almost ever subfolder other than /src doesn't need to be on git.  Also most of the files there too other than build.gradle...

 

 

Highlighted stuff is part of the project and should be on GitHub.  Everything underlined in blue is technically part of the project, but should not be on GitHub (you may or may not have build.properties or an /etc or /lib directory, depending on your needs).

 

(And Lars pointed out that I missed a directory, ha!)

 

Also I want to know how to contribute to other people's mods on Github. What is the setup process?

 

Go to the mod.  Click "fork."  Or click "edit" on a file and GitHub will automagically fork it for you and drop you right into the edit window.  You can also clone-to-desktop.

[whitephoenix]

I uploaded my first mod to Github, after some difficulty. I only uploaded the SRC folder, there isn't anything outside that that I am forgetting is there?

 

The build.gradle file.

 

Which is why I dislike the project setup for Forge Gradle.  Changing from one mod to another either requires that I duplicate a large portion of common files or moving around a bunch of stuff.  And makes setting up a git repo annoying, because almost ever subfolder other than /src doesn't need to be on git.  Also most of the files there too other than build.gradle...

-snip-

 

Highlighted stuff is part of the project and should be on GitHub.  Everything underlined in blue is technically part of the project, but should not be on GitHub (you may or may not have build.properties or an /etc or /lib directory, depending on your needs).

 

(And Lars pointed out that I missed a directory, ha!)

 

Also I want to know how to contribute to other people's mods on Github. What is the setup process?

 

Go to the mod.  Click "fork."  Or click "edit" on a file and GitHub will automagically fork it for you and drop you right into the edit window.  You can also clone-to-desktop.

 

Interestingly enough, my mod doesn't have a build.properties or an etc folder

[Draco18s]

Interestingly enough, my mod doesn't have a build.properties or an etc folder

 

As I said, depends on what you're doing.

For me, /etc is where I keep the mcmod.info files for each of my submods (I could have called it /fluff if I wanted to).  build.properties is supposed to be for each submod's version number (but for whatever reason gradle complained it couldn't find the variables, so they got shoved into the build.gradle file).