The GitHub Connector allows IT teams to seamlessly integrate GitHub functionalities into your Multiplier workflows. This integration enables you to automate tasks, retrieve information, and manage your GitHub resources directly from Multiplier, including:
Organization and repository management
Project and team administration
User access control and permissions
Setup in GitHub
This connector requires a classic API Token. A GitHub admin will need to generate a new classic token
Creating a GitHub token
You can create a GitHub classic token, required to connect Multiplier with your GitHub instance, by following the steps listed below:
Log in to your GitHub instance as an administrator.
Click your avatar and select the Settings option from the side menu.
Go to Developer settings, following the link located in the left sidebar near the bottom.
Click Personal access tokens on the left sidebar and select "Tokens (classic)".
Click the "Generate new token" button and select "Generate new token (classic)".
Enter a name, duration, and enable the required scopes. You can check what scope is required for each feature in the "Required Scopes" section.
Click the "Generate token" button, and copy the generated token. You will not be able to see it again in GitHub.
Setting up the integration
To setup the integration, simply paste the token generated in the steps above, and click the "Connect to GitHub button"
Required scopes
Each action provided by the GitHub integration require a different scope. If you don't want to enable all of them, you can select the ones you need according to the actions you'll implement.
Remove user from organization:
admin:orgRemove user from team:
admin:orgAdd user to team:
admin:orgInvite user to organization:
admin:orgBlock user from organization:
admin:orgInvite collaborator to repository:
repo:inviteAdd project collaborator:
project
Portal fields
The GitHub Connector allows IT Teams to configure portal fields that seamlessly integrate with GitHub entities such as organizations, repositories, projects, and teams. These fields enable the creation of tickets that automatically initiate actions, facilitating efficient interaction with the specified GitHub resources.
Some portal fields may require additional configuration settings. For example, a repository portal field will need to have an organization selected. This ensures that the field displays repositories specific to the chosen organization.
Following the example, when creating a portal field to expose a list of repositories, you will be prompted to select the organization from which repositories come.
Note that when configuring an action that uses a portal field value that has a common dependency, its value should match.
An example of this is adding a collaborator to a repository. The portal will display a portal field to let the user select a repository, and that repository will be used by an action that requires knowing the repository and the organization. In this case, the organization should be set to the same value used by the portal field.
To learn how to add a portal field, please see Using Portal Fields to insert external data in your Jira forms.