brew: consolidate trusted third-party taps into install/brew.d/taps

Open Beginner friendly
  • Is something wrong?
#67 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
shell
Domain
tooling

Research direction

Read install/brew and the Brewfiles under brew.d to see how taps are currently collected and trusted. Add install/brew.d/taps with each third-party tap and its reason, then update install/brew to use that file and report any Brewfile tap missing from it. Done means trust comes only from taps and a missing entry stops installation with a clear message.

Written by the indexing model from the issue text.

Description

Each third-party tap in brew.d was trusted on purpose, when its package
was installed. That decision is recorded only by its presence in a
Brewfile. install/brew finds every tap named in brew.d and runs
brew trust --tap on each.

The Brewfiles name eight third-party taps today:

charmbracelet/tap   drolosoft/tap   fastly/tap   openai/tools
rtk-ai/tap          vshulcz/tap     withgraphite/tap   xwmx/taps

The trust is the same either way. What changes is where it is written
down. Put it in one file, with a reason per tap.

Do

  1. Add install/brew.d/taps. One tap per line, with a reason:

     # <tap>             # why
 fastly/tap          # fastly CLI
 withgraphite/tap    # gt, stacked PRs

  2. Trust the taps in that file. Remove the loop that collects them from
    the Brewfiles.

  3. If a Brewfile names a tap that taps does not, stop. Print the tap
    and the Brewfile.

Done when

  • install/brew.d/taps lists each third-party tap with a reason.
  • install/brew reads trust from that file only.
  • A tap in a Brewfile but not in taps fails the install with a clear
    message.
Dominant language
Shell
Stars
1
Forks
0
Avg merge
9h 5m
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

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 indexzero/dotfiles

All issues in indexzero/dotfiles

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.