Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

feat: add mise install support

Open
  • Is something wrong?
#789 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #790 by @AndryOre — closed without merging
  • #791 by @AndryOre — closed without merging
  • #792 by @AndryOre — closed without merging

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
ci-cd, documentation, tooling

Research direction

Read the 3-comment thread and closed PRs #790, #791, #792 first — three prior attempts were not merged, so the scope or approach may be contested. Then start from updateInstructions() in internal/version/check.go (plus its unit test) for the mise detection part, and compare go.mod with the CI workflow files to see what a root mise.toml pin and its drift-guard script must stay in sync with. Done means mise.toml exists, the guard runs in CI, docs/INSTALLATION.md and README.md document the mise install, and non-mise install hints are unchanged.

Written by the indexing model from the issue text.

Description

priority:low status:needs-review type:feature
Pre-flight Checks
  • I have searched existing issues and this is not a duplicate
  • I understand this issue needs status:approved before a PR can be opened
Problem Description

engram supports Homebrew, go install, and manual binary downloads, but has no first-class mise install path, and the repo declares no pinned toolchain of its own (contributors reconstruct Go/Node versions by reading go.mod and the CI workflows by hand). Separately, updateInstructions() (internal/version/check.go) only branches on runtime.GOOS, so a user who installed engram via mise is told to run brew upgrade engram or go install .../engram@latest — instructions that ignore (and can conflict with) the install mise already manages.

Proposed Solution
  • Add a mise.toml at the repo root pinning go and node to the versions the project already targets, plus a small CI guard script that fails a PR if that pin drifts from go.mod / the CI workflow files (so it can't silently go stale).
  • Document installing engram via mise in docs/INSTALLATION.md / README.md (macOS, Linux, and Windows — engram already ships Windows release archives).
  • Teach updateInstructions() to detect a mise-managed install and print mise upgrade engram instead of the Homebrew/go install hint in that case; every other install method keeps today's behavior unchanged.

Example:

mise use -g github:Gentleman-Programming/engram@latest
engram version

Companion registry submissions (separate, non-code, tracked outside this repo) are both merged now, so the shorter mise use -g engram@latest form will resolve once mise ships a release with the updated registry:

Affected Area

Other

Alternatives Considered

Leaving mise unsupported and only documenting Homebrew/go install/manual download — but this repo's own CI already needs a pinned Go/Node toolchain that contributors currently have to reconstruct by hand, and the update hint giving wrong advice to mise users is a real (if minor) correctness bug independent of mise adoption.

Dominant language
Go
Stars
7.1k
Forks
729
Avg merge
9h 11m
Merged PRs (30d)
359

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Gentleman-Programming/engram

All issues in Gentleman-Programming/engram

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.