Skip to content

registry: add portless (npm:portless)#8508

Merged
jdx merged 1 commit intojdx:mainfrom
risu729:patch-1
Mar 7, 2026
Merged

registry: add portless (npm:portless)#8508
jdx merged 1 commit intojdx:mainfrom
risu729:patch-1

Conversation

@risu729
Copy link
Copy Markdown
Contributor

@risu729 risu729 commented Mar 7, 2026

@gemini-code-assist
Copy link
Copy Markdown
Contributor

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 integrates a new 'portless' entry into the registry, enhancing the system's ability to manage and verify this specific backend. The changes provide a clear definition of 'portless' functionality and establish a method for confirming its operational status within the system.

Highlights

  • New Registry Entry: Added a new entry for 'portless' to the registry, specifying its backend as 'npm:portless'.
  • Description and Test Command: Included a description for 'portless' and defined a test command to verify its installation and version.
Changelog
  • registry/portless.toml
    • Added a new registry configuration for 'portless'.
Activity
  • The pull request was created by risu729.
  • A new file 'registry/portless.toml' was added.
  • The file 'registry/portless.toml' was populated with configuration details for the 'portless' package.
  • No human activity (comments, reviews) has been recorded yet.
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
Contributor

@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

The pull request adds the portless tool to the registry. The definition is mostly correct, but can be improved. I've suggested adding idiomatic_files to the tool definition to allow mise to automatically detect projects using portless.

Note: Security Review has been skipped due to the limited scope of the PR.

@jdx jdx enabled auto-merge (squash) March 7, 2026 22:21
@greptile-apps
Copy link
Copy Markdown
Contributor

greptile-apps bot commented Mar 7, 2026

Greptile Summary

This PR adds a new registry entry for portless, a tool that replaces port numbers with stable named .localhost URLs, backed by the npm backend. The single-file change follows the established pattern for npm-backed registry entries in this project.

  • The file structure (backends, description, test) is consistent with other npm-backed entries such as registry/amp.toml and registry/bibtex-tidy.toml.
  • The npm backend is appropriate here since portless is a Node.js CLI tool.
  • The test assertion uses expected = "{{version}}" (bare version output), which is a common pattern. If portless --version actually emits a prefix such as portless/1.0.0 or v{{version}}, the smoke test will fail at CI time.

Confidence Score: 4/5

  • This PR is safe to merge; it is a minimal, well-formatted registry addition with no logic changes.
  • The change is a single new TOML file following established patterns. The only minor uncertainty is whether portless --version emits a bare version string (matching {{version}}) or includes a prefix — this would surface quickly in the existing registry CI tests.
  • registry/portless.toml — verify the exact output of portless --version matches the expected pattern.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User runs: mise use portless] --> B[mise looks up registry/portless.toml]
    B --> C[Reads backends: npm:portless]
    C --> D[npm backend resolves package]
    D --> E[Installs portless from npm registry]
    E --> F[Runs test: portless --version]
    F --> G{Output matches expected: version}
    G -- Yes --> H[Installation verified]
    G -- No --> I[Test failure]
Loading

Last reviewed commit: 0a9a7ff

@jdx jdx merged commit da798f7 into jdx:main Mar 7, 2026
36 checks passed
@risu729 risu729 deleted the patch-1 branch March 7, 2026 22:34
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