Make sure the name of your feature branch describes what you're trying to fix. ![]() Create a branch with a descriptive name of the issue you are solving.Git remote add your_github_username_here Please follow the following procedure when creating features to avoid unnecessary rejections:Äo this the first time (Cloning & Forking): If you want to fix a new issue that's not listed there, create the issue, see if If you want to contribute code, start by looking at the open issues on. We prefer well named methods and code re-usability than a lot of comments. ![]() Look and test your code well before submitting patches. If it's too hard to explain what you're doing, you're probably making things more complex than they already are.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |