Skip to content

Instantly share code, notes, and snippets.

A strict branching model - but for Agencies

The git workflow I am proposing here is a mixture between both the Gitflow Workflow and the Feature Branch Workflow. The reason for not using either is because I like the simplicity of the feature branch workflow as well as the robustness of the Gitflow workflow, but they both do not seem to fit the needs of a fast moving agency completely. I have therefore tried to take the best out of those two and adapt it to my or rather our company's needs.

Challenges

Sometimes it is hard to maintain a proper development, test and release cycle. This can be due to many facts, but in my opinion mostly because of the following reasons:

  • Multiple features being worked on at the same time which all have to be deployed to a testing environment for QA
  • Features are getting pulled back or put on hold (by the
@Chive
Chive / social_network_apis.md
Created July 30, 2014 15:14
API Access for common social Networks

Instructions to gain API access to common social networks

Facebook

  1. Register yourself at https://developers.facebook.com
  2. Create a new app, select it from the top bar and head to its dashboard
  3. Go to Settings to add a new platform (type: website). Enter your site's URL/URLs and click on Save Changes
  4. Also make note of both your App ID and App Secret, you will need it later on
  5. On the dashboard of the just created app, select Status & Review and make the app public

Keybase proof

I hereby claim:

  • I am Chive on github.
  • I am chive (https://keybase.io/chive) on keybase.
  • I have a public key whose fingerprint is EDA1 D330 71FA 4863 C548 9D3A ED00 F37F D02A 51AB

To claim this, I am signing this object: