Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Comparing changes

Choose two branches to see what's changed or to start a new pull request. If you need to, you can also compare across forks.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also compare across forks.
base fork: codeodor/How-to-avoid-becoming-a-formerly-employed-rails-developer-standing-in-line-at-the-OOP-kitchen
base: aee6152817
...
head fork: codeodor/How-to-avoid-becoming-a-formerly-employed-rails-developer-standing-in-line-at-the-OOP-kitchen
compare: 0e7313b1d6
Checking mergeability… Don't worry, you can still create the pull request.
  • 2 commits
  • 1 file changed
  • 0 commit comments
  • 1 contributor
Commits on Feb 14, 2012
@codeodor updated readme c7ab58f
@codeodor Merge branch 'master' of github.com:codeodor/How-to-avoid-becoming-a-…
…formerly-employed-rails-developer-standing-in-line-at-the-OOP-kitchen
0e7313b
Showing with 8 additions and 3 deletions.
  1. +8 −3 README.rdoc
View
11 README.rdoc
@@ -23,6 +23,11 @@ If you'd rather have me demonstrate a technique, get in touch with me at (insert
I'll keep a list of the major fixes here, so you can refer to them easily.
Tentative workflow will be:
-1. Original bad code will be in its own branch, so develop the example of what needs to be fixed on that branch.
-2. Create an issue that points out the bad code, develop a fix for it, do a pull request so the fix is highlighted, then merge it back into master.
-3. Except at the beginning, the master branch should be a good example for people to look at.
+1. Original bad code is in its own branch: bad_shape. Develop the example of what needs to be fixed on that branch.
+2. Create an issue that points out the bad code
+3. Develop a fix for it in a new branch. Try to remember to prepend #123 (the issue number to commit messages).
+4. Do a pull request so the fix is highlighted, then merge it back into master.
+5. Except at the beginning, the master branch should be a good example for people to look at.
+
+I'm taking suggestions on how to improve the workflow. It feels clunky. If you don't know how to get in touch with me, try
+{the contact form on my blog}[http://www.codeodor.com/contact.cfm].

No commit comments for this range

Something went wrong with that request. Please try again.