= GitHub Migration FAQ = [[PageOutline(2-4,,inline)]] == Git == #git === How can I use Git for my ports tree? === #portstree See the [[howto/SyncingWithGit|"Syncing with Git" HOWTO]]. == GitHub == #github === Where can I find the MacPorts source now? === #repositories As part of the migration, we have split our monolithic Mac OS Forge repository into smaller repositories on GitHub. The [https://techbase.kde.org/Projects/MoveToGit/UsingSvn2Git svn2git] rules used for the conversion are available on [https://github.com/neverpanic/macports-svn2git-rules/blob/master/gitconversion.rules Clemens Lang's GitHub]. ||= Mac OS Forge =||= GitHub ("master" branch unless otherwise noted) || trunk/base || [https://github.com/macports/macports-base macports-base.git] || trunk/base/portmgr/jobs || [https://github.com/macports/macports-infrastructure/tree/master/jobs macports-infrastructure.git, "jobs" directory] || trunk/doc || [https://github.com/macports/macports-guide/tree/doc-old macports-guide.git, "doc-old" branch] || trunk/doc-new || [https://github.com/macports/macports-guide macports-guide.git] || trunk/dports || [https://github.com/macports/macports-ports macports-ports.git] || trunk/dports/PortIndex* || //deleted// || trunk/www || [https://github.com/macports/macports-www macports-www.git] || contrib || [https://github.com/macports/macports-contrib macports-contrib.git] || contrib/MacPorts_Framework || [https://github.com/macports/pallet/tree/master/MacPorts_Framework pallet.git, "MacPorts_Framework" directory] || contrib/Pallet || [https://github.com/macports/pallet/tree/master/Pallet pallet.git, "Pallet" directory] || contrib/buildbot || [https://github.com/macports/macports-infrastructure/tree/buildbot-mpab/buildbot macports-infrastructure.git, "buildbot-mpab" branch, "buildbot" directory] || contrib/buildbot-test || [https://github.com/macports/macports-infrastructure/tree/master/buildbot macports-infrastructure.git, "buildbot" directory] || contrib/mp-buildbot || [https://github.com/macports/mpbb mpbb.git] || contrib/mpab || [https://github.com/macports/mpbb/tree/mpab mpbb.git, "mpab" branch] || users/* || //separate repository at macports/macports-user-*.git// || users/{dluke,jberry,pipping} || //deleted (exceeds GitHub size limit, only contains old files)// || branches/* || //branch of the appropriate repository// || distfiles/* || //deleted// || downloads/* || //deleted// || tags/* || //annotated tag in the appropriate repository// [https://help.github.com/articles/cloning-a-repository Cloning URLs and GitHub Desktop links] are available on each repository's GitHub page. === I am a MacPorts developer. How do I join the MacPorts organization on GitHub? === #joining In order to get commit access to the Git repositories, you will have to join the MacPorts organization on GitHub. To do that, send the following email to macports-infra@lists.macports.org: {{{ Subject: Please invite me to MacPorts on GitHub Handle: }}} The infrastructure team will send an invite to join the MacPorts organization on GitHub to your MacPorts email address. Follow the steps in this invitation email to get commit access to the MacPorts Git repositories. Please add your GitHub username to the MacPortsDevelopers page after finishing this process. == Trac == #trac === How can I associate my old tickets with my new Trac account? === #oldtickets When you log into the new Trac site, references to your GitHub email addresses are converted to your new Trac account. Thus, your new account only inherits reporter/owner/Cc status for email addresses you've added to GitHub. If you forgot about an address you used on the old Trac site, you can [https://help.github.com/articles/adding-an-email-address-to-your-github-account add it to GitHub] at any time, log out of Trac, and log back in. The conversion is done by a periodic job, so it may not occur for a few minutes after login.