You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a detailed description of the proposed feature
We have no good data on how often formulae fail outside the build stage This would, at least for homebrew/core, be good information to have to make better informed decisions about deprecation etc. Therefore it would be nice if audit and fetch failures, and possibly others would also be reported to InfluxDB.
What is the motivation for the feature?
The more maintainers know about the state of a package, the easier it should be to maintain it.
How will the feature be relevant to at least 90% of Homebrew users?
Happy maintainers make happy users
What alternatives to the feature have been considered?
Gathering the data from GitHub action runs, or not collecting data about this.
The text was updated successfully, but these errors were encountered:
Thanks for write-up @SMillerDev, added help wanted. As discussed at the AGM: I think this would be a good CI-specific way of identifying more issues with packages.
Verification
brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.Provide a detailed description of the proposed feature
We have no good data on how often formulae fail outside the build stage This would, at least for homebrew/core, be good information to have to make better informed decisions about deprecation etc. Therefore it would be nice if audit and fetch failures, and possibly others would also be reported to InfluxDB.
What is the motivation for the feature?
The more maintainers know about the state of a package, the easier it should be to maintain it.
How will the feature be relevant to at least 90% of Homebrew users?
Happy maintainers make happy users
What alternatives to the feature have been considered?
Gathering the data from GitHub action runs, or not collecting data about this.
The text was updated successfully, but these errors were encountered: