Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
B
brew
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to JiHu GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
KMSCAKKSCFKA AKFACAMADCAS
brew
Commits
f45d5302
Commit
f45d5302
authored
5 years ago
by
Jonathan Chang
Browse files
Options
Downloads
Patches
Plain Diff
docs: Update for developer tap migration
parent
203f8d66
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/Homebrew-linuxbrew-core-Maintainer-Guide.md
+3
-3
3 additions, 3 deletions
docs/Homebrew-linuxbrew-core-Maintainer-Guide.md
with
3 additions
and
3 deletions
docs/Homebrew-linuxbrew-core-Maintainer-Guide.md
+
3
−
3
View file @
f45d5302
...
...
@@ -22,11 +22,11 @@ export HOMEBREW_NO_AUTO_UPDATE=1
Once we've done that, we need to get access to the
`merge-homebrew`
command that will be used for the merge. To do that we have to tap the
[
`
linuxbrew/homebrew-developer
`
](
https://github.com/
Linux
brew/homebrew-
developer
)
[
`
Homebrew/linux-dev
`
](
https://github.com/
Home
brew/homebrew-
linux-dev
)
repo:
```
bash
brew tap
linuxbrew/developer
brew tap
homebrew/linux-dev
```
Next, we have to navigate to the repository where we want to do the
...
...
@@ -273,7 +273,7 @@ only one commit with contents "# Build a bottle for Linuxbrew", these
have been created with
`brew build-bottle-pr`
and the commit from the
PR doesn't need preserving. We don't want to litter the codebase with
comments. In these cases, you can combine
`brew pull --bottle`
with
`brew squash-bottle-pr`
(in the
Linuxbrew/developer
tap). This will
`brew squash-bottle-pr`
(in the
Homebrew/linux-dev
tap). This will
squash the first commit message, leaving just the commit with the
bottle SHA authored by
`LinuxbrewTestBot`
. It will still close the PR,
as
`brew pull --bottle`
adds
`Closes`
and
`Signed-off-by`
to the
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment