Adding a Workflow to a Repository

Now that the iCR CI/CD container is properly registered for this User, we can link it with any of the repositories for which we desire a CI/CD workflow to be triggered. Click on the package name to link it with a project. In our example, that is icr-github. That brings up this window:

which presents up a popup menu where you can select which repositories you wish this container to be linked with. Keeping with our earlier example, we will associate CI/CD workflow capability to the sample project baritone. Select it along with any other repositories that you wish to be linked to this package.

Then click on the Connect Repository button at the bottom of the popup menu to link all selected repositories to this package.

With our example project linked to the package, the next step is to configure each spcific repository to allow GitHub Actions on its behalf. To do that, click on the Package Settings menu item in the updated display of the registered repository as illustrated below.

To permit GitHub Actions to work with this repository, access must be authorized. From this Package Settings page, scroll to the section titled Manage Actions access where there is a button labeled Add repository.

Clicking on it will, like earlier, display all of the repositories available to the logged-in user. From that list click the repository for which you wish to grant access. In our example, that is the Baritone repository so we click on its radio button. That adds Baritone to the list of repositories allowed to use GitHub actions with this package.

With our example project registered with the iCR package and the package now authorized to access GitHub Actions on behalf of our example repository, we can move to the steps to invoke a GitHub Actions workflow.