Use GitHub Issues to track your work. At the start of the project, break your application down into small tasks and create an issue for each one. Assign issues to team members so everyone knows who is working on what. Close the issues when the related pull request is merged.
Each team member can work on any part of the project, or you can assign roles. Roles can match people's interests, skills, and chosen track. For example:
Find a time that works for everyone and hold a short daily standup (recommended: 10–15 minutes). Each person answers three questions: What did I do yesterday? What am I doing today? Is anything blocking me? Standups are on weekdays only, no standups on weekends.
Mentors are not required to join the standups.
Use the dedicated Slack group for your team. Avoid creating private side conversations. Your mentors are in the group because they want to stay involved and help out. If they can't see the conversation, they can't help. One-on-one messages are fine for personal matters or quick coordination, but technical discussions and decisions should happen in the shared group.
You can use the Slack Huddle feature to have a video call between the team if needed.
Follow this standard workflow for every change:
main (e.g. feature/add-search-endpoint).main.Never commit directly to main.
Every pull request needs at least one approval before merging. Do not just click "approve". Read the code carefully. Leave comments when something is unclear, could be improved, or looks wrong. Asking questions in a review is not criticism. It is how professional teams work. Good code reviews catch bugs early and help the whole team learn.
The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*
Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.