Tutorial Contributing Back To ESPEasy

From Let's Control It
Revision as of 00:02, 3 March 2017 by Psy0rz (talk | contribs) (Created page with "If you followed this tutorial: Tutorial_preparing_to_work_with_github and you've made some changes, they you're ready to contribute them back to us. This will make sure y...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

If you followed this tutorial: Tutorial_preparing_to_work_with_github and you've made some changes, they you're ready to contribute them back to us.

This will make sure your changes will be in the next release so you dont have to make the same changes again.

Also it makes ESPEasy better for everyone.

Before you continue, make sure that your changes adhere to our guidelines: ESPEasyDevelopmentGuidelines


Commitsing changes

When you commit a change, you add it to the git-history. Its best to make a commit for every logical thing you've did.

So if you are going to fix 2 different bugs, make a seperate commit for each one.

If you're working on a new plugin, its ok to do several commits during the development process. This might keep things more clear for yourself, and also allows you to undo mistakes by rolling them back.

If you really want to learn how to work with Git, we can recommend the free Pro Git book: https://git-scm.com/book/en/v2

Retrieved from "http://www.letscontrolit.com/wiki/index.php?title=Tutorial_Contributing_Back_To_ESPEasy&oldid=1558"