-
Notifications
You must be signed in to change notification settings - Fork 0
08 14 2020
Chuck Liu edited this page Aug 15, 2020
·
1 revision
To do list:
1. Create a swagger UI
2. We choose to use React framwork
3. Create a schema for our library
For our teams:
1.Each teammate should has couple small milestones for theirself. We can reach some goals each week.
2.Do not wait until the next meeting to share your work. Please communicate with your teammates frequently.
3.If you got stuck, please post your questions on slack, your mentor and teammates are willing to help you to solve it.
4.A reminder for our teammates, this is week 6 as our school calendar, we should at least create a demo at week 10.
- Branch name: When we create a branch name please use issue-(number) instead of using your own name.
- Committed message: The information should include issue numbers and the things you did. This is good to help the manager to reverse.
- Reviewer: When you pull a request please add reviewer so that GitHub will notice the reviewer to review.
- Merging: When the reviewer merges the code he needs to download, run, and test it.
What does the API structure look like?

What do branches merging look like?
