Update brew instructions #737
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This PR is going to conflict with this unmerged PR: #734 |
|
So, I would not worry about conflicts in this case - both PRs are very simple. That's what merge (or rebase) are for, right? No specific reason to keep your PR unmerged, @dashohoxha, just haven't had enough time to take a look yet - a pretty hectic day today :) |
shcheklein
approved these changes
Oct 25, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IMPORTANT NOTES (please read, then delete):
Have you followed the guidelines in
Contributing Documentation?
The PR title should start with "Fix #bugnum: " (if applicable), followed by a
clear one-line present-tense summary of the changes introduced in the PR. For
example: "Fix #bugnum: Introduce the first version of the collection editor.".
Please make sure to mention "Fix #bugnum" (if applicable) somewhere in the
description of the PR. This enables GitHub to link the PR to the corresponding
bug.