Github integration for AI agents
Browse repos, manage issues and PRs, and search code
Connect Github to Langdock and use it in chat, in agents and in workflows.
31 actions · 10 triggers
Github actions
Each action is one step an agent or workflow can run in Github.
- Change file
Creates a new file or updates an existing file in a repository. For new files, provide the path and content. For existing files, also provide the current file SHA (from get_file_content or get_repository_content) to update it.
- Change workflow file
Creates or updates a GitHub Actions workflow file in a repository's .github/workflows folder. For a new workflow, provide its file name and content. For an existing one, also provide the current file SHA (from get_file_content or get_repository_content). Use change_file for any file outside .github/workflows
- Compare
Compares two branches, tags, or commits and shows the diff. Returns commits, changed files with patches, and stats. Use for release diffs, PR previews, or any ref comparison.
- Create branch
Creates a new branch in a repository from an existing branch.
- Create issue
Creates an issue for a specified repository.
- Create issue comment
Creates a comment on a specified issue.
- Create pull request
Creates a GitHub pull request from an already pushed branch, in the same repository or a fork. Set draft when the pull request is not ready for review. To inspect or find an existing pull request, use the get or list actions instead.
- Get branch
Retrieves detailed information about a specific branch, including protection status and latest commit.
- Get commit diff
Gets diff information for a specific commit. Returns file stats (files changed, additions, deletions) and optionally the detailed patch content for each file.
- Get current user
Retrieves the profile of the authenticated GitHub user, including login, name, email, and account statistics.
- Get file content
Retrieves the actual content of a file from a repository. Use get_repository_content first to find the file path, then use this action to read its contents.
- Get pull request
Retrieves detailed information about the specified pull request.
- Get pull request comments
Gets the comments of a given pull request.
- Get pull request commits
Gets the commits of a given pull request.
- Get pull request files
Lists files changed in a pull request.
- Get release
Retrieves detailed information about a specific release by its ID, including release notes and downloadable assets.
- Get release by tag
Retrieves detailed information about a release by its tag name (e.g., v1.0.0). More intuitive than ID lookup when the tag is known.
- Get repository content
Lists files and directories in a repository path. Use this to browse the structure of a repository before retrieving specific files. Set Recursive to Yes to include every nested file and folder under the path.
- Get workflow logs
Gets a GitHub Actions job's status and log output. Use it to find out why a job or a workflow run failed: it returns the failed steps, the job's error annotations, and the log lines leading up to the last error. Pass a job ID or job URL, or a run ID or run URL to read the run's first failed job.
- List branches
Lists all branches in a repository. Useful for branch selection in workflows or checking available branches before operations.
- List issues
Lists all issues in a given repository.
- List pending deployments
Gets the deployments of a GitHub Actions workflow run that are waiting for review: the environment and its ID, whether the connected user can approve it, the environment's wait timer and its required reviewers. Use it to check who has to approve before calling 'Review deployments', or to pick single environments to review.
- List pull requests
Lists all pull requests in a repository.
- List releases
Lists all releases in a repository. Useful for changelog automation, docs sync, and tracking deployments.
- List repositories
Lists repositories accessible to the authenticated user.
- List workflow runs
Lists the most recent GitHub Actions workflow runs of a repository, newest first, optionally for one workflow, a status and a creation date range. Returns each run's status, conclusion, branch, actor and timestamps, enough to report the last run, success rate or run durations. To find runs waiting for a deployment approval, set Status to 'Waiting' and use 'List pending deployments' or 'Review deployments' on a returned run. To find out why a run failed, pass its ID to 'Get workflow logs'.
- List workflows
Lists the GitHub Actions workflows of a repository with their names, IDs, file paths and whether they are active or disabled. Use it to find the workflow file name or ID that other workflow actions expect.
- Review deployments
Approves or rejects deployments of a GitHub Actions workflow run that are waiting for review. Without environment IDs it reviews every waiting environment the connected user can review; pass environment IDs from 'List pending deployments' to review only some. Approving lets the run deploy to those environments; rejecting fails the run. Returns the reviewed deployments with their environments.
- Run workflow
Starts a GitHub Actions workflow that can be run manually (it has a workflow_dispatch trigger) on a branch or tag, with optional inputs. Returns the new run's ID and URL; the run itself continues on GitHub.
- Search code
Searches for code and files across GitHub repositories. Use 'filename' to find files by name (e.g., schema.prisma, package.json). Use 'query' to search for text INSIDE file contents. You can combine both. Always specify owner and repository when searching within a specific repo for best results.
- Update issue
Updates a specified issue.
Github triggers
A trigger starts a workflow when something happens in Github.
- Changes in path
Triggers when files are added or modified in a specific path. Useful for CI/CD pipelines, config monitoring, code review automation, or content tracking.
- Monitor deployments
Monitor deployment creation and status changes in a GitHub repository. Filter by environment, branch or tag, and deployment status. Each subscriber’s deployment access is checked before delivery. Creating the shared webhook requires repository administrator access.
- Monitor pull request
Monitor pull request changes, comments, reviews, review threads, and CI results. Each subscriber’s GitHub access is checked before delivery. Creating the shared repository webhook requires repository administrator access.
- New commit
Triggers when new commits are pushed to a specific branch.
- New issue
Triggers when a new issue is created in the repository. Does not trigger for pull requests.
- New issue comment
Triggers when a new comment is added to an issue in the repository.
- New pull request
Triggers when a new pull request is opened in the repository.
- New pull request comment
Triggers when a new comment is added to a pull request in the repository.
- New release
Triggers when a new release is published in the repository.
- Pull request merged
Triggers when a pull request is merged in the repository.
Setup and permissions
An action can ask for your confirmation before it runs. In an agent, each action is set to “Always allow” or “Needs approval”.