add support for gh projects, standardize workflows (#17)

.github/ISSUE_TEMPLATE/bug-form.yml

@@ -2,33 +2,20 @@ name: Bug
 description: For any issue related to a bug
 title: '[Area] - Short Description'
 labels: [bug]
+projects: ["Northeastern-Electric-Racing/20"]
 body:
   - type: textarea
     id: observed-behavior
     attributes:
       label: Observed Behavior
-      description: What happened?
-    validations:
-      required: true
-  - type: textarea
-    id: expected-behavior
-    attributes:
-      label: Expected Behavior
-      description: What should have happened?
+      description: What happened? What should of happened?
     validations:
       required: true
   - type: textarea
     id: steps-to-reproduce
     attributes:
       label: Steps to Reproduce
-      description: How could someone reproduce this bug?
+      description: How could someone reproduce this bug? Include versions of code or PCBs as applicable.
       value: "1. \n2. \n3. "
     validations:
       required: true
-  - type: textarea
-    id: screenshots
-    attributes:
-      label: Screenshots (as needed)
-      description: Add screenshots of the bug if applicable
-    validations:
-      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1 +1 @@
-blank_issues_enabled: true
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/task.yml

@@ -1,19 +1,20 @@
-name: Task
-description: Create a task that a developer can complete.
+name: Feature
+description: Describe a feature that a developer can add.
 title: '[Area] - Short Description'
+projects: ["Northeastern-Electric-Racing/20"]
 body:
   - type: textarea
     id: description
     attributes:
       label: Description
-      description: Provide a brief summary of this issue
+      description: Provide a brief summary of the current shortcoming or new improvement
     validations:
       required: true
   - type: textarea
     id: acceptance-criteria
     attributes:
       label: Acceptance Criteria
-      description: What are the conditions that need to be satisified to complete this task?
+      description: What are the test conditions that need to be satisified to complete this task?
     validations:
       required: true
   - type: textarea

.github/pull_request_template.md

@@ -25,7 +25,6 @@ It can be helpful to check the `Checks` and `Files changed` tabs.
 Please reach out to your Project Lead if anything is unclear.
 Please request reviewers and ping on slack only after you've gone through this whole checklist.
 
-- [ ] All commits are tagged with the ticket number
 - [ ] No merge conflicts
 - [ ] All checks passing
 - [ ] Remove any non-applicable sections of this template

.github/workflows/build-check.yml

@@ -3,8 +3,6 @@ on: [push]
 jobs:
   run-build:
     runs-on: ubuntu-latest
-    container:
-        image: ghcr.io/northeastern-electric-racing/embedded-base:main
     timeout-minutes: 10
     steps:
       - name: Checkout code
@@ -14,7 +12,7 @@ jobs:
 
       - name: Execute Make
         run: |
-            if ! make; then
+            if ! docker compose run --rm ner-gcc-arm make -j `nproc`; then
             echo "The application has failed to build."
             exit 1  # This will cause the workflow to fail
-            fi
+            fi