Git Workflow voor API en implementaties
De API ontwikkelen
The basic process of adding your changes is explained in the Hoe u Git(Hub) moet gebruiken 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.
De implementatie ontwikkelen
The process for the implementations is almost the same as for the API. You add your changes as described in Hoe u Git(Hub) moet gebruiken. 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
Voer gradle compileJava
uit om te controleren of alles zonder fouten compileert.
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.
U kunt een pull request openen zodra uw commit is gepusht naar uw fork of repository.