Add Markdown check/add language-specific triggers

[forstmeier]

Overview

Changes

• add Rust and Python language-specific path triggers
• add Markdown check workflow

Context

Markdown checks are already part of the pre-commit check so this is a good thing to add since we'll be working extensively in Markdown going forward.

Summary by CodeRabbit

• Chores
  • Added change-detection steps to PR validations that detect Markdown, Python, and Rust changes.
  • Gated language-specific code checks so Markdown, Python, and Rust jobs run only when relevant files changed.
  • Improved PR CI efficiency by avoiding unnecessary language-specific checks and reducing wasted runs.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds a new GitHub Actions workflow to run Markdown checks on PRs and updates Python and Rust workflows to detect changed files via dorny/paths-filter and conditionally run their checks only when relevant files changed.

Changes

Cohort / File(s)	Summary
Markdown workflow .github/workflows/run_markdown_code_checks.yaml	New workflow triggered on pull_request; adds detect_changes using dorny/paths-filter and a job that checks out code, installs Flox, and runs mask development markdown all when markdown files are detected.
Python workflow (gated) .github/workflows/run_python_code_checks.yaml	Added detect_changes job (paths-filter) and updated run_python_code_checks to needs: detect_changes with if: needs.detect_changes.outputs.python == 'true'. Outputs mapped from the filter step.
Rust workflow (gated) .github/workflows/run_rust_code_checks.yaml	Added detect_changes job (paths-filter) and updated run_rust_code_checks to needs: detect_changes with if: needs.detect_changes.outputs.rust == 'true'. Outputs mapped from the filter step.

Sequence Diagram(s)

sequenceDiagram
    participant PR as Pull Request
    participant GH as GitHub Actions
    participant Filter as dorny/paths-filter
    participant Runner as Job Runner
    participant Flox as Flox

    PR->>GH: push PR triggers workflows
    GH->>Filter: run detect_changes (paths-filter)
    Filter-->>GH: outputs (e.g., markdown=true / python=true / rust=true)
    GH->>Runner: start code_checks job if corresponding output == "true"
    Runner->>Runner: checkout repo & setup environment
    Runner->>Flox: install/setup Flox
    Runner->>Flox: run "mask development <lang> all" (e.g., markdown)
    Flox-->>Runner: return results
    Runner-->>GH: report job status

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• Various cleanup and tweaks #744: Refactors Flox activation behavior (manifest.toml) which directly affects the Flox activation invoked by the new Markdown job.
• Add various cleanup to command/prompt files #738: Adds markdownlint and pre-commit hook using mask development markdown all, closely related to the Markdown checks added here.
• Group GitHub workflow definitions by language #631: Reorganized language-specific GitHub Actions and modified the same Python/Rust workflow files; this PR adds path-detection gating atop that work.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add Markdown check/add language-specific triggers' accurately captures the main objectives of the PR: adding a new Markdown check workflow and implementing language-specific path-based triggers for Python and Rust workflows.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch expand-and-update-github-code-check-workflows

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[forstmeier]

• Add Markdown check/add language-specific triggers #746 👈 (View in Graphite)
• Add fixes for all GitHub Dependabot security alerts #745
• Various cleanup and tweaks #744
• Add Claude commands/remove Ralph logic #740
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

This PR adds language-specific path triggers to CI workflows to optimize build execution and introduces a new Markdown linting workflow.

Changes:

• Added path filters to Rust and Python workflow triggers to run only when relevant files change
• Created a new Markdown code checks workflow with appropriate file path triggers

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
.github/workflows/run_rust_code_checks.yaml	Added path filters for Rust source files and Cargo configuration files
.github/workflows/run_python_code_checks.yaml	Added path filters for Python source files and project configuration files
.github/workflows/run_markdown_code_checks.yaml	Created new workflow for Markdown linting with path triggers for .md and .markdown files

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR adds change-detection gating to the existing Python and Rust CI workflows (via dorny/paths-filter) so those checks only run when relevant files change, and introduces a new Markdown checks workflow that runs mask development markdown all via Flox when *.md/*.markdown files are touched.

The overall approach fits the repo’s existing mask-driven CI pattern and reduces unnecessary CI work on unrelated PRs.

Confidence Score: 3/5

• Mostly safe to merge once the Coveralls job permissions are made explicit.
• Workflow gating logic and YAML structure look correct, but the Python workflow’s coverage upload relies on GITHUB_TOKEN without declaring permissions, which can break CI in restricted-token environments.
• .github/workflows/run_python_code_checks.yaml

Important Files Changed

Filename	Overview
.github/workflows/run_markdown_code_checks.yaml	Adds Markdown-only workflow using dorny/paths-filter to gate a Flox+mask markdown check job.
.github/workflows/run_python_code_checks.yaml	Adds paths-filter gating for Python checks; coverage upload remains, but job lacks explicit token permissions for Coveralls reporting.
.github/workflows/run_rust_code_checks.yaml	Adds paths-filter gating for Rust checks to avoid running when no Rust-related files changed.

[greptile-apps]

_{3 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}

The base branch was changed.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[greptile-apps]

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In @.github/workflows/run_rust_code_checks.yaml:
- Around line 14-15: Replace the floating tag for the GitHub Action usage of
dorny/paths-filter (the line containing "uses: dorny/paths-filter@v3" and the
step id "filter") with the pinned commit SHA; change the version specifier from
"@v3" to "@de90cc6fb38fc0963ad72b210f1f284cd68cea36" so the workflow uses the
exact release (v3.0.2) instead of a moving tag.

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In @.github/workflows/run_markdown_code_checks.yaml:
- Around line 15-16: Replace the floating tag for the third-party GitHub Action
to pin it to the provided commit SHA: change the usage string
"dorny/paths-filter@v3" (the step with id "filter") to
"dorny/paths-filter@de90cc6fb38fc0963ad72b210f1f284cd68cea36" so the workflow
uses the exact commit (v3.0.2) instead of the floating `@v3` tag.

In @.github/workflows/run_python_code_checks.yaml:
- Around line 15-16: The workflow currently references the third-party action
using a floating tag at the 'uses' line (dorny/paths-filter@v3 with id
'filter'); update that 'uses' entry to pin the action to the specific commit SHA
de90cc6fb38fc0963ad72b210f1f284cd68cea36 (v3.0.2) to remove supply-chain risk
and ensure reproducible runs.