The steps in the readme to get it running locally were outdated and didn't reflect that the Gemfile points to a local copy of yard, so yard must be cloned prior to running bundle install.
Yard's been referenced locally for about a year now (see 2d8f6f2) so figured I'd update the steps to be accurate since it tripped me up for a second.
reorder readme steps reflecting that yard is required to bundle gems
Thanks. Ideally we want to use a gem install, but we maintain a separate install for yard as we occasionally run yard off of pre-releases. Unfortunately you can't list multiple sources for a dependency in a Gemfile.
Merge pull request #58 from cgunther/reorder-local-steps
Reorder readme steps reflecting that yard is required to bundle gems
What about pointing to the repo on GitHub via bundler, as opposed to a local install? http://gembundler.com/git.html
Only benefit there being that those who are not contributing to Yard as well don't have to worry about cloning it to the right path, bundler would just take care of fetching the prerelease.