Kanban Board Guide - HexCorpProgramming/HexCorpDiscordAI GitHub Wiki

Viewing the board

  1. Go to the “Projects” tab on the repo.
  2. Click on “HexCorp Mxtress AI”.

Creating an issue/ticket

  1. Go to the Issues tab on the repo, and click the nice green “New Issue” button.
  2. Fill out the details of your issue.
  3. Add the appropriate labels from the right-hand column.
  4. Choose “HexCorp Mxtress AI” from the Projects section in the right-hand column.
  5. Optionally, assign a person/drone to the new issue.
  6. Click the “Submit new issue” button.
  7. A new ticket is automatically created in the board under “Ready to work on”. If this doesn’t apply to your ticket, manually move the corresponding card over to the “Future ideas” or “Needs refining” columns.

Starting work on a ticket

  1. Open the project board.
  2. Click on the ticket title to expand the details view.
  3. Under “Assignees”, click the “assign yourself” button.
  4. Manually move the ticket to “In Progress”.
  5. Create a new branch, and work your magic!

Requesting a review

You have two options:

  1. Create a pull request. In the details/comments section for the PR, mention the ticket number before or after a keyword [#ticketNo close(s/d), #ticketNo fix(es/ed), #ticketNo resolve(s/d)]. This automatically links your PR to your ticket. Do not add the PR to the board under Projects, as this will create a duplicate card.
  2. Assign people/drones to your pull request.
  3. Ticket is automatically moved to “Review in progress”.

Or:

  1. Create a pull request. Do not add the PR to the board under Projects, as this will create a duplicate card.
  2. Assign people/drones to your pull request.
  3. After your PR is created, go to your PR’s details view, and manually select the associated issue under “Linked issues”.

Finishing a review and merging PRs

  1. Complete your review as per normal.
  2. Ensure that the PR is linked to at least one issue.
  3. Merge the PR.
  4. If all of an issue’s linked PRs are merged, the issue is automatically closed. The ticket is automatically moved to “Ready to be deployed to live”.

Deploying updates

  1. Deploy update.
  2. Manually move tickets from “Ready to be deployed to live” to “Done”.

Appendix: Issues without associated PRs

When an issue is manually marked as “Closed”, the corresponding ticket in the board is automatically moved to “Ready to be deployed to live”. Manually move the ticket to “Done” if necessary.