Merge branch 'main' into challenge/sum-of-digits/4

.github/ISSUE_TEMPLATE/help_wanted.md

@@ -1,10 +1,10 @@
 ---
 name: help wanted 
-about: >
+about: > 
   A template issue for when you're blocked on certain lines of code. 
-  This template has many sections to get you thinking about your problem, you don't need to fill all of them.
+  This template has many sections to get you thinking about your problem, 
+  you don't need to fill all of them. 
 labels: "help wanted"
-
 ---
 
 <!--

.github/ISSUE_TEMPLATE/meeting_agenda.md

@@ -1,10 +1,11 @@
 ---
 name: meeting agenda 
 about: A template issue for planning meetings 
-title: "Agenda: __" 
+title: "Agenda: \_\_" 
 labels: agenda
 ---
 
+
 <!-- Make your issue easy to find:
 
   - milestone: any milestones you will be addressing

.github/ISSUE_TEMPLATE/new_challenge.md

@@ -1,9 +1,8 @@
 ---
 name: new challenge 
-about: >
-  A template issue for describing a new challenge on the project board.
+about: > 
+  A template issue for describing a new challenge on the project board. 
   Place this issue in the TODO column of your group's project board. 
-title: ''
 ---
 
 <!--

.github/ISSUE_TEMPLATE/question.md

@@ -1,6 +1,6 @@
 ---
 name: question 
-about: >
+about: > 
   A template issue for topics you'd like to discuss or learn more about. 
   specific topics, general knowledge, it does not even need to be about code. 
   There are no bad questions! 

.github/workflows/ci-checks.yml

@@ -55,9 +55,26 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
+
       - name: python version
         run: python --version
         shell: bash
+
+      - name: Check for test files
+        id: check_tests
+        run: |
+          test_files=$(find ./solutions/tests -type f -name "test_*.py")
+          if [ -n "$test_files" ]; then
+            echo "Found test files:"
+            echo "$test_files"
+            echo "has_tests=true" >> $GITHUB_OUTPUT
+          else
+            echo "No test files found matching pattern ./solutions/tests/test_*.py"
+            echo "has_tests=false" >> $GITHUB_OUTPUT
+          fi
+        shell: bash
+
       - name: Python - Run Tests
+        if: steps.check_tests.outputs.has_tests == 'true'
         run: python -m unittest
         shell: bash

.vscode/settings.json

@@ -114,7 +114,12 @@
 
   // Enable/disable update table of contents on save
   "markdown.extension.toc.updateOnSave": false,
-  "cSpell.words": [
-    "Noorelsalam"
-  ]
+  "[python]": {
+    "editor.defaultFormatter": "charliermarsh.ruff",
+    "editor.formatOnSave": true,
+    "editor.codeActionsOnSave": {
+      "source.fixAll.ruff": true,
+      "source.organizeImports.ruff": true
+    }
+  }
 }

collaboration/group_norms.md

@@ -0,0 +1,68 @@
+# Group Norms
+
+<!-- group norms summary -->
+
+<!-- group norms list -->
+
+1. **Active Listening**
+
+   - We will listen carefully to each person without preparing a response in advance.
+   - We will not interrupt anyone who is speaking.
+
+2. **Respectful Communication**
+
+   - We will speak respectfully and use collaborative language, even when we disagree.
+   - We will focus on critiquing ideas rather than criticizing individuals, sharing
+   both agreements and disagreements to broaden our team’s knowledge and perspective.
+
+3. **Supportive Environment**
+
+   - We will foster an atmosphere where personal challenges that affect
+   attendance can be openly shared.
+   - We will work together to find individual solutions.
+   If someone has difficulty understanding an assignment:
+     - They are encouraged to consult the materials
+   shared by Evan and search online for up to one hour.
+     - If the issue remains unresolved, they should reach out to the team for help.
+
+4. **Timely Communication**
+
+   - We commit to responding to messages, emails,
+   and inquiries without unnecessary delay, generally within 24 hours.
+   - Our main communication channels will be Slack and WhatsApp.
+
+5. **Reintegration After Absences**
+
+   - If someone misses a group meeting or task, we
+   will offer helpful suggestions and
+   support to facilitate their reintegration.
+   - The individual is expected to catch up on missed
+   tasks to ensure the team’s progress does not stall.
+
+6. **Positive Support**
+
+   - We will remain positive and offer
+   encouragement, especially during challenging moments.
+   - We will honor our commitments by arriving on
+   time for meetings and meeting agreed-upon deadlines.
+
+7. **Appreciation**
+
+   - We will express appreciation for each other’s efforts recognizing that every
+   contribution, no matter how small, helps our team succeed.
+
+8. **Documentation and Accountability**
+
+   - We will record all group decisions, agreements, and established norms to
+   maintain clarity and ensure alignment.
+   - We will record our meetings whenever possible.
+   - Within 24 hours of each meeting, a summary of
+   key discussions and decisions will be posted in
+   a shared communication channel (e.g., Slack or WhatsApp).
+   - Anyone who misses a meeting is encouraged to review
+   these materials and ask questions for clarification.
+
+9. **Engaged Participation**
+
+   - We commit to being physically present, listening attentively, contributing
+   ideas, and staying focused on our shared objectives.

collaboration/guide/0_repository_setup.md

@@ -6,16 +6,14 @@ take the time to do this correctly at the beginning.
 
 ## Setup and Share a Repository
 
-As a team you will choose the name for your team and select
-someone from your team to be the repo owner. This person will fork this
-repository and configure it for collaboration:
+As a team you will choose the name for your team and select someone from your
+team to be the repo owner. This person will fork this repository and configure
+it for collaboration:
 
 - Public face of your repository
   - Change your
     [repository description](https://stackoverflow.com/questions/7757751/how-do-you-change-a-repository-description-on-github)
   - Add or remove topics from your repository
-  - Update your main README with your group name and an initial overview of
-    your project. (You can change this as much as you want.)
 - Under settings in your repository select:
   - _Issues_
   - _Projects_

solutions/__init__.py

@@ -0,0 +1 @@
+

solutions/tests/__init__.py

@@ -0,0 +1 @@
+