DevOps and GitHub

The DevOps hub connects PIY Action to GitHub so teams can see what is happening in their repositories and request deployments in a controlled way.

What you can do

• Connections: an administrator connects a GitHub account or organisation by installing the PIY Action GitHub App. On GitHub, whoever installs it chooses which repositories to share. Several accounts can be connected at the same time.
• Repositories, branches and commits: browse what the connection can see.
• Pull requests: see their reviews and checks.
• GitHub Actions: see workflows, runs, jobs and, with permission, job logs.
• Run a workflow: people with the right permission can start a workflow that supports manual runs, with the inputs the workflow declares. PIY Action shows the request as requested until GitHub confirms a run; it never reports success it has not seen.
• Deployments: only to targets an administrator has set up, with the approvals and checks each target requires. You cannot approve your own request, and production deployments need their own permission.
• Audit log: administrators and people with audit access can see who did what.

What it does not do

This release is deliberately cautious. You cannot approve, merge or close pull requests, comment, re-run or cancel runs, or create and delete branches from PIY Action. It does not edit workflow files, GitHub secrets or environments, and it offers no shell or SSH access.

Good to know

• Views are snapshots; refresh to see the latest. Only deployments update themselves.
• Branch protection details appear only if the GitHub App was allowed to read them.
• Lists load up to 300 repositories.

Access

DevOps has its own permissions, given by an administrator: viewing, connecting accounts, reading logs, running workflows, configuring and requesting deployments, approving them, and reading the audit log. See Roles and permissions.