| Version 14 (modified by larryv (Lawrence Velázquez), 7 years ago) (diff) |
|---|
GitHub Migration FAQ
Why
See Ryan's announcement email.
Git
How can I use Git for my ports tree?
See the "Syncing with Git" HOWTO.
I have never used Git! How do I start?
See WorkingWithGit.
GitHub
Where can I find the MacPorts source now?
As part of the migration, we have split our monolithic Mac OS Forge repository into smaller repositories on GitHub. The svn2git rules used for the conversion are available on Clemens Lang's GitHub.
| Mac OS Forge | GitHub ("master" branch unless otherwise noted) |
|---|---|
| trunk/base | macports-base.git |
| trunk/base/portmgr/jobs | macports-infrastructure.git, "jobs" directory |
| trunk/doc | macports-guide.git, "doc-old" branch |
| trunk/doc-new | macports-guide.git |
| trunk/dports | macports-ports.git |
| trunk/dports/PortIndex* | deleted |
| trunk/www | macports-www.git |
| contrib | macports-contrib.git |
| contrib/MacPorts_Framework | pallet.git, "MacPorts_Framework" directory |
| contrib/Pallet | pallet.git, "Pallet" directory |
| contrib/buildbot | macports-infrastructure.git, "buildbot-mpab" branch, "buildbot" directory |
| contrib/buildbot-test | macports-infrastructure.git, "buildbot" directory |
| contrib/mp-buildbot | mpbb.git |
| contrib/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 |
Cloning URLs and GitHub Desktop links are available on each repository's GitHub page.
How do I get commit privileges for the repositories on GitHub?
Push access to our primary repositories is restricted to members of our developers team on GitHub.
- If you are not a MacPorts developer, apply to become one.
- If you are already a MacPorts developer but are not on the developers team, send the following email to macports-infra@…:
Subject: Please invite me to MacPorts on GitHub Handle: <your-macports-handle>
Your<your-macports-handle>@macports.orgemail address will soon receive a invitation to our GitHub organization and the developers team.
Finally, add your GitHub username to the list of developers.
If you still cannot push, contact macports-infra@…. Note that push access to certain minor repositories is restricted to the infrastructure team, but you may submit pull requests as usual.
What happened to my user repository?
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.
- Find your repository in our GitHub organization. If you can't locate yours, try entering your MacPorts handle into the search box immediately above the repository list.
- Fork it to your personal GitHub account.
- Inform macports-infra@… that you have forked your repository. An organization owner will soon delete the original, 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
How can I associate my old tickets with my new Trac account?
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 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?
Ticket editing privileges are restricted to members of our developers team on GitHub. To join, follow the instructions for gaining push access.