If you would like to fully integrate Supernova with your organization's GitHub account, you can grant Supernova access to any GitHub repository to create pull requests on your behalf. This is done by installing and authorizing the Supernova GitHub App.
If you prefer not to authorize access to a repository that contains production code, it is also possible to create a separate repository for Supernova-created data (to be used as a git submodule). This method eliminates any possibility for Supernova to access parts of the code not maintained by Supernova.
With the secure GitHub authentication, Supernova will have the following permissions:
→ Read access to metadata→ Read and write access to code and pull requests
To authorize GitHub from the Account → Profile Settings page:
To authorize GitHub from the New Build or New Hook dialog:
After your GitHub authorization is complete, you will now see a list of repositories and branches to choose from during hook or build configuration.
To revoke your GitHub authorization at any time:
The repository you selected is where the code from a hook or successful build will be exported. You can also specify a relative path to export to. The path entered is relative to the repository root, example lib/assets/DesignSystem.
When you create a new hook or build, you can optionally create pull requests in GitHub directly from Supernova.
To create a pull request in a chosen repository from a successful build:
To automatically create pull requests with a hook:
Once the new hook has been created, it will appear in your list of hooks with the Create Pull Request step added.
If you would like to stop the hook from creating pull requests, you can click Disable in the list to temporarily disable the hook, or click Remove to delete the hook completely.
This documentation was created using Supernova's fully customizable documentation engine.Start building your docs now!
© 2022 Supernova.io