Skip to content

🛟 Arrumador: Configure mise, workspaced, and CI#50

Draft
lucasew wants to merge 1 commit intomasterfrom
arrumador-configure-tooling-5507031256308492343
Draft

🛟 Arrumador: Configure mise, workspaced, and CI#50
lucasew wants to merge 1 commit intomasterfrom
arrumador-configure-tooling-5507031256308492343

Conversation

@lucasew
Copy link
Copy Markdown
Owner

@lucasew lucasew commented Feb 28, 2026

Assumptions

  • The monorepo requires standard task aggregation using wildcard dependencies (test:*, install:*, codegen:*).
  • Specific tools (npm, go, cargo, make) can be executed contextually within subdirectories containing matching files (package.json, go.mod, Cargo.toml, Makefile) via the find ... -execdir ... pattern.
  • The project does not use Vercel or Cloudflare, meaning release and artifact generation conditionally runs on dispatch or tag.

Alternatives Not Chosen

  • Adding individual linter tools for Go, JS, or Rust manually. Decided against it per strict requirement to use workspaced codebase lint.
  • Manually listing install:go, test:npm, etc., inside depends. Decided against it per strict requirement to use wildcards.

How To Pivot

  • If find causes unexpected behaviors on non-Unix systems, update the commands in mise.toml to a cross-platform alternative or define specific tasks explicitly for known subdirectories.

Next Knobs

  • mise.toml [tools]: Update tool pins.
  • mise.toml [tasks.*]: Adjust find parameters or add/remove languages like Python or Ruby.
  • .github/workflows/autorelease.yml: Add actual artifact paths inside the Upload Artifacts step.

PR created automatically by Jules for task 5507031256308492343 started by @lucasew

Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request establishes a foundational development environment and continuous integration setup for the monorepo using mise and workspaced. It standardizes tool versions and defines a set of aggregate and language-specific tasks, enabling consistent execution of linting, formatting, testing, installation, and code generation across various subprojects. The approach emphasizes wildcard dependencies and contextual execution to streamline monorepo management.

Highlights

  • Mise Configuration: Configured mise to manage specific versions of Go (1.22.5), Node.js (20.15.0), Task (3.38.0), and the workspaced tool (0.1.3).
  • Aggregate Tasks Defined: Defined aggregate tasks such as lint, fmt, test, codegen, install, and ci to standardize common development operations across the monorepo, utilizing wildcard dependencies for test:*, codegen:*, and install:*.
  • Language-Specific Task Automation: Implemented language-specific installation, testing, and codegen tasks for Go, Node.js (npm), Rust (cargo), and Makefiles. These tasks use find -execdir to contextually execute commands like go mod tidy, npm install, cargo build, go test, npm test, cargo test, and make within relevant subdirectories.
Changelog
  • mise.toml
    • Added [tools] section to pin versions for Go, Node.js, Task, and workspaced.
    • Added [tasks] section to define aggregate and language-specific commands for linting, formatting, testing, installation, and code generation.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/autorelease.yml
Activity
  • The pull request was automatically created by Jules for a task started by @lucasew.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request introduces a mise.toml configuration to standardize tasks across a monorepo for Go, Node.js, and Rust projects. The approach of using find to discover and execute tasks is flexible. My review focuses on improving the robustness of these find commands to prevent them from running in unintended directories, such as build artifact folders or vendored dependency directories. I have provided suggestions to add exclusions for vendor directories in Go-related tasks and target directories for Rust tasks. Additionally, I've suggested a performance improvement for the Rust installation task.

Comment thread mise.toml
depends = ["lint", "test"]

[tasks."install:go"]
run = "find . -name go.mod -execdir go mod tidy \\;"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

The find command for the Go install task could inadvertently run on go.mod files within a vendor directory if the project uses vendoring. This can lead to unexpected behavior. It's best to explicitly exclude the vendor directory from the search.

run = "find . -name go.mod -not -path '*/vendor/*' -execdir go mod tidy \;"

Comment thread mise.toml
run = "find . -name package.json -not -path '*/node_modules/*' -execdir npm install \\;"

[tasks."install:rust"]
run = "find . -name Cargo.toml -execdir cargo build \\;"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

This task can be improved in two ways:

  1. The find command should exclude the target directory by adding -not -path '*/target/*' to avoid running cargo on build artifacts, which can cause errors.
  2. For an install task, cargo build performs a full compilation. Using cargo check is often more appropriate as it's faster. It verifies compilation and fetches dependencies without generating final artifacts.
run = "find . -name Cargo.toml -not -path '*/target/*' -execdir cargo check \;"

Comment thread mise.toml
run = "find . -name Cargo.toml -execdir cargo build \\;"

[tasks."test:go"]
run = "find . -name go.mod -execdir go test ./... \\;"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

The find command for the Go test task could inadvertently run on go.mod files within a vendor directory if the project uses vendoring. This can lead to unexpected behavior or test failures. It's best to explicitly exclude the vendor directory from the search.

run = "find . -name go.mod -not -path '*/vendor/*' -execdir go test ./... \;"

Comment thread mise.toml
run = "find . -name package.json -not -path '*/node_modules/*' -execdir npm test --if-present \\;"

[tasks."test:rust"]
run = "find . -name Cargo.toml -execdir cargo test \\;"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

high

The find command should exclude the target directory to avoid running cargo on build artifacts or dependencies within it, which can cause unexpected errors during testing. Please add -not -path '*/target/*' to the find command.

run = "find . -name Cargo.toml -not -path '*/target/*' -execdir cargo test \;"

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.

1 participant