Skip to content

fix: Improve build tooling configuration#45

Open
jcouball wants to merge 1 commit into
mainfrom
build-tooling-improvements
Open

fix: Improve build tooling configuration#45
jcouball wants to merge 1 commit into
mainfrom
build-tooling-improvements

Conversation

@jcouball
Copy link
Copy Markdown
Owner

Summary

Improvements to the build tooling and dependency configuration.

Changes

package.json

  • setup: Add asdf reshim python after pip install so that newly installed CLI tools (like mkdocs) are available on the PATH when using asdf
  • build/serve: Exclude .venv directory from markdown linting to avoid linting vendored dependencies

requirements.txt

  • Pin mkdocs version to ~= 1.6 for reproducible builds
  • Remove trailing blank line

- Add asdf reshim to setup script for Python compatibility
- Exclude .venv directory from markdown linting in build and serve
- Pin mkdocs version to ~= 1.6
- Remove trailing blank line from requirements.txt
Copilot AI review requested due to automatic review settings March 27, 2026 21:15
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refines local build/lint setup for the MkDocs documentation site by tightening dependency reproducibility and adjusting developer tooling scripts.

Changes:

  • Pin mkdocs to ~= 1.6 in requirements.txt.
  • Update setup to optionally run asdf reshim python after installing Python dependencies.
  • Exclude .venv from markdownlint runs invoked by build/serve.

Reviewed changes

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

File Description
requirements.txt Pins MkDocs to the 1.6.x line to reduce build variability.
package.json Enhances setup for asdf users and adjusts markdownlint globs for build/serve.

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

Comment thread package.json
{
"scripts": {
"setup": "npm install && pip3 install -r requirements.txt",
"setup": "npm install && pip3 install -r requirements.txt && (command -v asdf >/dev/null && asdf reshim python || true)",
Copy link

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The setup script currently swallows any failure from asdf reshim python (because of ... || true). If asdf is installed but the reshim fails, the script still exits successfully and CLI tools like mkdocs may still not be on PATH for asdf users. Consider using an explicit conditional (run asdf reshim python only when asdf exists) while letting real reshim failures surface.

Suggested change
"setup": "npm install && pip3 install -r requirements.txt && (command -v asdf >/dev/null && asdf reshim python || true)",
"setup": "npm install && pip3 install -r requirements.txt && (if command -v asdf >/dev/null; then asdf reshim python; fi)",

Copilot uses AI. Check for mistakes.
Comment thread package.json
"scripts": {
"setup": "npm install && pip3 install -r requirements.txt",
"setup": "npm install && pip3 install -r requirements.txt && (command -v asdf >/dev/null && asdf reshim python || true)",
"lint": "markdownlint-cli2 '**/*.md' '!node_modules'",
Copy link

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The .venv exclusion was added to build/serve, but npm run lint still runs markdownlint-cli2 without excluding .venv. If the goal is to avoid linting vendored dependencies consistently, lint should use the same ignore patterns as build/serve (or centralize the glob list to keep them in sync).

Suggested change
"lint": "markdownlint-cli2 '**/*.md' '!node_modules'",
"lint": "markdownlint-cli2 '**/*.md' '!node_modules' '!.venv'",

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants