= GitHub Migration FAQ = [[PageOutline(2-4,,inline)]] == Why == See [https://lists.macports.org/pipermail/macports-dev/2016-August/033405.html Ryan's announcement email]. == Git == #git === How can I sync my ports tree using Git? === #portstree See the [[howto/SyncingWithGit|"Syncing with Git" HOWTO]]. === I have never used Git! How do I start? === #gitnewbie See [[WorkingWithGit]]. == GitHub == #github === Where can I find the MacPorts source now? === #repositories We have split our monolithic [[span(Mac OS, style=white-space: nowrap)]] Forge repository into smaller GitHub repositories. ||= 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-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. The tools and [https://techbase.kde.org/Projects/MoveToGit/UsingSvn2Git svn2git] rules used for the conversion are available in [https://github.com/macports/macports-svn2git-rules their own repository]. === How do I get commit privileges for the repositories on GitHub? === #commitbit Push access to our primary repositories is restricted to members of [https://github.com/orgs/macports/teams/developers our developers team on GitHub]. - If you are not a MacPorts developer, [https://guide.macports.org/chunked/project.membership.html apply to become one]. - If you are already a MacPorts developer but are not on the developers team, send the following email to [mailto:macports-infra@lists.macports.org?subject=Please%20invite%20me%20to%20MacPorts%20on%20GitHub&body=Handle:%20 macports-infra@lists.macports.org]: {{{ Subject: Please invite me to MacPorts on GitHub Handle: }}} Your `@macports.org` email address will soon receive a invitation to our GitHub organization and the developers team. Finally, add your GitHub username to the [[MacPortsDevelopers|list of developers]]. If you still cannot push, contact macports-infra@lists.macports.org. Note that push access to certain minor repositories is restricted to the [https://github.com/orgs/macports/teams/infrastructure infrastructure team], but you may submit pull requests as usual. === What happened to my user repository? === #userrepositories Each directory `users/USER` in the Mac OS Forge repository has been migrated to a separate GitHub repository called `macports-user-USER`. If one of these repositories is yours, we encourage you to take custody of it. 1. Find your repository in [https://github.com/macports our GitHub organization]. If you can't locate yours, try entering your MacPorts handle into the search box immediately above the repository list. 1. [https://help.github.com/articles/fork-a-repo Fork it] to your personal GitHub account. 1. Inform macports-infra@lists.macports.org that you have forked your repository. An organization owner will soon delete the original, [https://help.github.com/articles/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility/#deleting-a-public-repository leaving your fork as the canonical repository]. If you don't consider your repository worth saving, you can skip the forking and simply request deletion. == Trac == #trac === How can I associate my old tickets with my new Trac account? === #oldtickets Your account on our new Trac site inherits reporter/owner/Cc status for the email addresses in your GitHub account. If you notice that some of your tickets or Cc's have not been migrated, you should [https://help.github.com/articles/adding-an-email-address-to-your-github-account add the relevant email address(es) to your GitHub account] and log out of Trac. Shortly after you log back in, a periodic job will notice the newly added email addresses and perform the migration. === I was able to edit tickets on the old Trac. Why can’t I do so on the new one? === #ticketprivileges Ticket editing privileges are restricted to members of [https://github.com/orgs/macports/teams/developers our developers team on GitHub]. To join, follow the [[#commitbit|instructions for gaining push access]]. === How exactly do Trac and GitHub integrate with one another? === #tracgithubplugin The MacPorts Trac and GitHub are connected to one another via the trac-github plugin, whose sources can be found in the following repo: [https://github.com/trac-hacks/trac-github https://github.com/trac-hacks/trac-github]