Talk:GitHub Pull Requests

git+ssh://
Some link for an explanation (maybe in a subarticle) about authenticity of host would be nice:

--Charles17 (talk) 09:06, 2 December 2017 (UTC)


 * According to this forum topic, the git+ssh:// protocol can be used only by Gentoo developers, not by end users. --Charles17 (talk) 17:02, 4 December 2017 (UTC)


 * Yes and no. This picture explains it better. Only the developer with write access to the tree writes to git.gentoo.org. The user may do what he/she wants on the github fork. https://wiki.gentoo.org/wiki/File:Github_pull_request.png Please comment on the new picture. We can improve it and then cut it into sections for this article. I think it fits better than the current illustration. --Jonas Stein (talk) 23:40, 13 December 2017 (UTC)


 * Thanks for the nice picture. My question was related to this version where you said User configures the local repository using that certain command. git clone -o upstream git+ssh://git@git.gentoo.org/repo/gentoo.git.  Did you mean to say ordinary users could use git+ssh://github.com but not git+ssh://git.gentoo.org?--Charles17 (talk) 07:08, 14 December 2017 (UTC)


 * You can use git+ssh on your fork of the gentoo/gentoo repository on GitHub, but usually not on the gentoo/gentoo repository directly. Waebbl (talk) 12:45, 14 December 2017 (UTC)


 * In my opinion the new picture illustrates the process very well. I would propose to either put Alice to the right of the picture, or split it into two pictures, one for each role. Waebbl (talk) 12:45, 14 December 2017 (UTC)

github as main portage tree
Step 0 variant b doesn't actually lead to a working main portage tree since it lacks metadata, e.g. eix considers the repo to be empty then. Maybe there's some more steps needed to make this work? But as-is this is leads to a flawed setup that is not fully functional. If this is not working reliably, it might be better to just recommend using two repositories. Could people comment?