registry: add ghtkn

[TyceHerrman]

Add ghtkn as a registry shorthand for suzuki-shunsuke/ghtkn.

Reason

ghtkn is now used as one of the methods for GitHub token management in mise.

Popularity

• GitHub: 149 stars, 1 fork
• Latest release: v0.2.4, published 2025-12-09
• Recent upstream activity: pushed in May 2026

Caveat

Public popularity is below the usual mise registry bar. This PR is still proposed because ghtkn is now used by mise.

Summary by CodeRabbit

• Chores
  • Added new registry configuration entry with support for multiple source backends (Aqua and GitHub) for obtaining releases and integrated version validation testing.

[greptile-apps]

Greptile Summary

This PR adds a single registry entry for ghtkn (suzuki-shunsuke/ghtkn), a CLI tool for creating short-lived GitHub App User Access Tokens for local development. The entry uses only Tier 1 backends and follows the established registry format.

• registry/ghtkn.toml: Adds aqua:suzuki-shunsuke/ghtkn and github:suzuki-shunsuke/ghtkn as backends — both Tier 1, no fragile runtime dependencies. The test block mirrors the pattern used by comparable entries (e.g., act.toml, acli.toml).
• The PR description satisfies the required popularity section and explicitly acknowledges the below-threshold star count, citing mise's own use of ghtkn as the rationale for submitting.

Confidence Score: 5/5

Safe to merge — the change is a single, well-formed registry TOML file with no logic, no migrations, and no runtime impact beyond adding the shorthand.

The entry uses only Tier 1 backends, matches the established registry format, includes a properly structured test block, and the PR description satisfies the required popularity documentation rule. No correctness issues were found.

No files require special attention.

Important Files Changed

Filename	Overview
registry/ghtkn.toml	New registry entry for suzuki-shunsuke/ghtkn; uses only Tier 1 backends (aqua: + github:), well-formed TOML with description and test block matching the existing registry pattern.

_{Reviews (4): Last reviewed commit: "registry: remove ghtkn go backend" | Re-trigger Greptile}

[gemini-code-assist]

Code Review

This pull request adds a new registry configuration for ghtkn, defining its backends, description, and a test command for version verification. As there are no review comments provided, I have no feedback to offer.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ae80867d-7e2c-47f6-bc0c-900190e62375

📥 Commits

Reviewing files that changed from the base of the PR and between a8bc180 and 4c6120a.

📒 Files selected for processing (1)

• registry/ghtkn.toml

---

📝 Walkthrough

Walkthrough

A new registry configuration file for ghtkn is added, defining a registry entry with two source backends (Aqua and GitHub) for release discovery, a description for short-lived GitHub App User Access Tokens, and a version test command with expected output.

Changes

ghtkn Registry Configuration

Layer / File(s)	Summary
ghtkn registry entry registry/ghtkn.toml	Registry configuration for ghtkn tool with Aqua and GitHub release backends, description indicating use for local development GitHub App tokens, and version command test expectation.

🎯 1 (Trivial) | ⏱️ ~2 minutes

🐰 A config file hops into place,
Three lines define a token's grace,
GitHub Apps for dev so keen,
Registry now holds something new, seen! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title 'registry: add ghtkn' directly and clearly summarizes the main change—adding a new ghtkn registry entry. It is concise, specific, and accurately reflects the primary modification in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}