pulling in changes from the master branch

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,33 @@
+---
+name: Bug Report
+about: Report an error or unexpected behavior.
+title: ""
+labels: bug
+assignees: ""
+---
+
+### Bug Description
+
+<!-- Please briefly describe your problem. -->
+
+### Steps to Reproduce
+
+<!-- Please describe the steps to reproduce the bug. -->
+
+1.
+2.
+3.
+
+<!-- 
+Alternatively, Please include a minimal reproducible example (AKA a reprex). If
+you've never heard of a reprex before, start by reading stackoverflow's help
+page: <https://stackoverflow.com/help/minimal-reproducible-example>.
+-->
+
+```shell
+# insert reprex here
+```
+
+### Expected Behavior
+
+<!-- Please detail what output you expect. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,5 @@
+blank_issues_enabled: true
+contact_links:
+  - name: 💬 MIPTools Google Group
+    url: https://groups.google.com/g/miptools
+    about: Please ask and answer questions here.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,35 @@
+---
+name: Feature Request
+about: Suggest an idea or feature.
+title: ""
+labels: "feature :sparkles:"
+assignees: ""
+---
+
+### Related Problem
+
+<!--
+**Is your feature request related to a problem?**
+If so, please briefly describe the problem.
+
+Please consider including a minimal reproducible example (AKA a reprex). If
+you've never heard of a reprex before, start by reading stackoverflow's help
+page: <https://stackoverflow.com/help/minimal-reproducible-example>.
+
+```shell
+# insert reprex here
+```
+-->
+
+### Solution Requested
+
+<!--
+**Describe the solution you'd like**
+Provide a description of what you want to happen.
+-->
+
+<!--
+**Describe alternatives you've considered**
+Provide a description of any alternative solutions or features you've
+considered.
+-->

.github/ISSUE_TEMPLATE/maintenance.md

@@ -0,0 +1,18 @@
+---
+name: Maintenance
+about: Request code maintenance, clarity improvements, styling fixes, etc.
+title: ""
+labels: "maintenance :hammer_and_wrench:"
+assignees: ""
+---
+
+### Maintenance Request
+
+<!-- Describe the type of maintenance requested. -->
+
+#### Code Example
+
+<!--
+Please include an example of where the change would be made.
+Consider including line numbers from a specific file.
+-->

.github/workflows/build-container.sh

@@ -0,0 +1,7 @@
+#!/bin/bash
+
+# Build container
+sudo singularity build --force miptools_dev.sif MIPTools.def
+
+# Upload to website
+mv -f miptools_dev.sif /work/bailey_share/software/MIPTools/download/

.github/workflows/notify-maintainers.yaml

@@ -1,7 +1,7 @@
 name: Notify Maintainers
 on:
-  schedule:
-    - cron: 0 12 1,15 * *
+  # schedule:
+  #   - cron: 0 12 1 * *
 
   workflow_dispatch:
 

.github/workflows/notify-message.md

@@ -1,15 +1,9 @@
-Please build the container and deploy it to the Sylabs Cloud. It has been two weeks since the last reminder.
+Please build the container and upload the container to the website. It has been one month since the last reminder.
 
-Steps to build:
+Build and deploy:
 
 ```bash
-sudo singularity build miptools.sif MIPTools.def
-```
-
-Steps to deploy:
-
-```bash
-singularity remote login
-singularity sign miptools.sif
-singularity push miptools.sif library://apascha1/miptools/miptools:{tag}
+gh repo clone bailey-lab/MIPTools
+cd MIPTools
+.github/workflows/build-container.sh
 ```