Merge release 1.4.0

.devcontainer/python_development/devcontainer.json

@@ -14,5 +14,6 @@
         "ms-python.black-formatter"
       ]
     }
-  }
+  },
+  "remoteUser": "admin.ackbar"
 }

.github/ISSUE_TEMPLATE/bug-or-error-report.md

@@ -21,7 +21,7 @@ If the above did not answer your question, proceed with creating an issue below:
 A clear and concise description of what you expected to happen.
 
 ## To Reproduce
-<!-- Steps to reproduce the behavior. These should be clear enough that our team can understand your running environment, software/operating system versions and anything else we might need to debug the issue.  -->  
+<!-- Steps to reproduce the behavior. These should be clear enough that our team can understand your running environment, software/operating system versions, and anything else we might need to debug the issue.  -->  
 <!-- Good examples can be found here: [Issue 1](https://github.com/cisagov/LME/issues/15) [Issue 2](https://github.com/cisagov/LME/issues/19).  --> 
 
 ### Please complete the following information
@@ -59,12 +59,14 @@ lsb_release -a
 ```
 for name in $(sudo docker ps -a --format '{{.Names}}'); do echo -e "\n\n\n-----------$name----------"; sudo docker logs $name | tail -n 20; done
 ```
-Increase the number of lines if your issue is not present or include a relevant log of the erroring container
+Increase the number of lines if your issue is not present, or include a relevant log of the erroring container
 - Output of the relevant /var/log/cron_logs/ file
 
+## Expected behavior
+A clear and concise description of what you expected to happen.
 
-## Screenshots **OPTIONAL**
+## Screenshots
 If applicable, add screenshots to help explain your problem.
 
 ## Additional context
-Add any other context about the problem or any unique environment information here.
+Add any other context about the problem here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -10,7 +10,8 @@
 <!-- Mention any related issue(s) here using appropriate keywords such -->
 <!-- as "closes" or "resolves" to auto-close them on merge. -->
 <!-- If this PR is *not* being merged into main, the related issues will not -->
-<!-- be auto-closed, so you need to close the issue manually -->
+<!-- be auto-closed, so you need to add the issue into the Development box -->
+<!-- in the right sidebar -->
 
 ### 📷 Screenshots (DELETE IF UNAPPLICABLE)
 
@@ -25,7 +26,8 @@
 - [ ] Git Issue that this PR solves has been selected in the Development section
 - [ ] The PR's base branch has been modified to be the proper branch. 
 - [ ] Changes are limited to a single goal **AND** 
-      the title reflects this in a clear human readable format for the release notes
+      the title reflects this in a clear human readable format
+- [ ] Issue that this PR solves has been selected in the Development section
 - [ ] I have read and agree to LME's [CONTRIBUTING.md](https://github.com/cisagov/LME/CONTRIBUTING.md) document.
 - [ ] The PR adheres to LME's requirements in [RELEASES.md](https://github.com/cisagov/LME/RELEASES.md#steps-to-submit-a-PR)
 - [ ] These code changes follow [cisagov code standards](https://github.com/cisagov/development-guide).

.github/README-github.md

@@ -0,0 +1 @@
+See the readme in `testing/development` for more information about these workflows and how to develop for them. 

.github/workflows/burndown_chart.yml

@@ -0,0 +1,100 @@
+name: Burndown Chart 
+
+on: 
+  workflow_dispatch:
+    inputs:
+      start_date:
+        description: 'Sprint start date (YYYY-MM-DD)'
+        required: true
+        default: '2024-05-09'
+        type: string
+      end_date:
+        description: 'Sprint end date (YYYY-MM-DD)'
+        required: true
+        default: '2024-05-25'
+        type: string
+      view:
+        description: 'View number'
+        required: true
+        default: '1'
+        type: string
+  pull_request:
+    branches:
+      - '*'
+
+jobs:
+  create_chart:
+    runs-on: ubuntu-latest
+    env:
+      UNIQUE_ID:      
+      start_date:
+      end_date:
+      view:
+
+    steps:
+    - name: Checkout repository
+      uses: actions/[email protected]
+
+    - name: Setup environment variables
+      run: |
+        echo "UNIQUE_ID=$(openssl rand -hex 3 | head -c 6)" >> $GITHUB_ENV
+
+    - name: Set default dates
+      if: github.event_name == 'pull_request'
+      run: |
+        echo "start_date=2024-05-09" >> $GITHUB_ENV
+        echo "end_date=2024-05-25" >> $GITHUB_ENV
+        echo "view=1" >> $GITHUB_ENV
+
+    - name: Use dispatch inputs
+      if: github.event_name == 'workflow_dispatch'
+      run: |
+        echo "start_date=${{ github.event.inputs.start_date }}" >> $GITHUB_ENV
+        echo "end_date=${{ github.event.inputs.end_date }}" >> $GITHUB_ENV
+        echo "view=${{ github.event.inputs.view }}" >> $GITHUB_ENV
+
+    - name: Run Docker Build
+      run: docker compose -p ${{ env.UNIQUE_ID }} -f testing/project_management/docker-compose.yml build burndown --no-cache
+
+    - name: Run Docker Compose
+      env: 
+        BURNDOWN_TOKEN: ${{ secrets.BURNDOWN_TOKEN }}
+      run: docker compose -p ${{ env.UNIQUE_ID }} -f testing/project_management/docker-compose.yml up -d
+
+    - name: List docker containers to wait for them to start
+      run: |
+        docker ps 
+
+    - name: Set up the burndown chart config
+      env:
+        BURNDOWN_TOKEN: ${{ secrets.BURNDOWN_TOKEN }}
+        UNIQUE_ID: ${{ env.UNIQUE_ID }}
+        START_DATE: ${{ env.start_date }}
+        END_DATE: ${{ env.end_date }}
+        VIEW: ${{ env.view }}
+      run: |
+        cd testing/project_management
+        docker compose -p ${{ env.UNIQUE_ID }} exec -T burndown bash -c '
+          /lme/testing/project_management/setup_config.sh -s ${{ env.START_DATE }}  -e ${{ env.END_DATE }}  -v ${{ env.VIEW }} -f /github-projects-burndown-chart/src/github_projects_burndown_chart/config/config.json
+          sed -i "s/\"github_token\": \"\"/\"github_token\": \"$BURNDOWN_TOKEN\"/g" /github-projects-burndown-chart/src/github_projects_burndown_chart/config/secrets.json
+          cat /github-projects-burndown-chart/src/github_projects_burndown_chart/config/config.json
+        '
+
+    - name: Run the burndown chart script 
+      run: |
+        cd testing/project_management
+        docker compose -p ${{ env.UNIQUE_ID }} exec -T burndown bash -c '
+          python3 /github-projects-burndown-chart/src/github_projects_burndown_chart/main.py organization LME --filepath /lme/burndown.png
+        '
+    - name: Upload chart artifact
+      uses: actions/upload-artifact@v4
+      with:
+        name: burndown
+        path: burndown.png
+
+    - name: Cleanup Docker Compose
+      if: always()
+      run: |
+        cd testing/project_management
+        docker compose -p ${{ env.UNIQUE_ID }} down
+        # docker system prune -a --force