Using GitHub Projects

☑️ Using GitHub Projects

We use GitHub Projects (GitHub's description; our project) to organise programming tasks. It can be found as the first item in the Projects tab at the top of the repository / wiki. Here's how to use it for the FTC:

• 🎥 Alternatively, please see this video. (It also includes branches and merging, which we aren't using this year.)

Important: Labels

Each task is given one or more labels, and these are custom categories making it clear how you should implement the code to avoid collaboration merge conflicts. Please see the descriptions below, or click on the "Click for label meanings" task in the project:

Label	Meaning
🤖 ftc-autonomous	Code to be run in the autonomous period (no human interaction)
🎮 ftc-drivercontrolled	Code to be run in the driver-controlled (AKA TeleOp[erated]) period (human with gamepad)
📦 ftc-component	Code to be written as a separate component Java class in the components folder
🚪 ftc-opmode	Code to be written as an OpMode (code entrypoint) - pay attention to whether it is an Autonomous or TeleOp OpMode.

Creating a task

This task could be a bug you found in the production code while testing, or a feature that needs to be created.

1. Click the + button to create a task

In the Board view	In the Table view

2. Type a name for the task, and press Enter.
3. Click the name of the draft task created.
4. Click Edit.
5. Write a description. You can Ctrl+V any images to upload them, then click Update comment.
6. You can repeat steps 4-5 in the future to add any more details.
7. Click Convert to Issue on the right, and select 2024.
8. Click the button next to Labels and select labels as given above.
9. Do the same for Assignees, for whoever the task is for, if it has been agreed.

8	9

Changing the status of Tasks

1. Enter the Board view.
2. Click-and-Drag the task to the correct column.
3. The rest is automated!