+[2016-07-08T15:35:16Z]Dougie187Yes, github doesn't do that though +[2016-07-08T15:35:25Z]Dougie187You have to try to merge by hand and that will tell you what they are +[2016-07-08T15:35:46Z]Dougie187You can figure out what the merge conflicts are without having write access +[2016-07-08T15:51:03Z]patarrYou know how when you "fork" a repo, the repo has a little hyperlink indicating where it was forked from? What happens when a company has been working on a fork for so long, it essentially becomes a different product. Is there a way to remove this link? +[2016-07-08T15:52:40Z]sveinsepatarr: git remote rm origin
message no. 142305
Posted by abhvl in #github at 2016-07-08T10:13:11Z
hi
+[2016-07-09T02:03:56Z]amingoiaIs there a way to display some sort of notice on the "New Issue" page? +[2016-07-09T03:01:18Z]GeoHi! one of our brilliant co-devs, several dozen commits back, somehow managed to only merge the 'ChangeLog' file in about a dozen PRs (via GitHub). I assume the local branches have since been deleted; is there someway to go back and resubmit those PRs via GitHub, when I'm not the originator? I have the original commit SHA of the originator, just not sure if I can re-do it on their behalf +[2016-07-09T09:34:42Z]averageif I delete a github fork after a pull-request is created, and just leave the pull-request open, will the upstream still be able to merge the pull-request ? +[2016-07-09T09:47:59Z]Zarthus!crosspost +[2016-07-09T09:47:59Z]gitinfoNote: The above question was posted in both #git and #github