Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure you execute rake rdoc from rails root directory [ci skip] #19932

Merged
merged 1 commit into from Apr 28, 2015

Conversation

axilleas
Copy link
Contributor

\cc @senny

@senny
Copy link
Member

senny commented Apr 28, 2015

@axilleas can you please combine this PR with #19933 and #19934 and squash the commits? We try to keep related changes together.

@axilleas
Copy link
Contributor Author

Ah ok sure.

@senny
Copy link
Member

senny commented Apr 28, 2015

@axilleas thanks man 💛

@axilleas
Copy link
Contributor Author

No problem, it's the commit messages that give me headaches so I try to split the PRs but I feel you :) It should be fixed.

lol I missed your heart emoticons back when you helped at the GitLab bug tracker 😄

@senny
Copy link
Member

senny commented Apr 28, 2015

@axilleas feel free to use multiline-commit messages.

update instructions to build guides locally [ci skip]

  1.
  2.
  3. 

@fxn
Copy link
Member

fxn commented Apr 28, 2015

Good! Question, are you "into" a directory?

@axilleas
Copy link
Contributor Author

@senny amended commit to match your recomendation.

@fxn actually I kinda copy-pasted from https://github.com/rails/rails/blob/master/guides/source/ruby_on_rails_guides_guidelines.md#generation 😄

@fxn
Copy link
Member

fxn commented Apr 28, 2015

@axilleas yeah, you can "cd into", but "be into"... not sure about that one :).

@@ -16,7 +16,8 @@ RDoc
----

The [Rails API documentation](http://api.rubyonrails.org) is generated with
[RDoc](http://docs.seattlerb.org/rdoc/).
[RDoc](http://docs.seattlerb.org/rdoc/). To generate it, make sure you are
into the `rails` root directory, run `bundle install` and execute:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm with @fxn. into feels off here.

make sure you are in the rails root directory.

@axilleas
Copy link
Contributor Author

Ah I see what you mean, updated. And yeah "be into" has a different meaning.

@@ -16,7 +16,8 @@ RDoc
----

The [Rails API documentation](http://api.rubyonrails.org) is generated with
[RDoc](http://docs.seattlerb.org/rdoc/).
[RDoc](http://docs.seattlerb.org/rdoc/). To generate it, make sure you are
in the `rails` root directory, run `bundle install` and execute:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

probably better not to quote rails.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fair enough. I took it from the generation section of the HTML Guides where guides as a dir is also quoted ;)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea but guides/ is an actual dir, while rails just refers to the folder you cloned rails into. We can't really know what it's called. Hence I see "the rails root directory" as the thing we are pointing to, not the directory rails/.

1. Make clear where rake rdoc is executed
2. Make clear where the generated HTML files for the guides are stored
3. Use bundler 1.3.5 or later
senny added a commit that referenced this pull request Apr 28, 2015
Make sure you execute rake rdoc from rails root directory [ci skip]
@senny senny merged commit 6ccf3bf into rails:master Apr 28, 2015
@senny
Copy link
Member

senny commented Apr 28, 2015

@axilleas thank you for your contribution.

@axilleas
Copy link
Contributor Author

Thank you for your time and support :)

@axilleas axilleas deleted the api_docs_guidelines branch April 28, 2015 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants