Skip to content

Conductor: add link to the GitHub Action #122

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 25, 2025
Merged

Conductor: add link to the GitHub Action #122

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion docs/conductor/getting-started.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,8 @@ To get started, click on the configure link displayed next to the package which

### GitHub Actions

Create a new GitHub Actions workflow in `.github/workflows/conductor.yaml` of your GitHub repository using the template below:
Create a new GitHub Actions workflow in `.github/workflows/conductor.yaml` of your GitHub repository to use the
[Conductor GitHub Action](https://github.com/packagist/conductor-github-action) with the template below:

CONDUCTOR_GITHUB_ACTIONS_WORKFLOW

Expand All @@ -38,6 +39,7 @@ If your package requires access to your Private Packagist Composer repository th
Similar to organization authentication tokens, access can be restricted to any set of packages to which any of the organization's teams has access.

Once the workflow is added to your GitHub repository, Conductor needs to verify your CI setup before you can start receiving PRs.

## Verify your CI setup

- Navigate to the "Conductor" tab in your Private Packagist organization.
Expand Down