Jim Foltz

My workflow is still evolving. I was trying to use branches to group together smaller, related commits for GitHub pull requests. I am not sure how this is working for...

US Eastern. I haven't settled on a branch workflow, because I'm still unsure how best to use them on GitHub. But this page[1] and the next has a good explanation...

Good idea, and a natural progression of our current workflow. Sounds more than a little like... http://nvie.com/posts/a-successful-git-branching-model/ I think I am finally comfortable enough with git to work with this...

One question I have is if I can continue to re-use my `develop` branch? If I delete the branch on GitHub and I continue using it locally.. then if I...

> I think we should try this. Are you talking about trying [Git Flow](https://github.com/nvie/gitflow)?

Slash or Dash in branch names? Something else? i.e. `git checkout -b feature/skui` `git checkout -b issue/24` or `git checkout -b feature-skui` `git checkout -b issue-24` I like the aesthetic...

I found these articles filled in a little more of the picture for me about how to use feature branches. - http://stackoverflow.com/questions/4428722/what-is-the-purpose-of-an-integration-branch - http://www.acquia.com/blog/pragmatic-guide-branch-feature-git-branching-strategy **Main Ideas** - The master branch...

Integration branches are meant to be temporary. Use integration branches to test code and merges from feature branches. Branching is fast and "cheap" in git. Sort of like a trial-run...

Yep.

I guess it won't have much of an effect on my workflow - I can only pull. I will continue working in feature/bug-fix branches designed for pull-requests.