Open hermands opened 9 years ago
What ever is easiest, replicating issues would be fine, some can be closed soon anyways.
What is proposed policy? When is the implementation date?
On Tue, Dec 16, 2014 at 4:46 PM, Daniel Herman notifications@github.com wrote:
Need to move so that meet proposed policy for labmed IT.
I have noticed some repositories designed to capture issues/history from github to transfer to bitbucket --> it could be worth looking at this briefly. If challenging, we would probably be fine just replicating active issues.
— Reply to this email directly or view it on GitHub https://github.com/davidpng/FCS_Database/issues/21.
I can show policy, but it is basically a procedure to ensure no PHI+ is uploaded. And apparently all works developed on labmed time should by definition be on bitbucket>uwlabmed
ok, sure thing then we can more easily load more test files.
On Tue, Dec 16, 2014 at 5:14 PM, Daniel Herman notifications@github.com wrote:
I can show policy, but it is basically a procedure to ensure no PHI+ is uploaded. And apparently all works developed on labmed time should by definition be on bitbucket>uwlabmed
— Reply to this email directly or view it on GitHub https://github.com/davidpng/FCS_Database/issues/21#issuecomment-67262735 .
Take a look at issue transfer --> ? https://github.com/mercomp/github-to-bitbucket-issues-migration ?
Need to move so that meet proposed policy for labmed IT.
I have noticed some repositories designed to capture issues/history from github to transfer to bitbucket --> it could be worth looking at this briefly. If challenging, we would probably be fine just replicating active issues.