I recommand you to work with gitflow in order to keep your code clean and working.
The branch master will host the version of the code used in production (aka the code available on the store)
The branch develop contains the next version of the code before it is put in production. This branch contains code that is always working and not code currently being developped.
The branch feature/name_of_the_feature will contain the code currently in development related to a specific feature.
When the feature is done and fully tested the branch feature/name_of_the_feature is merged on develop.
When the new version of the code is put in production the branch develop is merge into master.
This is a "simplified" version of gitflow that I stated here.
For more informations about gitflow I strongly recommand you to look at those two links :
More a suggestion than a issue :
I recommand you to work with gitflow in order to keep your code clean and working.
When the feature is done and fully tested the branch feature/name_of_the_feature is merged on develop. When the new version of the code is put in production the branch develop is merge into master.
This is a "simplified" version of gitflow that I stated here. For more informations about gitflow I strongly recommand you to look at those two links :
Using branches on github is definitely the best practise to respect if you want to avoid loosing code or introduce bugs.
Anyway, if you don't care you can just ignore this issue. 😄