A successful Git branching model » nvie.com In this post I present the development model that I’ve introduced for some of my projects (both at work and private) about a year ago, and which has turned out to be very successful. I’ve been meaning to write about it for a while now, but I’ve never really found the time to do so thoroughly, until now. I won’t talk about any of the projects’ details, merely about the branching strategy and release management. Why git? ¶ For a thorough discussion on the pros and cons of Git compared to centralized source code control systems, see the web. But with Git, these actions are extremely cheap and simple, and they are considered one of the core parts of your daily workflow, really. As a consequence of its simplicity and repetitive nature, branching and merging are no longer something to be afraid of. Enough about the tools, let’s head onto the development model. Decentralized but centralized ¶ Each developer pulls and pushes to origin. The main branches ¶ masterdevelop Supporting branches ¶ develop
List of HTTP status codes This is a list of Hypertext Transfer Protocol (HTTP) response status codes. Status codes are issued by a server in response to a client's request made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some additional codes used in some common applications of the Hypertext Transfer Protocol (HTTP). The first digit of the status code specifies one of five standard classes of responses. The message phrases shown are typical, but any human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231). The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes. Microsoft Internet Information Services (IIS) sometimes uses additional decimal sub-codes for more specific information, however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code. 100 Continue 2xx Success
How to GitHub: Fork, Branch, Track, Squash and Pull Request - Gun.io This guide will teach you how to properly contribute to open source projects on GitHub. It assumes that you already know about how to use Git for version control and that you already have a GitHub account. Psstt.. if you already have a GitHub account and you want to earn more money, sign up for Gun.io with your GitHub profile and we'll pair you with people looking for developers based on your portfolio! Getting Started GitHub displays these instructions when you start a new project. GitHub is pretty great about giving advice to users starting new repositories, but it isn't very helpful when it comes to contributing changes back to other projects. Before you get started, find the page of the project you're looking to improve. Check the Network The network graph. The first thing to do is check the Network tab on the project to see all the other forks that other people have made. Opening an Issue You've got issues, man. Next, head over to the Issues tab. Making Your Fork Hardcore Forking Action
Your One-Stop Guide to Laravel Commands In this day and age, it's quite normal for a developer to have an understanding of consoles, and how to issue basic commands. But what if you could code your own custom commands to improve your workflow? If we look back to Laravel 3, you might remember that it offered tasks. What is Artisan? Artisan is the command line utility that was released in Laravel 3. If you're not familiar with Laravel, then you might not be aware of Artisan. Artisan offers many useful commands that can help you perform various tasks, such as generating migrations or publishing a package's assets. Artisan's Foundations This is where Artisan draws its power. In Laravel 3, Artisan was written from scratch by Taylor Otwell (Laravel's creator), thus it was quite basic (although still awesome). If we take a look at the source of the Artisan application at Illuminate\Console\Application, we can see that the class, itself, extends Symfony\Component\Console\Application. Common Questions Q Where should I put commands? Options
How to Integrate Slack with Github, Google Drive and more A few years back, the primary mode of communication for a team was via mailing lists (for example, those old Python mailman lists — remember those?) As time passed, Google Groups came to the rescue, and managing threads for team communications became a lot easier. Teams all around the world began to use it, and most were happy with its features. In recent years, however, tools like Redmine and Trello have arrived, providing greater control over projects — with features for project management a step ahead of forums. At IMG, IIT Roorkee, we used Google Groups as our primary mode of communication, until we realized the time had come to take it to the next level. Slack is a collection of chat rooms, both public and private. Getting Started If you are the team lead, just head over to Slack and create your team. You can create public or private chat rooms, with the option of one-to-one messaging as well. Here’s a bonus — you can customize almost everything. Search Custom notifications 1. 2. 3.
nvie/gitflow: Git extensions to provide high-level repository operations for Vincent Driessen's branching model. 15 Incredible Sites Built With Twitter Bootstrap Here at Untame we have a special place in our hearts that is only filled by one thing – responsive design and smart design (okay, okay: two things). Twitter Bootstrap is a flexible front end framework that provides developers and designers an incredible set of tools that they can wield in as large or as small a capacity as needed. In any number of uses, there are tons of great sites that benefit from the Twitter Bootstrap framework and we want to highlight just a few! The Pink League Improvely Discoursehq leanix CodrSpace BreweryDB Opencooks NoteSurf Resource Guru Gusta Cup Trek Bagel Hint Percentage Calculator Sweet Soundtrack NameVine Well there you are!
GitHub Flow – Scott Chacon August 31, 2011 Issues with git-flow I travel all over the place teaching Git to people and nearly every class and workshop I’ve done recently has asked me what I think about git-flow. However, it does have its issues. One of the bigger issues for me is that it’s more complicated than I think most developers and development teams actually require. Both of these issues can be solved easily just by having a much more simplified process. Its simplicity gives it a number of advantages. GitHub Flow So, why don’t we use git-flow at GitHub? There are a number of advantages to deploying so regularly. Another advantage of deploying all the time is the ability to quickly address issues of all kinds. How We Do It So, what is GitHub Flow? That is the entire flow. So, let’s look at each of these steps in turn. #1 - anything in the master branch is deployable This is basically the only hard rule of the system. You could have a deployed branch that is updated only when you deploy, but we don’t do that.
Speaking With the Ember.js Core Team Single page apps are the new hotness; everyone's trying to figure out the easiest way to build them. But it's more than just finding a couple of controls to slap together and sprinkling Ajax pixie dust on it. Building scalable and maintainable apps is serious business, which requires serious tools. Ember.js is a very serious framework for doing just that. Check out the interview I did with Ember.js Core Team leads, Yehuda Katz and Tom Dale, as they discuss what prompted them to begin the Ember project, its design philosophy, and where it fits into an already crowded library ecosystem. Q Tell us about your professional backgrounds. Yehuda: I was an Accounting major in college, with a whole bunch of interesting minors (Journalism, Philosophy, History, TV/Radio). I had rejected a computer science major on the grounds that it was too hard and "not for me," even though I had done a small amount of QBasic programming as a kid and some Visual Basic in college. Take bindings, for example.
Using git-flow to automate your git branching workflow If you need tagged and versioned releases, you can use git-flow’s release branches to start a new branch when you’re ready to deploy a new version to production. Like everything else in git-flow, you don’t have to use release branches if you don’t want to. Prefer to manually git merge --no-ff develop into master without tagging? $ git flow release start 0.1.0 Switched to a new branch 'release/0.1.0' Summary of actions: - A new branch 'release/0.1.0' was created, based on 'develop' - You are now on branch 'release/0.1.0' Follow-up actions: - Bump the version number now! Bump the version number and do everything that’s required to release your project in the release branch. $ git flow release finish 0.1.0 Switched to branch 'master' Merge made by the 'recursive' strategy. authentication.txt | 1 + 1 file changed, 1 insertion(+) create mode 100644 authentication.txt Deleted branch release/0.1.0 (was 1b26f7c).
dafont.com winton/gitcycle · GitHub 10 Time Saving Online Color Tools for Web Designers Working with colors is a time consuming task for a web designer, for starters you need to pick out a color palette for your designs, then there’s all kinds of code values to remember and convert from hex to RGBa. To speed things up and make the designer’s life much easier a bunch of handy tools are available online. These tools help you pick, choose and convert your color selections with ease for your next web design project. If you’re starting a design from scratch with no brand guidelines or colour inspiration it can be tricky putting together a colour scheme that works. Here’s a few tools that will help you put together a pretty combination of colours that are guaranteed to work. ColourLovers ColourLovers is home to millions of user generated color palettes. Kuler Adobe’s Kuler is a powerful tool that only allows you to browse and rate existing color themes, but also includes tools for creating your own palette from scratch. Pictalulous color.hailpixel.com Hexu.al CSS Color Names Sphere