You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 17, 2023. It is now read-only.
issues
I love the titles and descriptions for your issues, they show what you are working on, which is great! Don't forget to open an issue for every feature/part of code you are working on.
commits
You almost always reference an issue when you commit changes, which is great! ✨
Don't forget that if you don't have an issue, you can open one before you commit your changes, but of course the best option is to create an issue before starting to work on something.
pull requests
Your pull requests have better titles and descriptions, and most of them reference an issue. Try to assigns your team members as reviewers, so all of you go over the code before merging it. This is your chance to approve ✅ request changes ✖️ or ask any question about the code ❓
Please don't make any changes on master 😱 even if it seems like a small change. Every change should come from your code editor and terminal.
contributions
Try to aim to split the work evenly between all of the team members. You can see the current graph here.
You can do it by making sure you swap roles and laptops all the time ⏲️
Keep up the good work! 😄
The text was updated successfully, but these errors were encountered:
Overall, your github flow is nice 🎉
issues
I love the titles and descriptions for your issues, they show what you are working on, which is great! Don't forget to open an issue for every feature/part of code you are working on.
commits
You almost always reference an issue when you commit changes, which is great! ✨
Don't forget that if you don't have an issue, you can open one before you commit your changes, but of course the best option is to create an issue before starting to work on something.
pull requests
Your pull requests have better titles and descriptions, and most of them reference an issue. Try to assigns your team members as reviewers, so all of you go over the code before merging it. This is your chance to approve ✅ request changes ✖️ or ask any question about the code ❓
Please don't make any changes on master 😱 even if it seems like a small change. Every change should come from your code editor and terminal.
contributions
Try to aim to split the work evenly between all of the team members. You can see the current graph here.
You can do it by making sure you swap roles and laptops all the time ⏲️
Keep up the good work! 😄
The text was updated successfully, but these errors were encountered: