| Age | Commit message (Collapse) | Author |
|
If `--no-browse` is passed, don't pass the `--browse` argument to `hub`
which opens the pull request URL in a browser. Instead, output it to the
command line.
|
|
These are both tools that end-users can find useful on occasion so it
doesn't make sense to hide them.
|
|
|
|
brew deps: add --include-requirements, plus some fixes
|
|
|
|
Fixes #3021.
|
|
May as well use the more secure link when possible.
|
|
- Document ilovezfs as the official lead maintainer of
Homebrew/homebrew-core. This is a role he's been doing unofficially
(and brilliantly) for a while and explicit documentation of power
structures makes it easier for non-Homebrew-maintainers to understand.
- Document the contents of some of Homebrew's subdirectories for people
clicking around in the GitHub UI looking to contribute.
- Remove update bug mention from README. Enough time has passed that we
can remove this disappointment.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Remove pending tests that are never run on CI (i.e. require `--online`),
remove fixtures for those tests and just make `--official-cmd-taps`
run by `--online` instead.
|
|
Fix internal links on the manpage
|
|
These previously, incorrectly pointed to bot.brew.sh.
Fixes #2703.
|
|
- only document HOMEBREW_* variables in the manpage (although still
read from all the original environment variables).
- resort manpage environment variables in alphabetical order
- check the original path for trailing slashes
|
|
|
|
|
|
|
|
|
|
Also refactor audit cops into two "departments"
- FormulaAudit
- FormulaAuditStrict
|
|
|
|
audit: allow skipping audit methods.
|
|
GitHub provides a description and homepage field so let `brew create`
use them where possible. Also, detect GitHub repositories based on
`releases` as well as `archive`s.
|
|
Add `--only` and `--except` methods which can be used to selectively
enable or disable audit groups.
|
|
|
|
This is useful when you're pulling PRs where individual bottles can't be
uploaded/built but you still want to pull the PR as a whole anyway.
|
|
The existing `brew.1.html` wasn't particularly pleasant to read and
given everything else in `docs/` is a Markdown file it makes sense to
generate a post-processed Markdown file that can in turn be used by
Jekyll to generate a nicely themed HTML file.
|