Developer · 2 pre-built actions
GitHub integration with Nexus
Start governed work from GitHub events. GitHub events start runs directly. Pre-built actions search repositories and read check errors, and the GitHub API covers anything else.
Pre-built actions
What you can automate
2 pre-built GitHub actions, grouped by what they work on.
2
PRE-BUILT ACTIONS
- 01Search a GitHub repository from a workflow step.
- 02Read check errors to decide what happens next.
- 03Other GitHub operations use the GitHub API in the same workflow.
Workflow
How it fits into a Nexus workflow
GitHub is a trigger source in Nexus. An event can start a governed run directly, and GitHub steps then run as pre-built actions in the same workflow.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the GitHub API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Failed checks to an issue
Check errors are read and a Jira issue is opened with the details.
Release events to change records
A GitHub event opens a ServiceNow change for review.
Repository lookups in runbooks
A runbook searches repositories for the configuration it needs.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use GitHub
Defense & national security
Configuration change across controlled environments
Configuration changes deploy only after approval, with checks and deployment events tied to the change record.
Critical infrastructure
Deployment governance
Every deployment links to an approved change, passing checks and a deployment event.
FAQ
GitHub connector questions
- Which GitHub actions are pre-built?
- Nexus includes 2 pre-built GitHub actions across Repository search (1) and Check errors (1).
- Can GitHub start a workflow?
- Yes. GitHub is a trigger source, so an event can start a run directly.
- What if the operation I need is not pre-built?
- Use the GitHub API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Jira connector
Engineering issues and projects.
- ServiceNow connector
Incidents, changes and CMDB.
- Code and extensibility
Multi-language code nodes in the same workflow.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how GitHub fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.