Bug #86973 for Perl-Critic: Migrate from svn to github

Andreas, if you give me your github id I'll add you to the organization: https://github.com/organizations/Perl-Critic Jeff, what were your plans re the two repos Perl-Critic and Perl-Critic-Core?

Andreas, you're a member of https://github.com/Perl-Critic now. I've created a repo at git@github.com:Perl-Critic/perl-critic.git Feel free to push when you've got a migration that meets Jeff's requirements. Thanks!

On Wed Jul 17 05:33:33 2013, ANDREMAR wrote: Show quoted text
Welcome to the wonderful world of subversion to git conversions! Graham Knop aka HAARG, who converted the DBIC repo, has gotten a better conversion than mine going, in part based on my work, though not much. Here is the web url: http://git.haarg.org/gknop/Test-Perl-Critic.git, and here is the url you can clone and look at locally: git://git.haarg.org/gknop/Perl-Critic As far as I can tell this is complete.

On Sat Jul 20 07:33:38 2013, haarg wrote: Show quoted text
They both look great! There is one gotcha though: Most (maybe all) of the Perl-Critic-* distributions share a common Module::Build base class. We used an svn:external link to a directory located here: http://perlcritic.tigris.org/svn/perlcritic/trunk/distributions/common/inc/Perl/Critic/Module/Build Would it be possible to use a git submodule for that too? If not I can just live with duplicating the file in each repo. I won't be the end of the world. It looks like there will be some yak shaving to do before I can make a release from the new repo, but it won't be bad. And it will give me an excuse to set up Dist::Zilla here. The only projects to move at this time are Perl-Critic, Test-Perl-Critic, Test-Perl-Critic-Progressive, Perl-Critic-More, Perl-Critic-Dynamic, Perl-Critic-StricterSubs, criticism, and perlcritic.com. The others mostly belong to Elliot and I'm not sure he's ready to move (he's not a big fan of git). But you've already done so much -- don't feel pressured to do all those. I'll be completely stoked if we only get Perl-Critic moved! Thanks everyone for making this happen :)

Should we push the latest Perl-Critic and Test-Perl-Critic to github as they are now, and fix the Module::Build base-class problem later?

I get a `access denied` when I try to clone Test-Perl-Critic: $ git clone git://git.haarg.org/gknop/Test-Perl-Critic.git test-perl-critic Cloning into 'test-perl-critic'... fatal: remote error: access denied or repository not exported: /gknop/Test-Perl-Critic.git In addition, I get a permission denied error when trying to push to the perl-critic.git repo created on github: $ git push --all -u origin ERROR: Permission to Perl-Critic/perl-critic.git denied to omega. fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. Maybe I am not in a team with the correct permissions in the organization?

Show quoted text
I find using git subtree[*] _much_ more pleasant to work with that git submodules, which are fraught with traps for the unwary. Tim. [*] http://git-scm.com/book/en/Git-Tools-Subtree-Merging Here are a couple of random blog posts google found about it: http://blogs.atlassian.com/2013/05/alternatives-to-git-submodule-git-subtree/ http://psionides.eu/2010/02/04/sharing-code-between-projects-with-git-subtree/

On Mon Jul 22 01:25:19 2013, ANDREMAR wrote: Show quoted text
I've fixed the permissions, so this should be clonable now.

Ok, I pushed * https://github.com/Perl-Critic/Test-Perl-Critic * https://github.com/Perl-Critic/Perl-Critic Please let me know if anything looks askew or wrong I don't know why https://github.com/Perl-Critic/Test-Perl-Critic/releases has the dates confused, but when I look at my clone, the tags look correct and the SHAs seem to be the same