GitHub Issues AirSync
To ease the transition from GitHub issues to DevRev, you can import and sync GitHub issues with DevRev.
Supported objects
Importing from GitHub
DevRev highly recommends creating a new dedicated GitHub account when setting up GitHub for 2-way sync. All issues and comments created in GitHub are done with this account.
-
Create a GitHub PAT with the account that will be used to set up the AirSync.
The minimum required permissions are READ + WRITE Issues and READ + WRITE Pull Requests.
-
Go to Settings > Integrations > Snap-ins and install GitHub Issues.
If there are any existing GitHub Issues already added, Add the other.
-
Under Settings > Integrations > Airdrops, click Start Airdrop or Airdrop.
-
Under the Snap-ins tab, select GitHub.
If this option isn't available, install the snap-in as described in step 2.
-
Follow the prompt and create a connection providing the GitHub PAT and the GitHub organization name when creating a new connection.
A recipe is presented where you select what data to import and how to map it. The recommended values are preselected.
Historical AirSyncs
To view currently running and previous AirSyncs from various sources, do the following:
- Go to Settings > Integrations > Airdrops.
- Select the import you want to view.
- Select the context menu (⋮) > View Report.
Periodic sync
After successfully importing to DevRev, you have the option to enable a periodic sync. This allows for automatic synchronization with DevRev on a regular basis. By default, the sync occurs once an hour.
To configure periodic sync, follow these steps:
- Go to Settings > Integrations > Airdrops.
- Locate the previously imported project.
- Select the ⋮ > Set Periodic Sync option.
The Enable automations for synced items setting is optional and can be activated during periodic sync configuration. When enabled, newly created or updated items trigger events, which can initiate webhooks, notifications, Snap-ins, and other processes, as if the events originated directly in DevRev.
If this setting is disabled, updates will not trigger any event-driven processes. This behavior applies only to periodic syncs; no events are triggered during a first-time import or manual sync to or from DevRev.
Delete import
This deletes any content created by the import, including users and works.
An import and all the content it creates can be deleted from DevRev. This can be useful when running POCs or to change the recipe used during the import. Once an import has been deleted, all the content it created gets deleted, even if they were modified in DevRev. It's possible to import the project again after its deletion.
To delete an import and all the content it created, go to Settings > Integrations > Airdrops, find the previously imported project, and select ⋮ > Delete Import.