Sync dev and main

.github/ISSUE_TEMPLATE/blank_issue.yml

@@ -0,0 +1,17 @@
+name: Blank issue
+description: Create a new issue from scratch
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thank you for contributing an issue to our project!
+  - type: markdown
+    attributes:
+      value: |
+        If you are reporting a bug or requesting a feature, please click "Choose a different template" above.
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,31 +1,77 @@
-name: SOE Tech Doc - Bug Report
-description: Use this issue template to report bugs in the State of the Ecosystem technical documentation.
-title: "[Bug Report]: "
+name: Bug Report
+description: Identify a problem or unexpected outcome
+title: "[Bug]: "
 labels: ["bug"]
-assignees: "BBeltz1"
 body:
-  - type: markdown
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Bug description
+      description: Please explain the problem you are experiencing
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: Version
+      description: What version of our product are you using?
+      placeholder: X.X.X
+    validations:
+      required: true
+  - type: dropdown
+    id: operating-system
     attributes:
+      label: Operating system
+      description: What operating system are you using?
+      options:
+        - Windows
+        - Mac
+        - Linux
+    validations:
+      required: true
+  - type: textarea
+    id: system-info
+    attributes:
+      label: System information
+      description: Please provide the following system information
       value: |
-        Please use the fields below to identify the bug and provide related information we can use to troubleshoot. Thanks.
+        - R version: 
+        - IDE: 
+        - IDE version: 
+    validations:
+      required: true
   - type: textarea
-    id: bugdesc
+    id: reproduction-steps
     attributes:
-      label: Describe the bug
-      description: A clear and concise description of what the bug is.
+      label: Reproduction steps
+      description: Please explain the steps required to reproduce the problem. Ideally, include a minimal reproducible example (AKA a reprex). If you've never heard of a [reprex](http://reprex.tidyverse.org/) before, start by reading <https://www.tidyverse.org/help/#reprex>.
     validations:
       required: true
   - type: textarea
-    id: bugdisc
+    id: actual-result
     attributes:
-      label: Describe the situation
-      description: How did you discover this bug? What were you trying to accomplish?
+      label: Actual result
+      description: What is the observed outcome of following the steps above?
     validations:
       required: true
   - type: textarea
-    id: addinfo
+    id: expected-result
+    attributes:
+      label: Expected result
+      description: What outcome did you expect from following the steps above?
+    validations:
+      required: true
+  - type: input
+    id: bug-impact
+    attributes:
+      label: Bug impact
+      description: How severely does this problem impact you and/or your work?
+    validations:
+      required: true
+  - type: upload
+    id: screenshots
     attributes:
-      label: Additional information
-      description: Add any other information about the problem here.
+      label: Upload screenshots
+      description: If applicable, you may upload screenshots to demonstrate the problem.
     validations:
       required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1 @@
+blank_issues_enabled: false

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,33 @@
+name: Feature Request
+description: Request the addition of a new feature
+title: "[Feature]: "
+labels: ["feature"]
+body:
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Feature description
+      description: Please explain the feature you are requesting
+    validations:
+      required: true
+  - type: textarea
+    id: feature-reason
+    attributes:
+      label: Justification
+      description: How would this feature improve your use of our product?
+    validations:
+      required: true 
+  - type: textarea
+    id: example-features
+    attributes:
+      label: Examples
+      description: If applicable, please provide an example of the feature. If you have seen or used an analagous feature elsewhere, please provide a link to it.
+    validations:
+      required: false
+  - type: upload
+    id: screenshots
+    attributes:
+      label: Upload screenshots
+      description: If applicable, you may upload screenshots to supplement your request.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/page_edit.yml

@@ -2,7 +2,6 @@ name: State of the Ecosystem - Edit Tech Doc Page
 description: Use this issue template to suggest an edit to a page in the State of the Ecosystem technical documentation.
 title: "[Tech Doc Page Edit]: "
 labels: ["page edit"]
-assignees: "BBeltz1"
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/techdoc_submission.yml

@@ -2,7 +2,6 @@ name: State of the Ecosystem - Tech Doc Submission
 description: Use this issue template to submit tech doc information for the State of the Ecosystem reports.
 title: "[Submission]: "
 labels: ["submission"]
-assignees: "BBeltz1"
 body:
   - type: markdown
     attributes:

.github/PULL_REQUEST_TEMPLATE/dev_pr.md

