brew/Library/Homebrew/cmd, branch 1.0.3 🍺 The missing package manager for macOS Fix Style/GuardClause. 2016-09-23T13:30:07+00:00 Markus Reiter 2016-09-22T18:12:28+00:00 a5b11a6a5c7e29b9040f93fd211f52479507dd01 






RuboCop has to be run inside `HOMEBREW_LIBRARY`.
2016-09-23T13:30:06+00:00

Markus Reiter

2016-09-21T10:43:05+00:00

ce6994b001520b8e5d26e5e15b410c9146072104












Update `rubocop` dependency to `0.43.0`.
2016-09-23T13:30:06+00:00

Markus Reiter

2016-09-21T07:59:45+00:00

21e0a7efb998b65c921885858969503513cad14b












Fix RuboCop CaseEquality.
2016-09-23T13:30:06+00:00

Markus Reiter

2016-09-20T20:03:08+00:00

52ff98853068c03b3bfa777932da1da69e35e583












Merge pull request #1103 from MikeMcQuaid/update-upstream-tag-strict
2016-09-23T13:26:04+00:00

Mike McQuaid

2016-09-23T13:26:04+00:00

4cbeb1e981e974474a0d37c120ffa18e13ac3db9

update.sh: only update to semver tags.




update.sh: only update to semver tags.






update.sh: only update to semver tags.
2016-09-23T10:26:24+00:00

Mike McQuaid

2016-09-23T10:26:24+00:00

b0dfd2d435fe6f5617bd699be90d86ad84bced02

Otherwise random e.g. `pr-123` tags may cause `brew update` to update
to the wrong version.





Otherwise random e.g. `pr-123` tags may cause `brew update` to update
to the wrong version.







sandbox: tweak HOMEBREW_REPOSITORY handling.
2016-09-23T07:29:05+00:00

Mike McQuaid

2016-09-23T07:26:49+00:00

536c48e804407a99c9fe750ca31cd42c7c1fd55a

If we have a HOMEBREW_REPOSITORY and HOMEBREW_PREFIX mismatch (now the
default) then we can block access to the whole of HOMEBREW_REPOSITORY
rather than just the HOMEBREW_LIBRARY and `.git`.





If we have a HOMEBREW_REPOSITORY and HOMEBREW_PREFIX mismatch (now the
default) then we can block access to the whole of HOMEBREW_REPOSITORY
rather than just the HOMEBREW_LIBRARY and `.git`.







update.sh: don't print "checkout branch" message.
2016-09-22T08:05:07+00:00

Mike McQuaid

2016-09-22T08:05:07+00:00

b33df4d0fad3ba6a968a86b14170ff1395239be3

It’ll only get printed for people getting updated to tags now and these
are people who haven’t run a `dev-cmd` so we want to air on the side of
telling them less stuff that will confuse them and assume people who
have manually made another `git` branch will know how to get back to it.





It’ll only get printed for people getting updated to tags now and these
are people who haven’t run a `dev-cmd` so we want to air on the side of
telling them less stuff that will confuse them and assume people who
have manually made another `git` branch will know how to get back to it.







uninstall: improve pronoun for multiple version message
2016-09-21T15:37:23+00:00

Joseph Frazier

2016-09-21T13:18:36+00:00

66ca9e79fc14f28e54f259bba94a52922728bde8

When exactly two versions of a package were installed, the uninstall
message should not read "Remove them all with...", since only one
version remains.

"Remove all versions with..." is flexible enough to avoid being
interpreted as grammatically incorrect, and it still accurately
describes the general behavior of `brew uninstall --force`.





When exactly two versions of a package were installed, the uninstall
message should not read "Remove them all with...", since only one
version remains.

"Remove all versions with..." is flexible enough to avoid being
interpreted as grammatically incorrect, and it still accurately
describes the general behavior of `brew uninstall --force`.







update.sh: tweak tag handling.
2016-09-21T13:32:48+00:00

Mike McQuaid

2016-09-21T13:32:48+00:00

f9bd121e387dfa478b924d1a28a439ae2318cafe

- Don't let the `UPSTREAM_TAG` variable bleed into future repository
  checks.
- Even if the tag branch is an ancestor of the tag ensure that it's
  forced back to the tag anyway.





- Don't let the `UPSTREAM_TAG` variable bleed into future repository
  checks.
- Even if the tag branch is an ancestor of the tag ensure that it's
  forced back to the tag anyway.