https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INFRA-173 Software Development Infrastructure <p>There are several request to put external (e.g. collaborator personal) repository at github into subaru-pfs github organization. It is better to seek 'easy' way to perform it and add as a procedure in operation document.</p> <p>For now, it seems we can take two options:</p> <ul> <li>transfer existing repository to one of organization admin, and admin will do all after that</li> <li>temporary assign some permission level to whom want to transfer repository, and ask them to do, and revert permission</li> </ul> <p>Considering number of interactions and security, it would be better to take first option.</p> INFRA-173

Add a procedure to accpet external repository into subaru_pfs organization

Task Normal Won't Fix Won't Fix shimono shimono Fri, 30 Mar 2018 05:01:29 +0000 Thu, 17 Jan 2019 17:25:05 +0000 Thu, 17 Jan 2019 17:25:05 +0000 web 0 1 <p>Why not use the standard github method? You create an empty Subaru-PFS repo, the other person adds that as a remote and pushes to it. Done. That also has the advantage of working with non-github repos.</p> <p>if you already have a repo in github, 'transfer' is the standard way in github.</p> <p>The way GitHub puts it, you can: "Transfer this repository to another user or to an organization where you have the ability to create repositories.". I don't have that ability, so the one-step method does not work. OK.</p> <p>We have previously, many times, used a <b>two-step</b> method: a Subaru-PFS admin creates the repo and the requesting user pushes to that new remote. When you create a GitHub repository, that is one of the cut-and-pasteable recommendations they immediately suggest. This method also works for non-github repos, as has been needed several times.</p> <p>I understand that some users might not actually use raw <tt>git</tt>, in which case you might need a more complicated scheme. But I don't know of any in this project.</p> <p>I want to state just one point, if you already have repository on github, we are better to complete all within github not to miss or lose any additional or attached information but not in the git tree itself. So, that's why I am proposing in this ticket.</p> <p>We have since settled on letting the developer push to a new repo. Direct.</p> Development Rank 0|ii042f: