Challenge/palindrome checker

.github/workflows/ci-checks.yml

@@ -4,19 +4,19 @@ on: [push, pull_request, workflow_dispatch]
 
 jobs:
   ls_linting:
-      runs-on: ubuntu-latest
-      steps:  
-        - uses: actions/checkout@v4
-        - uses: ls-lint/action@v2.2.3
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: ls-lint/action@v2.2.3
 
   md_formatting:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v4
-    - uses: nosborn/github-action-markdown-cli@v3.3.0
-      with:
-        files: .
-        config_file: .markdownlint.yml
+      - uses: actions/checkout@v4
+      - uses: nosborn/github-action-markdown-cli@v3.3.0
+        with:
+          files: .
+          config_file: .markdownlint.yml
 
   py_formatting:
     runs-on: ubuntu-latest
@@ -44,11 +44,11 @@ jobs:
         if: always()
       - name: install pylint
         run: |
-          python -  m pip install --upgrade pip
+          python -m pip install --upgrade pip
           pip install pylint
         shell: bash
       - name: Python - Check Linting - pylint
-        run: "pylint solutions tests  || echo '::warning title=Pylint Error(s)::Discuss solutions and trade-offs in code review.'"
+        run: "pylint solutions tests || echo '::warning title=Pylint Error(s)::Discuss solutions and trade-offs in code review.'"
         shell: bash
 
   py_tests:
@@ -59,22 +59,13 @@ jobs:
       - 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
+        run: echo "PYTHONPATH=$GITHUB_WORKSPACE" >> $GITHUB_ENV
         shell: bash
+

.markdownlint.yml

@@ -1,3 +1,9 @@
 ignore:
   - venv
   - .github
+
+
+MD013:
+  line_length: 180
+  ignore_urls: true
+

.vscode/settings.json

@@ -119,8 +119,7 @@
     "editor.defaultFormatter": "charliermarsh.ruff",
     "editor.formatOnSave": true,
     "editor.codeActionsOnSave": {
-      "source.fixAll.ruff": "explicit",
-      "source.organizeImports.ruff": "explicit"
+
     }
   }
 }

README.md

