Workflow Guide - matai-2020/ABA GitHub Wiki

When beginning a ticket

  1. Assign yourself to the ticket.
  2. Read the whole ticket, then check the [Wiki] if additional information is required.
  3. If you need any further clarification about how the ticket should be worked on, speak to your final project team members.
  4. When you feel you have all the information needed to commence development, move the ticket to In Progress.
  5. Remember to add a black estimate tag/time estimation label to the ticket. Estimate how long you think it will take to complete (1-10).
  6. git pull latest on the dev branch.
  7. Create a new branch with the following naming: [issue-number]-[brief-title-in-kebab-case], e.g: 5-create-income-component

When finishing a ticket

  1. Check that your work is fully tested. You didn't forget to write tests, did you?
  2. git pull origin dev into your branch.
  3. Handle any merge conflicts, check all tests are passing and then push your branch to GitHub.
  4. Get a review done by one of your team members;
    • Sit alongside a team member to review your code and merge changes.

Once your PR is complete

  1. Add a white actual tag to the ticket to indicate how long it took to complete.
  2. You can now click the magic green Merge button! Merge your code into dev 😁.
  3. Delete your branch.
  4. Celebrate! But not for too long, there's more work to do yet! 😉
  5. Take a look at other Open and unassigned tickets in preparation for what you might work on next.
  6. Ask your other team members what ticket needs to be address next, THINK MVP.