microsoft
diff --git a/‎.github/ISSUE_TEMPLATE/bug_report.md
+45 b/‎.github/ISSUE_TEMPLATE/bug_report.md
+45
diff --git a/‎.github/ISSUE_TEMPLATE/feature_request.md
+32 b/‎.github/ISSUE_TEMPLATE/feature_request.md
+32
diff --git a/‎.github/ISSUE_TEMPLATE/subtask.md
+22 b/‎.github/ISSUE_TEMPLATE/subtask.md
+22
diff --git a/‎.github/PULL_REQUEST_TEMPLATE.md
+37 b/‎.github/PULL_REQUEST_TEMPLATE.md
+37
diff --git a/‎.github/workflows/pr-title-checker.yml
+22 b/‎.github/workflows/pr-title-checker.yml
+22
diff --git a/‎.github/workflows/pylint.yml
+5-2 b/‎.github/workflows/pylint.yml
+5-2
diff --git a/‎.github/workflows/stale-bot.yml
+19 b/‎.github/workflows/stale-bot.yml
+19
diff --git a/‎ClientAdvisor/App/.flake8
+3-2 b/‎ClientAdvisor/App/.flake8
+3-2
diff --git a/‎ClientAdvisor/App/frontend/__mocks__/react-markdown.tsx
+5 b/‎ClientAdvisor/App/frontend/__mocks__/react-markdown.tsx
+5
@@ -0,0 +1,45 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+# Describe the bug
+A clear and concise description of what the bug is.
+
+# Expected behavior
+A clear and concise description of what you expected to happen.
+
+# How does this bug make you feel?
+_Share a gif from [giphy](https://giphy.com/) to tells us how you'd feel_
+
+---
+
+# Debugging information
+
+## Steps to reproduce
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Screenshots
+If applicable, add screenshots to help explain your problem.
+
+## Logs
+
+If applicable, add logs to help the engineer debug the problem.
+
+---
+
+# Tasks
+
+_To be filled in by the engineer picking up the issue_
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] ...
@@ -0,0 +1,32 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+# Motivation
+
+A clear and concise description of why this feature would be useful and the value it would bring.
+Explain any alternatives considered and why they are not sufficient.
+
+# How would you feel if this feature request was implemented?
+
+_Share a gif from [giphy](https://giphy.com/) to tells us how you'd feel. Format: ![alt_text](https://media.giphy.com/media/xxx/giphy.gif)_
+
+# Requirements
+
+A list of requirements to consider this feature delivered
+- Requirement 1
+- Requirement 2
+- ...
+
+# Tasks
+
+_To be filled in by the engineer picking up the issue_
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] ...
@@ -0,0 +1,22 @@
+---
+name: Sub task
+about: A sub task
+title: ''
+labels: subtask
+assignees: ''
+
+---
+
+Required by <link to parent issue>
+
+# Description
+
+A clear and concise description of what this subtask is.
+
+# Tasks
+
+_To be filled in by the engineer picking up the subtask
+
+- [ ] Task 1
+- [ ] Task 2
+- [ ] ...
@@ -0,0 +1,37 @@
+## Purpose
+<!-- Describe the intention of the changes being proposed. What problem does it solve or functionality does it add? -->
+* ...
+
+## Does this introduce a breaking change?
+<!-- Mark one with an "x". -->
+
+- [ ] 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.
+-->
+
+## Golden Path Validation
+- [ ] I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.
+
+## 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
+* ...
+
+## Other Information
+<!-- Add any other helpful information that may be needed here.. -->
@@ -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 }}
@@ -18,5 +18,8 @@ jobs:
       run: |
         python -m pip install --upgrade pip
         pip install -r ClientAdvisor/App/requirements.txt
-    - name: Run flake8
-      run: flake8 --config=ClientAdvisor/App/.flake8 ClientAdvisor/App
+        pip install -r ResearchAssistant/App/requirements.txt
+    - name: Run flake8 and pylint
+      run: |
+        flake8 --config=ClientAdvisor/App/.flake8 ClientAdvisor/App
+        flake8 --config=ResearchAssistant/App/.flake8 ResearchAssistant/App
@@ -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
@@ -1,4 +1,5 @@
 [flake8]
 max-line-length = 88
-extend-ignore = E501, E203
-exclude = .venv, frontend,
+extend-ignore = E501
+exclude = .venv, frontend
+ignore = E203, W503, G004, G200
@@ -9,6 +9,11 @@ const mockNode = {
 const mockProps = { className: 'language-javascript' };
 
 const ReactMarkdown: React.FC<{ children: React.ReactNode , components: any }> = ({ children,components }) => {
+  if(!components.code){
+    components.code = ({ ...codeProps }) => {
+      return <div>Test Code text from markdown </div>
+    }
+  }
   return <div data-testid="reactMockDown">
     {components && components.code({ node: mockNode, ...mockProps })}
     {children}</div>; // Simply render the children