provide a link to to issue in the description. (PR for #222 Deprecated API usage) so that it is easy for the mentors to connect your pr with the corresponding issues.
Also squash your your commits untill you are dealing with seprate issues.
This ones is suggestion that don't make changes in your develop branch i.e. create a separate branch based on sashafierce:develop so don't have to delete your forked repo every time you want to contribute. But since you have already done so you can create new branch from sashafierce:develop using the previous commit history of the systers:develop.
@sashafierce please follow the PR practices: https://github.com/systers/FirstAide-Android/wiki/PR-Best-Practices
Following I could think of:
provide a link to to issue in the description. (PR for #222 Deprecated API usage) so that it is easy for the mentors to connect your pr with the corresponding issues.
Also squash your your commits untill you are dealing with seprate issues.
This ones is suggestion that don't make changes in your develop branch i.e. create a separate branch based on sashafierce:develop so don't have to delete your forked repo every time you want to contribute. But since you have already done so you can create new branch from sashafierce:develop using the previous commit history of the systers:develop.