Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Combine Homebrew organisation repositories #19210

Open
1 task done
MikeMcQuaid opened this issue Feb 3, 2025 · 2 comments
Open
1 task done

Combine Homebrew organisation repositories #19210

MikeMcQuaid opened this issue Feb 3, 2025 · 2 comments
Labels
features New features help wanted We want help addressing this

Comments

@MikeMcQuaid
Copy link
Member

Verification

Provide a detailed description of the proposed feature

We should combine as many repositories in the Homebrew organisation as possible. This includes moving as many external commands (e.g. homebrew-bundle, homebrew-services) taps into Homebrew/brew and all private repos into Homebrew/private.

After this, when creating new repositories or internet-accessible services with repositories in the Homebrew organisation: we should strive to reuse an existing repositories/service unless it is extremely painful to do otherwise (and, ideally, after discussion with @MikeMcQuaid and getting his 👍🏻).

Note: GitHub Pages sites (e.g. rubydoc.brew.sh, formulae.brew.sh, docs.brew.sh) are fine to be one-repo-per-pages-site.

What is the motivation for the feature?

Many reasons:

  • external commands are less discoverable than non-external commands and documented inconsistently
  • external commands rely on either slow public APIs/shelling out or break periodically due to using internal APIs
  • the more repositories we have: the more we need to sync, run dependabot updates on, check access control for, etc. etc.

How will the feature be relevant to at least 90% of Homebrew users?

It won't be but maintainers will like it.

What alternatives to the feature have been considered?

Doing nothing.

@MikeMcQuaid MikeMcQuaid added features New features help wanted We want help addressing this labels Feb 3, 2025
@colindean
Copy link
Contributor

My sole hesitation is my perception of homebrew-bundle as an example of an external command.

Should a part of this effort include or inspire the creation of a template external command repo since this effort could effectively eliminate the external command repos that Homebrew owns?

@MikeMcQuaid
Copy link
Member Author

My sole hesitation is my perception of homebrew-bundle as an example of an external command.

We could point to one of the external commands in homebrew-core instead: https://github.com/Homebrew/homebrew-core/tree/master/cmd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
features New features help wanted We want help addressing this
Projects
None yet
Development

No branches or pull requests

2 participants