Skip to main content

homebrew, git

IN PROGRESS - Steps to contribute a cask to homebrew. Also a good way to stay in touch with git use if you don't have it at work.

https://github.com/caskroom/homebrew-cask/blob/master/CONTRIBUTING.md#getting-set-up-to-contribute

1: Fork the repository in GitHub with the Fork button.

create or login into your github account

use the Fork button at
https://github.com/caskroom/homebrew-cask

A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project. Most commonly, forks are used to either propose changes to someone else's project or to use someone else's project as a starting point for your own idea.

Now get a 'remote' local copy of the fork

you must have git installed
comes pre-installed on later osx versions
can switch to most current with homebrew - $brew install git



$ github_user='<my-github-username>'
$ cd "$(brew --repository)"/Library/Taps/caskroom/homebrew-cask
$ git remote add "${github_user}" "https://github.com/${github_user}/homebrew-cask"


Now update your remote to master - 'pull' most current for master branch
https://help.github.com/articles/merging-an-upstream-repository-into-your-fork/
git checkout master


  1. git pull https://github.com/ORIGINAL_OWNER/ORIGINAL_REPOSITORY.git BRANCH_NAME
    
  2. =
  1. git pull https://github.com/christopinka/homebrew-cask.git master
deal with conflicts

Push the merge to your GitHub repository.
git push origin master

next time I commit something I'll complete the example

Comments

Popular posts from this blog

Answer to interview question - "What is the most important thing Object Oriented languages have contributed to software development?" ...sufficiently  model  the real world and problem at hand before jumping the gun. ...the success of graphical user interfaces like X and Windows. A GUI consists of several objects which have a behaviour on their own, something that OO is able to represent closely. ...polymorphism to match the logical way classification worked in real life -> code reuse ..limit project churn s tackexchange Tony Hoare introduced Null references in ALGOL W back in 1965 “simply because it was so easy to implement”, says Mr. Hoare. He talks about that decision considering it “my billion-dollar mistake”.  http://www.infoq.com/presentations/Null-References-The-Billion-Dollar-Mistake-Tony-Hoare

devops day 1

Kubernetes on a mac tutorial Assumes you have node and docker. Get them with homebrew works. https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/