Add sub page navigation to translations of "Ruby in 20 minutes" about www.ruby-lang.org HOT 5 CLOSED

Closed with 72af34d.

from www.ruby-lang.org.

@stomar A very neat feature of Github is the ability to auto-close issues from commit messages: https://github.com/blog/1386-closing-issues-via-commit-messages

It encourages you to work on a topic branch and, once you gained positive feedback, merge it on master (where the auto-closing of issue occurs). That's why I worked using PR (but I forgot to use the proper syntax to close related issues :p)

from www.ruby-lang.org.

I know, but I don't like coupling of git commit messages to GitHub issues too much. I also prefer rebasing my topic branches and fast forwarding over merging of pull requests.

from www.ruby-lang.org.

Ok. Actually I kind of do the same: rebasing master onto topic branches, then fast-forwarding on master. I like opening a PR on Github though, as it gives an opportunity to discuss the diff and the "request" it backs. I just don't use their merge button to close the PR. That explains why I did not use the "Fixes #XYZ" trick on my PR, then ;)

from www.ruby-lang.org.

Granted, if feedback is needed. Regarding your current pull requests, the diffs itself are no-brainers, the only question is whether the changes should be made or not. (For an essentially unmaintained site, pointing to the English feed might be a good idea.)

from www.ruby-lang.org.