Flujo de trabajo de Git para la API e implementaciones

Desarrollo de la API

The basic process of adding your changes is explained in the Como usar Git(Hub) section. On top of that we suggest that you create your new branch with a meaningful name. With the new branching model, you need to be aware which branch you need to base your PRs on and where it should get merged afterwards. Read about the new branching and versioning model here: Repository Branch Layout

Additionally, we require that you ensure the module will compile with gradle compileJava. This will run a simple build of the source files. When finished successfully, you can PR your changes to SpongeAPI repo.

Desarrollo de la Implementación

The process for the implementations is almost the same as for the API. You add your changes as described in Como usar Git(Hub). Note that you should give your branches a meaningful name. With the new branching model, you need to be aware which branch you need to base your PRs on and where it should get merged afterwards. Read about the new branching and versioning model here: Repository Branch Layout

Corre gradle compileJava para comprobar si todo compila sin errores.

Since you are working on the implementation, there is a possibility that your work included changes in the API. This is okay. Just remember to ensure the pointers for the version of SpongeAPI match the version of your branch prior to committing and pushing. To do this, you may need to add the submodules to the commit (with git add SpongeAPI and/or git add Mixin) prior to committing on your implementation work.

Puedes abrir una solicitud de extracción una vez que su entrega sea lanzada a su bifurcación o al repositorio.