Skip to content

Workflow

Oculux edited this page Jul 21, 2024 · 8 revisions

If you haven't set up your local repository yet, check out Getting Started. Otherwise, read on!

🏃 Sprint Structure

  • [1] Wed: Sprint meeting
  • [2] Wed: Mid-sprint meeting

🎫 Tickets: How To

Important: see Conventions

  1. Tickets are assigned at sprint meetings
  2. Find your ticket on the Kanban Board and move it to 'in progress'
  3. If working in a pair, create a thread on Discord in the Tickets Channel to communicate
  4. Create a new branch for your ticket
  5. Check the requirements for your ticket and make sure you have a solid grasp of what to do! (If not, ask!)
    For visual designs, check out the Figma
  6. Work on your ticket, committing as you go
  7. When done, open a PR (choose 2 PR reviewers: Nate or Yvonne, +1 more) and move your ticket to 'in review'
  8. Once merged, move your ticket to 'resolved'

Figma

Link (it's a bit of a mess from 2023, but you can find the finalised designs in the bottom left - everything else can be ignored)

🌳 Handy Git Commands

  • git clone <link>
  • git pull
  • git branch <newbranchname>
  • git checkout <branchname>
  • git checkout -b <newbranchname> (make new branch & checkout in one)
  • git add .
  • git commit -m "<message>"
  • git push (if you haven't published your branch yet, git will prompt you - run the command they give)
Clone this wiki locally