Changes between Version 12 and Version 13 of FAQ/GitHubMigration
- Timestamp:
- Nov 3, 2016, 4:37:18 PM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ/GitHubMigration
v12 v13 47 47 [https://help.github.com/articles/cloning-a-repository Cloning URLs and GitHub Desktop links] are available on each repository's GitHub page. 48 48 49 === I am a MacPorts developer.How do I get commit privileges for the repositories on GitHub? === #commitbit49 === How do I get commit privileges for the repositories on GitHub? === #commitbit 50 50 51 Only members of [https://github.com/macports our GitHub organization] have push access to our repositories. To join, send the following email to [mailto:macports-infra@lists.macports.org?subject=Please%20invite%20me%20to%20MacPorts%20on%20GitHub&body=Handle:%20<your-macports-handle> macports-infra@lists.macports.org]: 52 {{{ 53 Subject: Please invite me to MacPorts on GitHub 51 Push access to our primary repositories is restricted to members of [https://github.com/orgs/macports/teams/developers our developers team on GitHub]. 52 - If you are not a MacPorts developer, [https://guide.macports.org/chunked/project.membership.html apply to become one]. 53 - 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<your-macports-handle> macports-infra@lists.macports.org]: 54 {{{ 55 Subject: Please invite me to MacPorts on GitHub 54 56 55 Handle: <your-macports-handle>56 }}}57 A member of the infrastructure team will send a GitHub invitation to `<your-macports-handle>@macports.org`. After following the invitation's instructions to join the organization, your GitHub account will have push access.57 Handle: <your-macports-handle> 58 }}} 59 Your `<your-macports-handle>@macports.org` email address will soon receive a invitation to our GitHub organization and the developers team. 58 60 59 61 Finally, add your GitHub username to the [[MacPortsDevelopers|list of developers]]. 62 63 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. 60 64 61 65 == Trac == #trac … … 65 69 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. 66 70 67 === I am a MacPorts developer and could edit tickets on the old Trac. How canI do so on the new one? === #ticketprivileges71 === I was able to edit tickets on the old Trac. Why can’t I do so on the new one? === #ticketprivileges 68 72 69 Only members of the [https://github.com/orgs/macports/teams/developers "Developers" team] within our GitHub organization can edit tickets on the new Trac site. 70 - If you are not yet a member of the organization, [#commitbit request to join]. The member of the infrastructure team who handles your request will add you to the "Developers" team. 71 - If you are already a member of the organization but still cannot edit tickets, contact macports-infra@lists.macports.org. 73 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]].