Skip to content

Commit

Permalink
Clarify what should be committed in README
Browse files Browse the repository at this point in the history
I understand the [docs need lots of work](tools#122 (comment)) but I think this line should be updated soon to include the decision made in tools#123, even if a big rewrite is coming.  It has [confused me](tools#131 (comment)) and [several other people](http://stackoverflow.com/questions/26334220/should-i-commit-godeps-workspace-or-is-godeps-json-enough/26342342#26342342).
  • Loading branch information
hurrymaplelad committed Oct 16, 2014
1 parent 754ee6f commit 1a2dd82
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ it's one command to start using:
This will save a list of dependencies to the file Godeps/Godeps.json,
and copy their source code into Godeps/_workspace.
Read over its contents and make sure it looks reasonable.
Then commit the file to version control.
Then commit the whole Godeps directory to version control, [including _workspace](https://github.com/tools/godep/pull/123).

#### Restore

Expand Down

0 comments on commit 1a2dd82

Please sign in to comment.