Merge remote-tracking branch 'upstream/main'

Author: Roopan-Microsoft

.flake8

@@ -1,13 +1,4 @@
 [flake8]
 max-line-length = 120
-exclude = .venv, _pycache_, migrations, build, dist
-ignore =
-    F401
-    F841
-    W293
-    E501
-    E722
-    W503
-    F811
-    E266
-    F541
+exclude = .venv, _pycache_, migrations
+ignore = E501,F401,F811,F841,E203,E231,W503

.github/CODEOWNERS

@@ -2,5 +2,4 @@
 # Each line is a file pattern followed by one or more owners.
 
 # These owners will be the default owners for everything in the repo.
-* @Avijit-Microsoft @Roopan-Microsoft @Prajwal-Microsoft
-
+* @toherman-msft @hunterjam @Avijit-Microsoft @Roopan-Microsoft @Prajwal-Microsoft

.github/dependabot.yml

@@ -5,7 +5,20 @@
 
 version: 2
 updates:
-  - package-ecosystem: "pip" # See documentation for possible values
-    directory: "/" # Location of package manifests
+  - package-ecosystem: "npm" # for frontend dependencies
+    directory: "/frontend"  
     schedule:
-      interval: "weekly"
+      interval: "monthly"
+    commit-message:
+      prefix: "build"
+    target-branch: "dependabotchanges"
+    open-pull-requests-limit: 10
+
+  - package-ecosystem: "pip" # for backend dependencies
+    directory: "/"   
+    schedule:
+      interval: "monthly"
+    commit-message:
+      prefix: "build"
+    target-branch: "dependabotchanges"
+    open-pull-requests-limit: 10

.github/pull_request_template.md

@@ -1,25 +1,40 @@
-### Motivation and Context
-
-<!-- Thank you for your contribution to this repo!
-Please help reviewers and future users, providing the following information:
-  1. Why is this change required? 
-  2. What problem does it solve?
-  3. What scenario does it contribute to?
-  4. If it fixes an open issue, please link to the issue here.
-  5. Does this solve an issue or add a feature that *all* users of this sample app can benefit from? Contributions will only be accepted that apply across all users of this app.
--->
+## Purpose
+<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? -->
+* ...
 
-### Description
+## Does this introduce a breaking change?
+<!-- Mark one with an "x". -->
 
-<!-- Describe your changes, the overall approach, the underlying design.
-     These notes will help understanding how your code works. Thanks! -->
+- [ ] Yes
+- [ ] No
 
+<!-- Please prefix your PR title with one of the following:
+  * `feat`: A new feature
+  * `fix`: A bug fix
+  * `docs`: Documentation only changes
+  * `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
+  * `refactor`: A code change that neither fixes a bug nor adds a feature
+  * `perf`: A code change that improves performance
+  * `test`: Adding missing tests or correcting existing tests
+  * `build`: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
+  * `ci`: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
+  * `chore`: Other changes that don't modify src or test files
+  * `revert`: Reverts a previous commit
+  * !: A breaking change is indicated with a `!` after the listed prefixes above, e.g. `feat!`, `fix!`, `refactor!`, etc.
+-->
 
-### Contribution Checklist
+## Golden Path Validation
+- [ ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.
 
-<!-- Before submitting this PR, please make sure: -->
+## Deployment Validation
+- [ ] I have validated the deployment process successfully and all services are running as expected with this change.
 
+## What to Check
+Verify that the following are valid
 - [ ] I have built and tested the code locally and in a deployed app
 - [ ] For frontend changes, I have pulled the latest code from main, built the frontend, and committed all static files.
 - [ ] This is a change for all users of this app. No code or asset is specific to my use case or my organization.
-- [ ] I didn't break any existing functionality :smile:
+
+
+## Other Information
+<!-- Add any other helpful information that may be needed here.. -->

.github/workflows/pr-title-checker.yml

@@ -0,0 +1,22 @@
+name: "pr-title-checker"
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+  merge_group:
+
+permissions:
+  pull-requests: read
+
+jobs:
+  main:
+    name: Validate PR title
+    runs-on: ubuntu-latest
+    if: ${{ github.event_name != 'merge_group' }}
+    steps:
+      - uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/pylint.yml

@@ -30,6 +30,6 @@ jobs:
           echo "Formatting code with Black..."
           python -m black --verbose .
           echo "Running Flake8..."
-          python -m flake8 --config=.flake8 --verbose . || true
+          python -m flake8 --config=.flake8 --verbose .
           echo "Running Pylint..."
-          python -m pylint --rcfile=.pylintrc --verbose . || true
+          python -m pylint --rcfile=.pylintrc --verbose .

.github/workflows/stale-bot.yml

@@ -0,0 +1,19 @@
+name: 'Close stale issues and PRs'
+on:
+  schedule:
+    - cron: '30 1 * * *'
+
+permissions:
+  contents: write
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          stale-issue-message: 'This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.'
+          days-before-stale: 180
+          days-before-close: 30

.github/workflows/sync-branches.yml

@@ -0,0 +1,44 @@
+name: Sync Main to dependabotchanges
+
+on:
+  # Schedule the sync job to run daily or customize as needed
+  schedule:
+    - cron: '0 1 * * *'  # Runs every day at 1 AM UTC
+  # Trigger the sync job on pushes to the main branch
+  push:
+    branches:
+      - main
+
+jobs:
+  sync:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v3
+        with:
+          fetch-depth: 0  # Fetch all history for accurate branch comparison
+
+      - name: Configure Git
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Sync main to dependabotchanges
+        run: |
+          # Ensure we're on the main branch
+          git checkout main
+          # Fetch the latest changes
+          git pull origin main
+
+          # Switch to dependabotchanges branch
+          git checkout dependabotchanges
+          # Merge main branch changes
+          git merge main --no-edit
+
+          # Push changes back to dependabotchanges1 branch
+          git push origin dependabotchanges
+
+      - name: Notify on Failure
+        if: failure()
+        run: echo "Sync from main to dependabotchanges failed!"

.pylintrc

@@ -1,34 +1,24 @@
 [MASTER]
-ignore=__init__.py,__pycache__
-
+ignore=__pycache__, migrations, .venv
 
 [MESSAGES CONTROL]
-# Retain your disabled warnings and errors
-disable=
-    missing-docstring,  # Missing docstrings
-    invalid-name,  # Variable names not in snake_case
-    too-many-arguments,  # Exceeding argument limits
-    too-many-locals,  # Exceeding local variable limits
-    too-many-branches,  # Complex functions
-    too-many-lines,  # Exceeding file line limit
-    import-error,  # Ignored unresolved imports
-    no-name-in-module,  # Missing module names
-    broad-exception-raised,  # Avoid broad exceptions
-    redefined-outer-name,  # Outer variable shadowing
-    no-else-return,  # Remove unnecessary else
-    unused-import,  # Unused imports
+
+disable=parse-error,missing-docstring,too-many-arguments,line-too-long
 
 [FORMAT]
-# Set the maximum line length
+
 max-line-length=120
 
 [DESIGN]
-# Adjust thresholds for warnings
+
 max-args=10
-max-locals=30
-max-branches=20
-max-statements=100
+max-locals=25
+max-branches=15
+max-statements=75
+
+[REPORTS]
+output-format=colorized
+reports=no
 
-[LOGGING]
-# Disable logging format errors
-logging-format-style=old
+[EXCEPTIONS]
+overgeneral-exceptions=builtins.Exception,builtins.BaseException