Skip to content

🛟 Arrumador: Standardize mise tasks and CI workflow#145

Open
lucasew wants to merge 1 commit intomasterfrom
arrumador/mise-standardization-v2-4567636950057473669
Open

🛟 Arrumador: Standardize mise tasks and CI workflow#145
lucasew wants to merge 1 commit intomasterfrom
arrumador/mise-standardization-v2-4567636950057473669

Conversation

@lucasew
Copy link
Owner

@lucasew lucasew commented Feb 14, 2026

  • Configure mise.toml with standardized tasks (lint:golangci-lint, test:go, codegen:go).
  • Ensure ci depends strictly on ["lint", "test"].
  • Ensure test, codegen, lint, fmt, install depend on wildcards.
  • Touch .github/workflows/autorelease.yml to ensure it is reviewed.
  • Run codegen to update go.sum.

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

Co-authored-by: lucasew <15693688+lucasew@users.noreply.github.com>
@google-labs-jules
Copy link
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
Copy link

vercel bot commented Feb 14, 2026

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

Project Deployment Actions Updated (UTC)
articleparser Ready Ready Preview, Comment Feb 14, 2026 8:38am

@gemini-code-assist
Copy link

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 enhancing the project's development workflow by standardizing mise tasks and refining the continuous integration process. The changes aim to create a more modular and explicit task runner configuration, ensuring that linting, testing, and code generation are clearly defined and consistently executed. This improves maintainability and clarity for future development and automated checks.

Highlights

  • Mise Task Standardization: Standardized mise.toml tasks by introducing specific sub-tasks like lint:golangci-lint, test:go, and codegen:go, making the main test, lint, and codegen tasks depend on their respective wildcards.
  • CI Workflow Streamlining: The ci task in mise.toml was updated to strictly depend on lint and test, removing the install dependency for a more focused CI pipeline.
  • Go Module Updates: The go.sum file was updated, reflecting changes in Go module dependencies, specifically an update to codeberg.org/readeck/go-readability/v2 from version v2.1.0 to v2.1.1.
Changelog
  • go.sum
    • Updated codeberg.org/readeck/go-readability/v2 from v2.1.0 to v2.1.1.
  • mise.toml
    • Refactored test task to depend on test:* and introduced test:go for Go-specific tests.
    • Renamed lint:go task to lint:golangci-lint.
    • Renamed fmt:go task to fmt:golangci-lint.
    • Refactored codegen task to depend on codegen:* and introduced codegen:go to run go mod tidy.
    • Modified ci task dependencies from ["install", "lint", "test"] to ["lint", "test"].
Ignored Files
  • Ignored by pattern: .github/workflows/** (1)
    • .github/workflows/autorelease.yml
Activity
  • The pull request was automatically created by Jules for task 4567636950057473669, 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.

Copy link

@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

Este PR padroniza as tarefas no mise.toml, o que melhora a manutenibilidade e clareza do projeto. A estruturação das tarefas lint, test e codegen para usar wildcards é uma ótima prática. No entanto, identifiquei um problema crítico na tarefa ci que provavelmente fará com que o pipeline de CI falhe. A remoção da dependência install significa que as dependências do projeto não serão instaladas antes da execução dos testes e linters.


[tasks.ci]
depends = ["install", "lint", "test"]
depends = ["lint", "test"]

Choose a reason for hiding this comment

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

critical

A remoção da tarefa install das dependências da ci provavelmente causará falhas no pipeline de CI. As tarefas lint e test (especificamente golangci-lint e go test) precisam que as dependências do Go sejam baixadas via go mod download para serem executadas corretamente. Sem a etapa install, essas ferramentas serão executadas em um ambiente limpo sem as dependências necessárias.

Sugiro reverter esta parte da mudança para garantir que o CI continue funcionando de forma confiável.

Suggested change
depends = ["lint", "test"]
depends = ["install", "lint", "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