tag:rubydoc.tenderapp.com,2010-12-26:/discussions/problems/3-github-projects-docs-return-a-404-after-forced-updateRubydoc.info: Discussion 2018-10-19T03:09:06Ztag:rubydoc.tenderapp.com,2010-12-26:Comment/45035922010-12-30T21:23:32Z2010-12-30T21:23:35ZGitHub project's docs return a 404 after forced update<div><p>I just pushed a commit that I amended a couple times with a
forced push to my GitHub repository, and now my docs on
Rubydoc.info are returning a 404. I tried to refresh the docs, but
it just hangs forever with the refresh icon spinning. Then I tried
adding the project again with the "add project" popover form but I
get "Invalid git repository or URL" even when specifying "master"
as the commit. How can I recover from this? Thank you!</p></div>Jimmytag:rubydoc.tenderapp.com,2010-12-26:Comment/45035922010-12-30T21:24:19Z2010-12-30T21:24:20ZGitHub project's docs return a 404 after forced update<div><p>Sorry, forgot to include info on the repository:</p>
<p><a href=
"https://github.com/jimmycuadra/to_lang">https://github.com/jimmycuadra/to_lang</a><br>
<a href=
"http://rubydoc.info/github/jimmycuadra/to_lang/master/frames">http://rubydoc.info/github/jimmycuadra/to_lang/master/frames</a></p></div>Jimmytag:rubydoc.tenderapp.com,2010-12-26:Comment/45035922010-12-30T21:31:24Z2010-12-30T21:31:24ZGitHub project's docs return a 404 after forced update<div><p>I've reset your project, so it should work now.</p>
<p>You probably already know (have heard) that forced pushes are
bad when other people (or entities in this case) are tracking your
repo. This is why :)</p></div>lsegaltag:rubydoc.tenderapp.com,2010-12-26:Comment/45035922010-12-30T21:48:29Z2010-12-30T21:48:30ZGitHub project's docs return a 404 after forced update<div><p>Thank you. It seems to be loading an older version of the docs
still, however. Note that it's still using the version with
blockquotes which have been replaced with pre/code tags, per our
discussion on that YARD issue earlier. I clicked the reload button
but it still showed the old docs. I never do forced pushes unless
I'm just amending a commit and it's been like 10 seconds or less,
when it's very unlikely anyone has pulled the original commit. Now
I see how even that won't work if automated systems are watching
the repository. I will avoid them entirely now. Sorry about
this.</p></div>Jimmytag:rubydoc.tenderapp.com,2010-12-26:Comment/45035922010-12-30T21:50:26Z2010-12-30T21:50:28ZGitHub project's docs return a 404 after forced update<div><p>Ugh, ignore me again. Looks like it was just browser cache.</p></div>Jimmy