Merge branch 'main' into feat/multiple-categories-selection

Author: mcanouil

.git-blame-ignore-revs

@@ -0,0 +1,8 @@
+# This file lists revisions of large-scale formatting/style changes so that
+# they can be excluded from git blame results.
+#
+# To set this file as the default ignore file for git blame, run:
+#   $ git config blame.ignoreRevsFile .git-blame-ignore-revs
+
+# Run air formatter on project
+809462301b7e19d95dcf160ae9a85e1fe2c49b0d

.github/DISCUSSION_TEMPLATE/feature-requests.yml

@@ -4,6 +4,16 @@ body:
   - type: markdown
     attributes:
       value: |
+        Welcome to the Quarto CLI GitHub repository!
+        We are always happy to hear feedback from our users.
+
+        This is the repository for the command-line program `quarto`:
+
+        - If you're reporting an issue with the **Visual Editor** or with the **Visual Studio Code / Positron extension**, please visit https://github.com/quarto-dev/quarto
+        - If you're reporting an issue inside **RStudio**, please visit https://github.com/rstudio/rstudio
+        - If you're reporting an issue inside **Positron**, please visit https://github.com/posit-dev/positron
+        - If you want to ask for help, please use the [Q&A GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/q-a).
+
         First, please check [Quarto Issues](https://github.com/quarto-dev/quarto-cli/issues) and [Feature Requests GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/feature-requests) to see if your feature request has already been discussed.
         If it has, please consider adding a comment to the existing discussion instead of creating a new one.
 

.github/DISCUSSION_TEMPLATE/q-a.yml

@@ -3,7 +3,17 @@ body:
   - type: markdown
     attributes:
       value: |
-        First, please check [Quarto Issues](https://github.com/quarto-dev/quarto-cli/issues) and [Q&A GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/q-a) first to see if your question has already been asked.
+        Welcome to the Quarto CLI GitHub repository!
+        We are always happy to hear feedback from our users.
+
+        This is the repository for the command-line program `quarto`:
+
+        - If you're reporting an issue with the **Visual Editor** or with the **Visual Studio Code / Positron extension**, please visit https://github.com/quarto-dev/quarto
+        - If you're reporting an issue inside **RStudio**, please visit https://github.com/rstudio/rstudio
+        - If you're reporting an issue inside **Positron**, please visit https://github.com/posit-dev/positron
+        - If you want to ask for a feature, please use the [Feature Requests GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/feature-requests).
+
+        First, please check [Quarto Issues](https://github.com/quarto-dev/quarto-cli/issues) and [Q&A GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/q-a) to see if your question has already been asked.
         If it has, please consider adding a comment to the existing discussion instead of creating a new one.
 
         After checking, if you are not sure if your question has already been asked, please create a new discussion.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -11,9 +11,9 @@ body:
 
         This is the repository for the command-line program `quarto`:
 
-        - If you're reporting an issue with the VS Code extension, please visit https://github.com/quarto-dev/quarto
-        - If you're reporting an issue inside RStudio, please visit https://github.com/rstudio/rstudio
-        - If you're reporting an issue inside **Positron**, please visit https://github.com/posit-dev/positron
+        - If you're reporting an issue with the **Visual Editor** or with the **Visual Studio Code / Positron extension**, please visit https://github.com/quarto-dev/quarto
+        - If you're reporting an issue inside **RStudio**, please visit https://github.com/rstudio/rstudio
+        - If you're reporting an issue inside **Positron**, please visit https://github.com/posit-dev/positron/discussions
         - If you want to ask for a feature, please use the [Feature Requests GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/feature-requests).
         - If you want to ask for help, please use the [Q&A GitHub Discussions](https://github.com/quarto-dev/quarto-cli/discussions/categories/q-a).
 
@@ -53,6 +53,14 @@ body:
             The end.
             ````
 
+  - type: checkboxes
+    attributes:
+      label: "I have:"
+      options:
+        - label: searched the issue tracker for similar issues
+        - label: installed the latest version of [Quarto CLI](https://github.com/quarto-dev/quarto-cli/releases/latest)
+        - label: formatted my issue following the [Bug Reports guide](https://quarto.org/bug-reports.html)
+
   - type: textarea
     attributes:
       label: Bug description

.github/ISSUE_TEMPLATE/documentation.yml

@@ -29,6 +29,7 @@ body:
       required: true
 
   - type: textarea
+    id: description
     attributes:
       label: Description
       description: Describe the issue, give feedback or suggest an improvement.

.github/workflows/actions/prevent-rerun/action.yml

@@ -0,0 +1,11 @@
+name: Prevent Workflow Re-run
+description: Fails if the workflow is re-run (github.run_attempt > 1)
+runs:
+  using: "composite"
+  steps:
+    - name: Prevent any re-run
+      if: ${{ github.run_attempt > 1 }}
+      run: |
+        echo "::error::Re-running jobs is not permitted. Please trigger a new build manually at https://github.com/quarto-dev/quarto-cli/actions/workflows/create-release.yml (click 'Run workflow'), or use the GitHub CLI: 'gh workflow run create-release.yml'"
+        exit 1
+      shell: bash

.github/workflows/cleanup-caches.yml

@@ -0,0 +1,63 @@
+name: Cleanup github runner caches on closed pull requests
+on:
+  pull_request:
+    types:
+      - closed
+
+jobs:
+  cleanup:
+    runs-on: ubuntu-latest
+    permissions:
+      actions: write
+    steps:
+      - name: Cleanup
+        run: |
+          echo "::group::Fetching cache list for PR #${{ github.event.pull_request.number }}"
+          echo "Branch ref: $BRANCH"
+
+          # Get full cache list with details for logging
+          cacheList=$(gh cache list --ref $BRANCH --limit 100 --json id,key,sizeInBytes)
+          cacheCount=$(echo "$cacheList" | jq '. | length')
+
+          echo "Found $cacheCount cache(s) for this PR"
+
+          if [ "$cacheCount" -gt 0 ]; then
+            echo "Cache details:"
+            echo "$cacheList" | jq -r '.[] | "  - ID: \(.id) | Key: \(.key) | Size: \(.sizeInBytes | tonumber / 1024 / 1024 | floor)MB"'
+          fi
+          echo "::endgroup::"
+
+          if [ "$cacheCount" -eq 0 ]; then
+            echo "No caches to delete"
+            exit 0
+          fi
+
+          # Extract just the IDs for deletion
+          cacheKeysForPR=$(echo "$cacheList" | jq -r '.[].id')
+
+          ## Setting this to not fail the workflow while deleting cache keys.
+          set +e
+
+          echo "::group::Deleting caches"
+          deleted=0
+          failed=0
+
+          for cacheKey in $cacheKeysForPR
+          do
+              echo "Deleting cache ID: $cacheKey"
+              if gh cache delete $cacheKey; then
+                echo "  ✓ Successfully deleted cache $cacheKey"
+                ((deleted++))
+              else
+                echo "  ✗ Failed to delete cache $cacheKey"
+                ((failed++))
+              fi
+          done
+
+          echo "::endgroup::"
+
+          echo "::notice::Cache cleanup complete: $deleted deleted, $failed failed out of $cacheCount total"
+        env:
+          GH_TOKEN: ${{ github.token }}
+          GH_REPO: ${{ github.repository }}
+          BRANCH: refs/pull/${{ github.event.pull_request.number }}/merge