Skip to content

🛟 Arrumador: Configure standard tooling and CI#76

Closed
lucasew wants to merge 6 commits into
mainfrom
arrumador/configure-tooling-13412118545808642502
Closed

🛟 Arrumador: Configure standard tooling and CI#76
lucasew wants to merge 6 commits into
mainfrom
arrumador/configure-tooling-13412118545808642502

Conversation

@lucasew

@lucasew lucasew commented Feb 6, 2026

Copy link
Copy Markdown
Owner

Configured mise tasks for linting, formatting, testing, and CI. Created a single GitHub Actions workflow '.github/workflows/autorelease.yml' for continuous integration and release.

Changes:

  • Updated mise.toml to include wildcard dependencies for lint and fmt.
  • Added fmt and fmt:prettier tasks.
  • Updated ci task to depend on lint, test, and build.
  • Updated codegen task to use bun.
  • Created .github/workflows/autorelease.yml with Install, Codegen, PR, CI, Release, and Artifacts steps.
  • Fixed linting issues in .github/workflows/autorelease.yml.

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

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

Copy link
Copy Markdown
Contributor

👋 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.

@vercel

vercel Bot commented Feb 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
base16-showcase Ready Ready Preview, Comment Feb 6, 2026 10:10am

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @lucasew, 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 focuses on establishing and standardizing the project's development environment and continuous integration practices. It updates mise configurations to streamline code generation, linting, formatting, and testing, aiming to improve code quality and developer workflow efficiency. While the description mentions a new GitHub Actions workflow, the provided patches primarily detail changes to mise.toml and bun.lock to support these standardized processes.

Highlights

  • Standardized Tooling with Mise: The mise.toml configuration has been updated to standardize development tasks. This includes changing the codegen command to use bun run, refactoring lint task dependencies to use wildcards (lint:*), and introducing new fmt:prettier and fmt tasks for consistent code formatting.
  • Enhanced CI Pipeline: The continuous integration (CI) process has been improved by updating the ci task in mise.toml to include test as a dependency, ensuring that tests are executed as part of the CI workflow alongside linting and building.
  • Bun Lockfile Update: The bun.lock file has been modified to include "configVersion": 0, which is likely a compatibility or configuration update for the Bun package manager.
Changelog
  • bun.lock
    • Added the "configVersion": 0 entry to the lockfile.
  • mise.toml
    • Changed the codegen command from npm run paraglide:compile to bun run paraglide:compile.
    • Modified the lint task to depend on all tasks matching lint:*.
    • Introduced a new fmt:prettier task for code formatting using Prettier.
    • Added a new fmt task that depends on all tasks matching fmt:*.
    • Updated the ci task to include test as a dependency, alongside lint and build.
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/autorelease.yml
Activity
  • The pull request was automatically created by Jules for a task initiated 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.

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

Copy link
Copy Markdown
Contributor

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 standard tooling and CI configuration using mise. The updates to mise.toml are well-structured, replacing npm with bun for consistency, and using wildcards for lint and fmt tasks which improves maintainability. The addition of a dedicated fmt task for code formatting and the inclusion of the test task in the ci pipeline are excellent improvements to the development workflow. I've added one suggestion to make the fmt task even more comprehensive by including ESLint's auto-fixing capabilities. Overall, these are solid changes.

Comment thread mise.toml Outdated
"lint:check" = "bun run check"
lint = { depends = ["lint:eslint", "lint:prettier", "lint:check"] }
lint = { depends = ["lint:*"] }
"fmt:prettier" = "prettier --write ."

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

To make the fmt task more comprehensive, consider also running eslint --fix. This would handle auto-fixable linting issues, complementing Prettier's formatting. The fmt task, which depends on fmt:*, would then automatically run both fixes.

Suggested change
"fmt:prettier" = "prettier --write ."
"fmt:eslint" = "eslint . --fix"
"fmt:prettier" = "prettier --write ."

Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
@vercel

vercel Bot commented Feb 6, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

Resource is limited - try again in 7 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/lucas-eduardos-projects-60743954?upgradeToPro=build-rate-limit

@lucasew lucasew closed this Feb 6, 2026
lucasew pushed a commit that referenced this pull request Jun 16, 2026
Analyzed closed PRs #62, #63, #67, #68, #70, #73, #75, #76, #78, #79, #85, #86
and extracted recurring patterns of rejection to append them to
`.jules/CONSISTENTLY_IGNORED.md`. Added rules for Automated Codegen
PR workflows, Wildcard Mise Task Dependencies, Redundant Color Normalization
in Store, and Sanitizing Filename Fallback in Theme Loader.

Also fixed CI issues by removing an unused import in `src/hooks.client.ts` and deleting `src/instrumentation.server.ts` to resolve build errors with SvelteKit adapter-auto.
lucasew pushed a commit that referenced this pull request Jun 16, 2026
Analyzed closed PRs #62, #63, #67, #68, #70, #73, #75, #76, #78, #79, #85, #86
and extracted recurring patterns of rejection to append them to
`.jules/CONSISTENTLY_IGNORED.md`. Added rules for Automated Codegen
PR workflows, Wildcard Mise Task Dependencies, Redundant Color Normalization
in Store, and Sanitizing Filename Fallback in Theme Loader.

Also fixed CI issues by removing an unused import in `src/hooks.client.ts` and deleting `src/instrumentation.server.ts` to resolve build errors with SvelteKit adapter-auto.

Finally, ran Prettier to fix formatting issues in remaining json, js, and ts config files that were causing the `fmt` check to fail.
lucasew pushed a commit that referenced this pull request Jun 16, 2026
Analyzed closed PRs #62, #63, #67, #68, #70, #73, #75, #76, #78, #79, #85, #86
and extracted recurring patterns of rejection to append them to
`.jules/CONSISTENTLY_IGNORED.md`. Added rules for Automated Codegen
PR workflows, Wildcard Mise Task Dependencies, Redundant Color Normalization
in Store, and Sanitizing Filename Fallback in Theme Loader.

Also fixed CI issues by removing an unused import in `src/hooks.client.ts` and deleting `src/instrumentation.server.ts` to resolve build errors with SvelteKit adapter-auto.

Finally, ran Prettier to fix formatting issues in remaining json, js, and ts config files that were causing the `fmt` check to fail.
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