latest 14 messages by iwo
+
[2015-03-02T22:30:10Z]
iwo
then: git push origin AA-watch
+
[2015-03-02T22:29:50Z]
iwo
you can easily create a branch that matches upstream master like: git checkout upstream/master; git checkout -b AA-watch
+
[2015-03-02T22:29:18Z]
iwo
i'd add two remotes, your fork as 'origin' and the original repo as 'upstream'
+
[2015-03-02T22:24:38Z]
iwo
t4nk402: so you want to have your own fork where 'master' contains extra commits from you, but you have an additional branch that matches AA master?
+
[2015-03-02T22:14:27Z]
iwo
but full page loads that have a fragment identifier don't jump to the right place
+
[2015-03-02T22:13:34Z]
iwo
once the page has loaded, clicking heading links works correctly (scrolls to the right position)
+
[2015-03-02T22:13:15Z]
iwo
it looks like it's something to do with the dynamically loaded content
+
[2015-03-02T22:13:03Z]
iwo
URLs with fragments for linking into pages no longer work correctly: https://github.com/clojure-emacs/cider#keyboard-shortcuts
+
[2015-03-02T22:11:11Z]
iwo
hey, is there a good repo somewhere on https://github.com/github for raising problems with the github site itself?
+
[2014-11-29T21:17:43Z]
iwo
ah, looks like it was just paging that was causing the milestone to not appear :)
+
[2014-11-29T21:08:44Z]
iwo
I guess there's some eventual consistency around milestones but 45 minutes seems a long wait :\
+
[2014-11-29T21:08:18Z]
iwo
I can see it when I use /milestones?state=closed on github.com (UI) but not when I make the same request to api.github.com
+
[2014-11-29T21:07:04Z]
iwo
I closed a milestone about 45 minutes ago and I stil don't see it when I GET /milestones?state=closed
+
[2014-11-29T21:06:26Z]
iwo
hey, does anyone know how long it takes for milestone changes to be reflected in github API responses?