lgtmaybe

Version updated for https://github.com/MattJColes/lgtmaybe to version lgtmaybe-v2.5.0.

  • This action is used across all versions by ? repositories.

Action Type

This is a Composite action.

Go to the GitHub Marketplace to find the latest changes.

Action Summary

The lgtmaybe GitHub Action is a tool designed to review pull requests or merge requests across multiple version control platforms (GitHub, GitLab, and Gitea) using AI-based models. It generates inline comments on changes, focusing on logic errors, security vulnerabilities, missing tests, outdated code, performance regressions, unnecessary complexity, intent alignment, and unnecessary code, all without executing the code. The tool is designed to be secure by not running any of the PR’s code and redacting sensitive information before submission to the model.

What’s Changed

2.5.0 (2026-08-20)

Features

  • hold the advisory lenses to the severity their prompt asks for (#529) (c9aab3c)

Bug Fixes

  • count tokens in the model’s own tokenizer and reserve prompt overhead (#528) (d41dab9), closes #509
  • escape the file path when fetching file contents (#522) (c244bf7), closes #508
  • honour resolve_fixed on GitLab (#525) (6f5efe5), closes #502
  • read a fenced reply in /ask and follow-up validation (#523) (ae4e650), closes #510 #511
  • read a self-hosted server’s tool-call rejection wording (#526) (3e3a200), closes #499

Performance Improvements

  • overlap the per-file boundary scans and guard the flood counter (#524) (70b87e5), closes #505 #506

Documentation

  • correct the gitea token scopes and drop a flag that does not exist (#527) (fd36563), closes #500 #501
  • rescore the model-choice tables and correct three recommendations (#512) (d9953cc)