+[2016-12-18T21:59:24Z]canton7But yes, every time you install software, you trust the makers not to add malicious code. On GitHub, all of the source is out in the open, and anyone can read any changes which were made. That's far better than the vast majority of software running on your machine +[2016-12-18T22:00:44Z]SwingShockYes. I understand that now. So git shows all the changes line by line ? That must be why it does not show the direct link to the repository in PR. +[2016-12-18T22:00:58Z]canton7yeah, the "changes" tab on a PR shows all of the changes in the PR +[2016-12-18T22:01:15Z]canton7I think it doesn't give you an easy link to the originating repository because there's no point: it's never needed +[2016-12-18T22:27:08Z]SwingShockThanks. Bye.
It feels very unsafe for open-source projects that way.
+[2016-12-19T00:06:30Z]rangergordhi...I have a question of etiquette. Person A creates an issue on a project, identifying a problem that's no big deal to others, but important to them. Person B sends a PR (minor change) to fix it, but the dev doesn't want to merge it because it's not the way he wants. Person B hasn't been online in the week since this happened to update the PR. Person A really wants this ASAP, is it acceptable +[2016-12-19T00:06:30Z]rangergordfor them to create a new PR on the project that applies the dev's requested changes? +[2016-12-19T00:06:59Z]rangergordIf Person A submit a PR to person B's fork, then they're left waiting for god knows how long +[2016-12-19T00:16:11Z]llamapixelIs person A in a company working with a senior dev who is Person B ? +[2016-12-19T00:17:03Z]llamapixelIs there a heirachy in this group of developers?