@@ -0,0 +1,25 @@
+PRs into `dev` contained all necessary info. They have already been approved.
+Please provide the information below so `main` can be synced with `dev`:
+
+### List PRs
+
+List the PRs that were merged into `dev` that will be pulled into `main` and any issues they fix:
+
+* PR #? which fixes #?
+
+### Types of changes
+
+What types of changes does this pull request introduce? Put an `x` in the boxes that apply.
+This will inform the new release number.
+
+- [ ] Fix (non-breaking change which fixes a bug)
+- [ ] Feature (non-breaking change which adds or changes functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Other change (if none of the other choices apply)
+
+### Reviewer instructions
+
+The underlying PRs should have been reviewed. Please check that the proposed merge is correct before approving.
+If any checkboxes other than "Other change" have been selected please prepare the following file changes for a new release version:
+- [ ] changelog.Rmd - add release notes
+- [ ] DESCRIPTION - increment the version number according to [Semantic Versioning](https://semver.org)

.github/pull_request_template.md

@@ -0,0 +1,36 @@
+Your commits explain the `who`, `what`, `where` and `when` of these changes. Your code shows the `how`. You do not need to reiterate this. This PR should complete the picture by explaining `why` these changes are necessary.
+Please complete the fields below, replacing or removing placeholder text where necessary:
+
+### Justification
+
+Please describe the importance/impact of the problem and a description of how the changes in this pull request will address, resolve or improve it. This section should sufficiently explain to reviewers why these changes should be approved.
+If the proposed changes should close an issue, be sure to link to it below:  
+Fixes #?
+
+### Types of changes
+
+What types of changes does this pull request introduce? Put an `x` in the boxes that apply.
+This will inform the new release number.
+
+- [ ] Fix (non-breaking change which fixes a bug)
+- [ ] Feature (non-breaking change which adds or changes functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] Other change (if none of the other choices apply)
+
+### Further comments
+
+If this is a relatively large or complex change, kick off a discussion by explaining why you chose the solution you did, what alternatives you considered, problems you may have encountered, etc.
+
+### Reviewer instructions
+
+Assign at least 2 reviewers: 
+* one of which should be a maintainer of this repo, 
+* the others should be familiar with the subject or problem.
+
+Please detail the process reviewers will need to follow to properly test these changes. It is especially helpful to identify the exact code needed to conduct a local build/review/test and to specify any aspects of the testing that may not be obvious.
+
+### Formatting
+
+This repo contains an `air.toml` file that automatically formats code to a set of standards.
+It is preferred that contributors and reviewers install the [Air](https://posit-dev.github.io/air/) formatting tool.
+Code submitted in this pull request will be automatically checked for correct formatting.

.github/workflows/bookdown.yaml

@@ -3,13 +3,8 @@
 on:
   push:
     branches:
-      - master
-      - dev
-
-  pull_request:
-    branches:
-      - master
-
+      - main
+  workflow_dispatch:
 
 name: build-book
 
@@ -22,7 +17,7 @@ jobs:
       GITHUB_PAT: ${{ secrets.GITHUB_TOKEN }}
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v6
 
       - uses: r-lib/actions/setup-pandoc@v2
 
@@ -33,10 +28,10 @@ jobs:
       - uses: r-lib/actions/setup-r-dependencies@v2
 
       - name: Build book
-        run: Rscript -e 'bookdown::render_book("index.Rmd", quiet = TRUE)'
+        run: Rscript -e 'bookdown::render_book("index.Rmd", quiet = FALSE)'
 
       - name: Deploy to gh-pages
-        uses: JamesIves/github-pages-deploy-action@v4
+        uses: JamesIves/github-pages-deploy-action@v4.8.0
         with:
           GITHUB_TOKEN: ${{ secrets.ACCESS_TOKEN }}
           BRANCH: gh-pages # The branch the action should deploy to.

.github/workflows/format-check.yml

@@ -0,0 +1,24 @@
+# Workflow derived from https://github.com/posit-dev/setup-air/tree/main/examples
+
+on:
+  push:
+    branches: [main, dev]
+  pull_request:
+  workflow_dispatch:
+
+name: format-check.yaml
+
+permissions: read-all
+
+jobs:
+  format-check:
+    name: format-check
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install
+        uses: posit-dev/setup-air@v1
+
+      - name: Check
+        run: air format . --check

.github/workflows/format-suggest.yml

@@ -0,0 +1,31 @@
+# Workflow derived from https://github.com/posit-dev/setup-air/tree/main/examples
+
+on:
+  pull_request:
+
+name: format-suggest.yaml
+
+jobs:
+  format-suggest:
+    name: format-suggest
+    runs-on: ubuntu-latest
+
+    permissions:
+      # Required to push suggestion comments to the PR
+      pull-requests: write
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install
+        uses: posit-dev/setup-air@v1
+
+      - name: Format
+        run: air format .
+
+      - name: Suggest
+        uses: reviewdog/action-suggester@v1
+        with:
+          level: error
+          fail_level: error
+          tool_name: air

.github/workflows/secretScan.yml

@@ -6,7 +6,7 @@ jobs:
   gitleaks:
     runs-on: ubuntu-latest
     steps:
-    - uses: actions/checkout@v2
+    - uses: actions/checkout@v6
       with:
         fetch-depth: '2'
     - name: gitleaks-action

.github/workflows/verify_pr.yml

@@ -2,7 +2,7 @@ name: Run PR Checks
 on:
   pull_request:
     branches:
-    - master
+    - main
 
 jobs:
   check_description:
@@ -13,3 +13,8 @@ jobs:
       uses: takanuva15/verify-file-updated@v1
       with:
         filename_to_check: DESCRIPTION
+
+    - name: Verify Changelog Updated
+      uses: takanuva15/verify-file-updated@v1
+      with:
+        filename_to_check: chapters/changelog.Rmd