opp-repl-github-actions

You can trigger GitHub Actions workflows from a REPL by dispatching workflow_dispatch events to your CI pipelines. This allows on-demand execution of single or all workflows during development, testing, or release cycles without leaving the interactive environment.

workflow_dispatch is a GitHub Actions event type that manually triggers CI pipelines on demand. You need it during development, testing, or release cycles when you want to run specific workflows outside of automatic triggers like pushes or pull requests.

Yes, you need a personal access token stored at ~/.ssh/github_repo_token with repo and workflow scopes. This token authorizes the workflow_dispatch operations required to trigger your GitHub Actions CI pipelines.

Yes, you can configure project-specific workflows using .opp fields like github_owner, github_repository, and github_workflows. This enables targeted triggering of single or multiple workflows tailored to your project's CI setup.

You can dispatch multiple GitHub Actions workflows at once by calling dispatch_workflow with your project configuration. Using .opp fields to define github_workflows, you can trigger all configured workflows simultaneously during release cycles.

workflow_dispatch triggers fail when the personal access token at ~/.ssh/github_repo_token lacks the required repo and workflow scopes. Ensure the token has proper authorization and the github extra dependency is installed to execute the operations successfully.