Add GitHub issue templates for bug reports, feature requests, and doc changes

Author: ayushman1210

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# All files in the repository must be reviewed by one of these users
+*   @Alomir @dlebauer @mdietze @mswilburn

.github/ISSUE_TEMPLATE/Bug_report.md

@@ -0,0 +1,35 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+### Bug Description
+
+A clear and concise description of what the bug is.
+
+In the format "When I do X, I expect Y but observe Z"
+
+### To Reproduce
+
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+## Expected behavior
+
+A clear and concise description of what you expected to happen.
+
+## Screenshots
+
+If applicable, add screenshots to help explain your problem.
+
+## SIPNET Version
+
+ - Version or Git SHA [e.g. 2.1.0 or abc1234]
+
+## Additional context
+
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/Doc_changes.md

@@ -0,0 +1,18 @@
+---
+name: Documentation Changes
+about: Create a report to help us improve
+
+---
+
+### Document Change needed
+
+A clear description of what changes are needed with the location of the error, or that needs to be fixed.
+
+Example: 
+There is a broken URL link in the documentation. It is in the parameters documentation. The underlying file is `docs/parameters.md`. The correct link should be https://aws.amazon.com/.
+
+### Information for those wanting to make changes
+
+Please refer to the documentation guidelines in `CONTRIBUTING.md` to learn how to make changes to the documentation.
+
+All markdown files related to documentation are located within the main directory `docs/`.

.github/ISSUE_TEMPLATE/Feature_request.md

@@ -0,0 +1,24 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+## Description
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+## Use Cases and Requirements
+
+**Describe the use cases and requirements**
+Please focus on describing the problem and your requirements without going into the solution space. We believe in understanding requirements before design, and design before solution!
+
+## Alternatives Considered (Optional)
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative workflows or workarounds you are currently using.
+
+## Additional Context 
+
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,39 @@
+<!-- Please fill out the sections below to help reviewers. -->
+
+## Summary
+
+- **What**: Short description of the functional or documentation changes
+- **Motivation**: Why is this change needed?
+
+## How was this change tested?
+List steps taken to test this change, with appropriate outputs if applicable
+
+If changes are needed for any `sipnet.out` files in the `test/smoke` subdirectories, then include output from
+`tools/smoke_check.py` by running the commands below and pasting the output at the end of this PR. Note that 
+this must be run BEFORE submitting changes to any `sipnet.out` files.
+```bash
+make smoke
+python tools/smoke_check.py run verbose <list tests/smoke subdirectories with changed outputs>
+```
+Run `python tools/smoke_check.py help` for more info.
+
+## Reproduction steps
+
+If appropriate, list steps to reproduce the change locally
+
+## Related issues
+
+- Fixes #<issue>
+
+## Checklist
+
+- [ ] Related issues are listed above. [PRs without an approved, related issue may not get reviewed](docs/CONTRIBUTING.md#propose-and-receive-feedback).
+- [ ] PR title has the issue number in it ("[#<number>] \<concise description of proposed change>")
+- [ ] Tests added/updated for new features (if applicable)
+- [ ] Documentation updated (if applicable)
+- [ ] `docs/CHANGELOG.md` updated with noteworthy changes
+- [ ] Code formatted with `clang-format` (run `git clang-format` if needed)
+
+---
+
+**Note**: See [CONTRIBUTING.md](../docs/CONTRIBUTING.md) for additional guidance. This repository uses automated formatting checks; if the pre-commit hook blocks your commit, run `git clang-format` to format staged changes.

.github/workflows/ci.yml

@@ -7,6 +7,7 @@ on:
   pull_request:
 
 jobs:
+
   # Build and Integration Test
   build:
     strategy:

.github/workflows/cpp-linter.yaml

@@ -26,5 +26,5 @@ jobs:
       - name: analysis
         if: steps.linter.outputs.checks-failed > 0
         run: |
-            echo "${{ steps.linter.outputs.checks-failed }} linter checks failed" |
-
+            echo "${{ steps.linter.outputs.checks-failed }} linter checks failed"
+            exit 1

.github/workflows/debug.yml

@@ -0,0 +1,24 @@
+name: Setup Linux Debug Session
+
+on:
+  workflow_dispatch:
+    inputs:
+      debug_enabled:
+        type: boolean
+        description: 'Run the build with tmate debugging enabled (https://github.com/marketplace/actions/debugging-with-tmate)'
+        required: false
+        default: false
+
+jobs:
+  # Debug environment
+  debug:
+    runs-on: ubuntu-latest
+    environment: debug
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install gdb
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.debug_enabled }}
+        run: sudo apt install gdb
+      - name: Setup tmate session
+        if: ${{ github.event_name == 'workflow_dispatch' && inputs.debug_enabled }}
+        uses: mxschmitt/action-tmate@v3

.github/workflows/docs-build.yml

@@ -0,0 +1,42 @@
+name: Build and Upload Docs
+
+on:
+  push:
+    branches: [ master ]
+  pull_request:
+    branches: [ master ]
+    types: [opened, synchronize, reopened, closed]
+
+permissions:
+  contents: read      # needed for checkout
+  pages: write        # to deploy to GitHub Pages
+  id-token: write     # to authenticate with GitHub Pages
+
+concurrency:
+  group: "pages"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    name: docs-build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install system deps
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y doxygen graphviz
+          python3 -m pip install --upgrade pip
+          python3 -m pip install mkdocs mkdocs-material pymdown-extensions
+
+      - name: Build docs (MkDocs + Doxygen)
+        run: |
+          make clean document
+          touch site/.nojekyll
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site

.github/workflows/docs-publish.yml

@@ -0,0 +1,54 @@
+name: Publish Docs
+
+on:
+  push:
+    branches: [ master ]
+
+permissions:
+  contents: read
+  pages: write
+  id-token: write
+
+concurrency:
+  group: "pages-prod"
+  cancel-in-progress: true
+
+jobs:
+  build:
+    name: docs-build
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Install system deps
+        run: |
+          sudo apt-get update
+          sudo apt-get install -y doxygen graphviz
+          python3 -m pip install --upgrade pip
+          python3 -m pip install mkdocs mkdocs-material pymdown-extensions
+
+      - name: Build docs (MkDocs + Doxygen)
+        run: |
+          make clean document
+          touch site/.nojekyll
+
+      - name: Upload Pages artifact
+        uses: actions/upload-pages-artifact@v3
+        with:
+          path: site
+
+  deploy:
+    name: deploy-pages
+    needs: build
+    environment:
+      name: github-pages
+      url: ${{ steps.deployment.outputs.page_url }}
+    runs-on: ubuntu-latest
+    permissions:
+      pages: write
+      id-token: write
+    steps:
+      - name: Deploy to GitHub Pages
+        id: deployment
+        uses: actions/deploy-pages@v4