Contribute to Luna
Do you want to make a pull request to Luna? Great! Through it is important to follow some rules.
Where do I publish my pull request?
If you’re pull request contains bugfixes, you can add the pull request to the then current branch (for example: version3.1), do not add a pull request to master, stable or unsupported branches. When a bugfix alters the way Luna functions, you’re probably better of adding the pull request to the branch that’s then in development.
If you’re pull request contains new features, changes in behavior, code additions or large amounts of revised code, please add the pull request to the then current development branch, if you create a pull request to any other branch, we’ll have to close your merge request as we can not add features to a stable and already released version of Luna or any other branch that is not named “versionX.X”. If the current development branch is post beta, you’ll have to add your pull request to the next development branch instead.
Do I have to create a ticket for a feature I want to see in Luna?
Depends on it, if you’re able to code it yourself and think: “Why not, even if it isn’t allowed, at least I’ve a working example for my own fork!”, then no. If you create this feature and add a pull request to the official Luna repository, it will create a ticket for you. Describe properly what the pull request contains, how better explained, the more is the chance that it will make it to the official Luna core.
Can I change to Luna core in my own coding style?
If you want you’re code to become later part of the official Luna core, no, you can’t. We have to keep the Luna core readable and consitent. That is very important. That’s why we have coding conventions. They are very important, and if your code doesn’t apply to them, we can’t merge your pull request in any case. Of course, if you have no intention to pull your changes to the Luna core, go ahead, you’re free to do whatever you want.