@@ -0,0 +1,48 @@
+# Collab Coders
+
+> Welcome to the **Collab Coders** repository! 🚀  
+We are a team of passionate Junior developers From MET.
+> dedicated to building impactful solutions through collaboration and innovation.
+
+---
+
+## 🌟 About Us
+
+> At **Collab Coders**, we believe in the power of teamwork:
+
+- to tackle complex challenges and create meaningful projects.
+- This repository serves as a hub for our collaborative efforts.
+- where ideas turn into reality.
+
+---
+
+## 📂 Repository Structure
+
+Here’s how the repository is organized:
+
+- `main`: The primary branch containing stable and reviewed code.
+- `feature-branches`: Each team member has their own branch
+- for working on features or tasks.
+- Branches are named after it is functionality for clarity
+- (e.g., `challenges/factorial-function`, `challenges/sort-list`).
+
+---
+
+## 🛠️ Technologies Used
+
+> Our team use stack of tools and technologies
+> based on the program specifications and requirements:
+
+- **Languages**: Python, Markdown  
+- **Frameworks**: N/A
+- **Tools**: Github,Git, VS Code  
+- **Communication_channels**: Slack, Google Meet, Zoom, Whatsapp  
+
+---
+
+## 🌱 How to Contribute
+
+1. Clone the repository:  
+
+   ```bash
+   git clone <repository_url>

collaboration/communication.md

@@ -7,41 +7,46 @@
         you can share the rest in confidence with you group by another channel
 -->
 
-# Communication
+# Communication 📬
 
 ______________________________________________________________________
 
 ## Communication Schedule
 
-| Day | How | The topic of discussion | | --- | :-: | ----------------------- |
+| Day & Time | How | The topic of discussion |
+| --- | :-: | ----------------------- |
+|Every Friday, 9 EST| Google Meet| Activity Updates|
+| | | |
 | | | |
 
 ## Communication Channels
 
 how often will we get in touch on each channel, and what we will discuss there:
 
-- **Issues**:
-- **Pull Requests**:
-- **Slack/Discord**:
-- **Video Calls**:
+- **Issues**: To track team progress, update as needed, and assign tasks where needed
+- **Pull Requests**: Reviewed within 48 hours for feedback, approving the change and merging it to the main branch
+
+- **Slack**: For daily task updates and resolving small problems from team members
+- **Video Calls**: Zoom/Google meet preferably for general group meetings and weekly updates
 
 ______________________________________________________________________
 
 ## Availability
 
-### Availability for calling/messaging
-
-| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday | |
------- | :----: | :-----: | :-------: | :------: | :----: | :------: | :----: |
-| _name_ | | | | | | | |
-
-### How many hours everyone has per day
-
-- name: _5h_;
-- name: _6h_;
-- name: _5h_;
-- name: _4h_;
-- name: _3h_;
+### Availability for calling/messaging(+how many hours each day in EST)
+
+| Day | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | Sunday |
+|:------ | :----: | :-----: | :-------: | :------: | :----: | :------: | ----: |
+|  Hiba | 9-12     |  9-12       |    9-12    |    9-12     |   9-12    |     9-12   |   9-12   |
+| Jeffery |   9-12    |    9-12     |    9-12    |     9-12   |   9-12   |    9-12    |   9-12  |
+| Kelvin |         |          |          |            |          |          |                   |
+| Mahdia |     9-12  |     9-12   |     10-12   |    10-12    |    9-12   |   9-12   |   10-12  |
+| Martha |   9-12      |   9-12       |   9-12       |   9-12      | 9-12     | 9-12    | 9-12  |
+| Osei |   10-13      |11-15          | 9-12         |  9-12        | 9-15    |  13-15   |  9-15|
+| Rina |         |   7-15       |          |    7-15      | 7-15       |  9-15     |  9-15      |
+| Terry |    9-11     | 9-11         |  9-11        |    6-9      | 9-11       |  9-12  | 9-11  |
+| Yool |    9-12     | 9-12         | 10-13    |   8-12    |  9-12      |  10-13  | 10-13       |
+|Shagun |            |               |          |         |         |           |               |
 
 ## Asking for Help
 

collaboration/constraints.md

@@ -2,7 +2,8 @@
 
 # Constraints
 
-Some boundaries around our project.
+In any collaborative project, understanding and addressing constraints is essential for success.
+A survey was conducted within the group to know the constraint of each member of our group. Below are the internal and external constraint of the group.
 
 ## External
 
@@ -15,6 +16,13 @@ Some boundaries around our project.
   - ...
 -->
 
+- **Primary Constraint:**
+  - Technology limitations (e.g., Git, GitHub, and communication tools) were the most frequently cited
+  external constraint, affecting 75% of respondents.
+- Time zone differences and internet connectivity are also notable external constraints, each affecting 50% of respondents.
+- **Other Concerns:**
+  - Project deadlines, inconsistent power supply, and access to a personal computer were mentioned by 25% of respondents each.
+
 ## Internal: Involuntary
 
 <!--
@@ -23,12 +31,27 @@ Some boundaries around our project.
   - amount of time available to work on the project
 -->
 
-## Internal: Voluntary
+- **Primary Constraint:**
+  - The individual skill levels of group members were cited by 62.5% of respondents, making it the most significant internal constraint.
+- **Other notable constraints (each at 37.5%) include:**
+  - The amount of time available to work on the project.
+  - Individual work schedules.
+  - Inability to respond quickly to messages.
+- **Least Concern:**
+  - The number of hours members want to spend working (12.5%).
 
+## Internal: Voluntary
 <!--
   constraints that your team decided on to help scope the project. they may include:
   - coding style & conventions
   - agree on a code review checklist for the project repository
   - the number of hours you want to spend working
   - only using the colors black and white
 -->
+
+- **Primary Constraint**:
+  - Technology limitations (e.g., Git, GitHub, and communication tools) were the most frequently cited external constraint, affecting 75% of respondents.
+- **Time Zone Differences and Connectivity**:
+  - Time zone differences and internet connectivity are notable external constraints, each affecting 50% of respondents.
+- **Other Concerns**:
+  - Project deadlines, inconsistent power supply, and access to a personal computer were mentioned by 25% of respondents each.