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

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

There’s a lot of talk about transformation and some metrics around what we are lacking and need to do better. Do we also know what we do well and the good things about our work processes and environment that we want to keep? I’m concerned that if we don’t diagram this as a spectrum we risk running over those good things that we do in the course of transforming. Running agile retrospectives at team levels could provide us with this feedback DAKI – drop, add, keep, improve | Fun Retrospectives www.funretrospectives.com/daki-drop-add-keep-improve/ 1.         2.         DAKI is a great data gathering to foster the thinking around practices and the value the team get from it. It helps team members to understand each other ... KALM – Keep, Add, More, Less | Fun Retrospectives www.funretrospectives.com/kalm-keep-add-more-less/ 1.         2.       ...

Microservices Design Patterns

functional decomposition or domain-driven design well-defined interfaces  explicitly published interface  single responsibility principle potentially polyglot http://blog.arungupta.me/microservice-design-patterns/ http://blog.arungupta.me/microservices-monoliths-noops/ https://go.forrester.com/blogs/13-11-20-mobile_needs_a_four_tier_engagement_platform/ three-tier architecture — presentation, application, data vs. 4 tier -- client, delivery, aggregation, services