GitLab × AmbactiBring GitLab into
the flow of work.
A little less busywork with GitLab.
File5 capabilities+
- Get a fileRead
Get the data of a single file
- List filesRead
List contents of a folder
- Create a fileWrite
Create a new file in repository
- Delete a fileWrite
Delete a file in repository
- Edit a fileWrite
Edit a file in repository
Issue5 capabilities+
- Get an issueRead
Get the data of a single issue
- Create a comment on an issueWrite
Create a new comment on an issue
- Create an issueWrite
Create a new issue
- Edit an issueWrite
- Lock an issueWrite
Release5 capabilities+
- Get many releasesRead
- Get a releaseRead
- Create a releaseWrite
Create a new release
- Delete a releaseWrite
- Update a releaseWrite
Repository2 capabilities+
- Get issues of a repositoryRead
Returns issues of a repository
- Get a repositoryRead
Get the data of a single repository
User1 capabilities+
- Get a user's repositoriesRead
Returns the repositories of a user
Update events13 capabilities+
- *Event
- CommentEvent
- Confidential CommentsEvent
- Confidential IssuesEvent
- DeploymentsEvent
- IssueEvent
- JobEvent
- Merge RequestEvent
- PipelineEvent
- PushEvent
- ReleaseEvent
- TagEvent
- Wiki PageEvent
Frequently asked
questions.
What could an Ambacti integration do with GitLab?
The documented operations include File: Get a file; File: List files; Issue: Get an issue; Release: Get many releases.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in GitLab?
Decide which work could run on its own and which steps need your review.