search

ruby-hacking-guide / ruby-hacking-guide.github.com

Ruby Hacking Guide Translation
http://ruby-hacking-guide.github.io/
318 stars 52 forks source link

Markdown - RE #23 #24

Closed markburns closed 10 years ago

markburns commented 11 years ago

The problem with this is as @ocha- mentioned, it replaces the contributors on GitHub with the person who renamed the file. I've just tweeted github, with the hope that they may magically fix this issue.

The API call still shows up contributions:

curl https://api.github.com/repos/ruby-hacking-guide/ruby-hacking-guide.github.com/contributors

Also there's a flag for git to follow the renames, so it must be possible.

ocha- commented 11 years ago

It's nice if GitHub can show the accurate contributors list even if we renamed files. Thank you for tweeting.

Why the converted files contain a lot of backslash \ ? https://github.com/ruby-hacking-guide/ruby-hacking-guide.github.com/blob/0a84b3f2097074086c7949bf5ad14e7d03c3736f/anyeval.textile

Maybe converting a file per a commit could be easier to review.

ocha- commented 11 years ago

If the final decision is moving to Markdown, please let me do it. I can convert the files with the least amount of changes. I think the information we can get by git-blame is also important. I'd like to make the trace of each contribution obvious, and this is also about the responsibility of each text.