Triggers
There are multiple ways to trigger a build in Appcircle. You can run builds manually, automate the build process with various event-based triggers, or schedule builds to run automatically at times you define.
Triggers for Manual Buildsβ
For the manual builds, the currently available push triggers apply, and if no trigger is configured, the following trigger is provided by default under the push triggers. If there are others, they may take precedence based on the trigger priorities.
Triggers Configurationβ
To set up or manage the build triggers, click the Triggers button at the top right of the build profile details.
The Triggers panel is organized into tabs: On Every Push, On Merge/Pull Request, On Tag Push, and Scheduled (Beta). Event-based triggers (push, merge/pull request, and tag) are set up at the profile level, and you can specify individual branch names or utilize wildcards for branch names to trigger builds. Scheduled triggers, described in Scheduled builds, instead run at fixed times regardless of repository activity.
You also need to select a workflow for each trigger, and the build will be run with that trigger for the specified branch. You can build the same branch with different workflows (e.g., production or development), or you can use the same workflow for multiple branches (e.g., multiple feature branches built with the develop workflow).
Automatic Buildβ
Builds can be triggered with various triggers such as every push to the repository, pull/merge requests, tagged pushes, or a defined schedule. Event-based triggers (push, pull/merge request, and tag) require the following:
- Webhook connection to the repository
- Setting up build triggers
There are two options to set up webhooks for automatic builds:
- You can authorize the Appcircle app for GitHub, Bitbucket, or GitLab repositories for direct integration. The triggers will be available for use immediately. (You can skip the next part about the webhook setup.)
- For the repository connections through SSH, you can add the specific webhook for that build profile manually to the compatible git provider. This enables the Git provider to send a POST request to Appcircle for the selected events, which you can then use for triggers.
Scheduled builds do not rely on repository webhooks at all, since they are started by Appcircle itself at the times you configure. No webhook setup is required for scheduled triggers. See Scheduled builds below.
Webhook Setup by Connection Typeβ
Depending on how your Git provider is connected to Appcircle, the webhook setup may be handled automatically or may require manual configuration.
Setting Up Manual Webhooks for SSH and Public Repositoriesβ
For repositories connected through SSH, you can set up triggers with webhooks in compatible repository providers.
When you connect a repository through SSH or through a public URL, the Webhooks option will be enabled in the ... menu next to the build profile name, at the top of the profile details.
You can copy this URL and paste it in the related section in the git provider repository settings with the copy button.
To manually configure a webhook:
1. Go to your build profile.
2. Open the ... menu next to the profile name and select Webhooks.
3. In the Webhooks dialog:
-
Select a Git Provider: If the Git provider is detected, a compatible URL will be displayed automatically. If not, choose your Git provider (e.g., GitHub, GitLab, Bitbucket) from the dropdown list.
-
Copy the Webhook URL: The generated Repository Webhook URL will appear based on your Git Provider. Copy this URL and paste it into your repositoryβs webhook settings.
The URL Format:
https://api.appcircle.io/build/v1/callback/hooks/{GIT_PROVIDER}/{YOUR_ORGANIZATION_ID}/custom/{WEBHOOK_KEY}/V11
api.appcircle.io: Use your own API address for self-hosted Appcircle.{GIT_PROVIDER}: The provider you selected, such asGithub,GithubEnterprise,Gitlab,GitlabSelfHosted,Bitbucket,BitbucketServer,AzureDevopsServices, orAzureDevopsServer.{WEBHOOK_KEY}: Generated by Appcircle for the repository. All build profiles bound to this webhook receive its events.
Always copy the URL from the Webhooks dialog instead of building it by hand.
- Generate a Webhook Key: You can generate a new webhook key/secret to refresh or reset the endpointβs security token.
4. Paste the Webhook URL in your Git repository.
The Selected Git Provider option in the Webhooks dialog is only available for repositories connected via SSH or Public URL.
If your repository is connected using GitHub, GitLab, Bitbucket or Azure Devops App integrations, this selection will not appear since webhooks are automatically managed.
Azure Devops has slightly different steps to configure a manual webhook. To manually configure a webhook for an Azure DevOps repository:
- Connect your Azure DevOps repository to Appcircle and create a build profile.
- In Azure DevOps, navigate to:
Project Settings β Service Hooks β + Create Subscription - Choose Web Hooks as the service.
- Select your repository and an event. Create one subscription for each of these events: Code pushed, Pull request created, Pull request updated, Pull request merge attempted, and Pull request commented on.
- In the βActionβ step, paste the webhook URL.
- βAccept untrusted SSL certificatesβ option can stay disabled.
- Enter
appcircleas username. - Paste
{YOUR_WEBHOOK_SECRET}as password.
Binding Existing Manual Webhooks to Other Build Profilesβ
When a manual webhook (SSH/Public URL/Read-only PAT) is already configured for a repository, additional build profiles that are connected to the same repository can reuse this existing webhook configuration.
- When opening the Webhooks section of a build profile, if a manual webhook is already detected for the repository, a prompt will appear asking if you would like to bind the build profile to the existing webhook.
- Selected Git Provider, Webhook URL, and the existing Webhook Key/Secret will be displayed as partially masked.
- Users can directly click the Bind button to link the build profile to the existing webhook.
Webhook Setup for OAuth and PAT-Based Repository Connectionsβ
When a repository is connected to Appcircle via an OAuth connection (such as GitHub, GitLab, or Bitbucket) or a Personal Access Token (PAT), Appcircle tries to create the webhook automatically with the connection's credentials. Whether this succeeds depends on the role of the connected user in the repository and, for tokens, on the token's permissions. When it can't, set up a manual webhook from the Webhooks dialog.
Below is a breakdown of how webhooks are managed for each supported Git provider based on the connection method.
GitHub OAuth Connectionβ
When your repository is connected using the GitHub OAuth connection or the GitHub App, Appcircle creates the webhook automatically. The connected GitHub user must have admin access to the repository, because GitHub only lets repository admins manage webhooks. Otherwise, set up a manual webhook.
GitHub PAT and GitHub Enterprise Connectionsβ
To create a webhook automatically, Appcircle must be able to add a webhook to the repository settings. GitHub requires the Webhooks: Read and write permission (fine-grained PAT) or the write:repo_hook scope (classic PAT) for this, and the token owner must have admin access to the repository. This permission only covers the repository's webhook settings. It doesn't give write access to code or pull requests, so the Contents permission can stay read-only. If you don't want to grant webhook permissions, set up a manual webhook from the Webhooks dialog.
GitLab OAuth Connectionβ
Appcircle creates the webhook automatically when the connected GitLab user has at least the Maintainer role on the project. GitLab doesn't let lower roles manage webhooks. Otherwise, set up a manual webhook.
GitLab Cloud/Server - PAT Connectionβ
The behavior depends on the role of the PAT owner on the project:
- Maintainer or Owner role: Webhooks are created automatically. The token also needs the
apiscope. - Lower roles (Developer, Reporter, Guest): Manual webhook creation is required.
To set up a manual webhook:
- Connect the GitLab repository to Appcircle using the PAT and create a build profile.
- In GitLab, go to:
Projects β <Your Connected Repository> β Settings β Webhooks β Add Webhook - Copy the webhook URL and secret from the build profile's Webhooks dialog and paste them into GitLab. The URL has this format:
https://api.appcircle.io/build/v1/callback/hooks/{GIT_PROVIDER}/{YOUR_ORGANIZATION_ID}/custom/{WEBHOOK_KEY}/V11
- Paste the webhook secret into the Secret token field, and select the events listed in Events to Select for Manual Webhooks.
For Appcircle to create the webhook automatically, the PAT owner must have at least the Maintainer role on the project and the token must have the api scope. GitLab does not allow lower roles to manage webhooks.
Bitbucket OAuth Connectionβ
Appcircle creates the webhook automatically when the connected Bitbucket user is an admin of the repository. Bitbucket only lets repository admins create webhooks. Otherwise, set up a manual webhook.
Bitbucket Cloud Token Connectionsβ
For API tokens and access tokens, Appcircle creates the webhook automatically when the token has the read:webhook:bitbucket and write:webhook:bitbucket scopes and its owner is a repository admin. Otherwise, set up a manual webhook from the Webhooks dialog. See API Token Permissions for Bitbucket Cloud Integration.
Bitbucket Server - PAT Connectionβ
Webhook behavior is determined by the token's repository permission:
- Repository admin: The webhook is created automatically.
- Repository read or write: Manual setup is required.
To manually configure a webhook for a Bitbucket Server repository:
- Connect the Bitbucket Server repository using the token and create a build profile in Appcircle.
- In Bitbucket Server, go to:
Repositories β <Your Connected Repository> β Repository Settings β Webhooks β Create Web Hook - Copy the webhook URL and secret from the build profile's Webhooks dialog and paste them into Bitbucket Server. The URL has this format:
https://api.appcircle.io/build/v1/callback/hooks/{GIT_PROVIDER}/{YOUR_ORGANIZATION_ID}/custom/{WEBHOOK_KEY}/V11
- Select the events listed in Events to Select for Manual Webhooks.
For Appcircle to create the webhook automatically, the HTTP access token must have Repository admin permission. Bitbucket only allows repository admins to manage webhooks.
Azure Devops - PAT Connectionβ
When using the Azure DevOps PAT integration, Appcircle automatically creates the service hook subscriptions. The token owner needs the View subscriptions and Edit subscriptions permissions in the project, which only Project Administrators have by default. Otherwise, follow the manual Azure DevOps steps above.
Automatically Created Webhooksβ
When Appcircle creates a webhook in your Git provider, it uses the following settings. You can use them to find and verify the webhook in your repository settings.
- Name/description:
Appcircle/V11 - URL:
https://api.appcircle.io/build/v1/callback/hooks/{GIT_PROVIDER}/{YOUR_ORGANIZATION_ID}/{HOOK_ID}/V11. Self-hosted Appcircle uses its own API address. - Security: Each webhook has its own secret, which Appcircle checks on every request. GitHub and Bitbucket sign the payload with it (HMAC SHA-256), GitLab sends it in the
X-Gitlab-Tokenheader, and Azure DevOps uses basic authentication with usernameappcircle.
| Provider | Subscribed event | Used in Appcircle for |
|---|---|---|
| GitHub / GitHub Enterprise | push | Push and tag triggers, new commits |
create, delete | Branch list sync | |
pull_request | Pull request triggers | |
| GitLab | Push events | Push triggers, new commits, branch list sync |
| Tag push events | Tag triggers | |
| Merge request events | Merge request triggers | |
| Comments | [retry] comments (Retrying a workflow) | |
| Bitbucket Cloud | repo:push | Push and tag triggers, new commits, branch list sync |
pullrequest:created, pullrequest:updated | Pull request triggers | |
| Bitbucket Server | repo:refs_changed | Push and tag triggers, new commits, branch list sync |
repo:modified | Repository changes, not used for triggers | |
pr:opened, pr:from_ref_updated | Pull request triggers | |
| Azure DevOps | Code pushed | Push and tag triggers, new commits |
| Pull request created, Pull request updated, Pull request merge attempted | Pull request triggers | |
| Pull request commented on | [retry] comments (Retrying a workflow) |
These events are notifications that the Git provider sends to Appcircle, for example "a pull request was opened or got new commits". Subscribing to them doesn't let Appcircle change your code, branches, or pull requests.
Appcircle checks the webhook again every time the repository is refreshed and recreates it if it's missing or outdated. This needs the same webhook permissions as the first setup.
Some guides allow you to downgrade the token to read access after the webhook is created. The existing webhook keeps working, and the Webhooks option doesn't reappear. However, Appcircle can no longer verify or recreate the webhook on refresh. If the webhook is deleted in the Git provider or a new webhook version is released, you need to restore the token's admin permission or set up a manual webhook.
Events to Select for Manual Webhooksβ
When you set up a manual webhook, select the same events that Appcircle uses for automatic webhooks:
- GitHub / GitHub Enterprise: Pushes, Branch or tag creation, Branch or tag deletion, and Pull requests. Set Content type to
application/jsonand paste the webhook secret into Secret. - GitLab: Push events, Tag push events, and Merge request events. Add Comments to use
[retry]comments. - Bitbucket Cloud: Repository: Push, Pull request: Created, and Pull request: Updated.
- Bitbucket Server: Repository: Push, Repository: Modified, Pull request: Opened, and Pull request: Source branch updated.
- Azure DevOps: One service hook subscription for each of Code pushed, Pull request created, Pull request updated, Pull request merge attempted, and Pull request commented on.
To use [retry] comments on GitHub, Bitbucket Cloud, or Bitbucket Server, also select the comment event in your manual webhook: Issue comments (GitHub), Pull request: Comment created (Bitbucket Cloud), or Pull request: Comment added (Bitbucket Server).
When Appcircle Cannot Create the Webhookβ
Appcircle can't create the webhook automatically in these cases:
- The repository is connected via SSH or a public URL.
- The user connected via OAuth isn't an admin of the repository (GitHub, Bitbucket) or has a role lower than Maintainer (GitLab).
- The connection token does not have the webhook permissions described above (for example a read-only token, or a GitLab role lower than Maintainer).
- The Git server rejects or can't reach the request (for example GitLab blocks local network requests, see Outbound Requests).
The build profile is still created, but triggers won't fire until a webhook exists. You can tell this happened when the Webhooks option appears in the ... menu of the build profile and no Appcircle/V11 webhook exists in your repository settings. Set up a manual webhook from that dialog, or fix the permissions and refresh the repository so Appcircle can try again.
Please refer to the following guides to set up webhooks in various git providers:



You can also use appcircle-cli to trigger your builds from the command line as well.
Managing Triggers for Buildsβ
To set up or manage the build triggers, click the Triggers button at the top right of the build profile details.
Auto build on every pushβ
Appcircle will start building your application whenever you push a commit to your Git repository. For the specified branches, your project will be built automatically with the selected workflow.
You must choose both workflow, and a configuration when you're setting up a trigger.
Auto build pull/merge requestsβ
Appcircle will start building your application whenever you initiate a pull request or merge request from the source branch(es) to the target branch.
The build will be done with the pull/merge result using the selected workflow. This allows testing of the PR/MR result before the actual approval of the request.
Make sure that the names of the source branch and the target branch are spelled correctly.
If spaces are used in the name, Appcircle will trim it without spaces.
If you are using Azure DevOps Server or Azure DevOps Services Cloud as a Git provider, the Appcircle build trigger will not run for PR status updates (Approve, Approve with suggestions, Wait for author, Reject, etc.) or action changes (Complete, Mark as draft, Abandon).
Appcircle will only run the trigger for PR creation or PR updates.
Triggering different workflows at the same timeβ
Now you will be able to trigger different workflows in the same source branch and target branch on Appcircle at once. As soon as the trigger is triggered, Appcircle will start running all the triggered triggers in the build queue, starting from the first place in the established trigger queue.
Selective auto build with specific tagsβ
Appcircle will start building your application with the selected workflow whenever you perform a push with certain tags to your Git repository. Your project will be built automatically only if the push has the tags you specify, or you can specify a wildcard tag to build all tagged pushes.
This allows building scenarios like building only specific pushes that have the "release" in the tag.
Scheduled builds (Beta)β
In addition to event-based triggers, Appcircle can start a build automatically at times you define, independent of any push, pull/merge request, or tag activity in your repository. This is useful for nightly or periodic builds, regression runs, or any workflow that needs to run on a fixed cadence rather than in response to a Git event.
To set up a scheduled trigger:
1. Open the Triggers panel for the build profile and select the Scheduled tab.
2. Configure the schedule:
-
Time Zone: The time zone used to interpret the cron expression below. Appcircle offers the full list of UTC offsets (e.g.,
UTC+03:00,UTC+03:30) so you can schedule builds in your team's local time rather than converting to UTC manually.
-
Cron Expression: A standard 5-field cron expression that defines when the build should run, in the format
minute hour day-of-month month day-of-week:Field Allowed values Notes Minute 0β59Hour 0β23Day of month 1β31Month 1β12Day of week 0β60is SundayEach field accepts
*(any value), a specific number, a comma-separated list (e.g.1,15), a range (e.g.1-5), or a step value (e.g.*/30for every 30 units). Appcircle shows a plain-language summary underneath the field to help confirm the schedule before saving β for example:0 11 * * 1β "Schedule build will start 11:00 AM every Monday"*/30 * * * *β runs every 30 minutes0 0 1 * *β runs at midnight on the first day of every month
-
Branch Name: The branch the scheduled build will run against.
-
Config: The build configuration to use.
-
Workflow: The workflow to run.
3. Click the + button to add additional schedules to the same build profile, or the x next to a field to remove a schedule. Click Save once you're done.
Scheduled builds are currently in Beta. Design and behaviour could change in future stages.
You can tell scheduled runs apart from other builds afterward: builds started by a schedule are labeled with their own Schedule trigger type in Build History and reporting, rather than being grouped with manually started builds.
Skipping a workflowβ
If your commit message includes [skip ci] or [ci skip], your workflow will be skipped.
Retrying a workflowβ
If your pull/merge request comment includes [retry], your workflow will be retried.
Appcircle needs to receive comment events for this to work:
- GitLab and Azure DevOps: Automatic webhooks already include comment events.
- GitHub, Bitbucket Cloud, and Bitbucket Server: Automatic webhooks don't include comment events, so
[retry]comments are not received. To use[retry], set up a manual webhook that includes the comment event. See Events to Select for Manual Webhooks.
Auto Cancel Redundant Pipelineβ
When enabled, this feature automatically cancels any previously running build that matches the same build configuration, build workflow, build trigger and branch if a new run is triggered. This helps prevent unnecessary resource usage and reduces queue time by skipping outdated pipeline runs.
To enable this feature:
- Open the build profile and select Configurations at the top right.
- Open the configuration and, on the Config tab, turn on the Auto cancel toggle.
- Click Save.
The Auto-Cancel Redundant Pipeline mechanism works based on four key parameters:
- Build Configuration
- Build Workflow
- Build Trigger
- Git Branch
If a new build is triggered with the same values for all these parameters, any previously queued or running build is automatically cancelled.
Builds that are manually started do not affect ongoing or queued builds; the auto-cancel mechanism does not apply to manually started builds.
Further Automatic Build Subjectsβ
Trigger Prioritiesβ
If you set multiple triggers, certain branch definitions will not take precedence over wildcard definitions. They will all start at the same time. Below is an example:
Assume that you have a branch named development with three push triggers.
- Trigger branch:
*-> Trigger Workflow: Workflow 1 - Trigger branch:
development-> Trigger Workflow: Workflow 2 - Trigger branch:
develop*-> Trigger Workflow: Workflow 3
When there is a push or PR for the development branch, all triggers (since the word development contains both * and develop*) will be used to start a different build for each branch. At this point, a total of three build pipelines will begin.
If multiple triggered builds exceed your plan's concurrency limits, Appcircle will automatically queue them, and all of them will be executed unless you cancel.
Wildcard Referenceβ
You can specify branch names or tags with an asterisk wildcard to automate builds. Below are some examples:
| Pattern | Description |
|---|---|
*-fix | Build if it ends with -fix |
fix-* | Build if it starts with fix- |
*-fix-* | Build if it -fix- is present anywhere in the name |
fix-*-build | Build if it starts with fix- and ends with -build |
* | Build everything |
Build Initiator Shown in Appcircleβ
Appcircle shows who started a build in three places:
- Started by in the active process panel
- Triggered User in the "Starting workflow" section of the build logs
- Initiated by in the Build History report
All three show the same value. Appcircle sets this value when the build enters the queue, and the value depends on the trigger type:
| Trigger type | Value shown |
|---|---|
| Manual build | The email of the Appcircle user who started the build |
| Push | The commit author's email, as sent by the Git provider |
| Pull/merge request | The identity of the pull request, as sent by the Git provider (see the table below) |
| Tag | The user who pushed the tag, not the author of the tagged commit |
| Scheduled build | system |
Some Git providers send a username or an account name instead of an email. In that case, Appcircle shows that value as it is:
| Git provider | Push | Pull/merge request | Tag |
|---|---|---|---|
| GitHub / GitHub Enterprise | Commit author email | Pull request author's GitHub username | Pusher email |
| GitLab | Commit author email | Last commit author email | Pusher email, or username if the email is hidden |
| Bitbucket Cloud | Commit author email | Pull request author | Pusher nickname |
| Bitbucket Server | Commit author email | Pull request author email | Pusher email |
| Azure DevOps | Commit author email | Pull request creator account (for example, DOMAIN\user) | Pusher account (for example, DOMAIN\user) |
If the Git provider sends no identity for the event, Appcircle shows an email from your organization instead.
FAQβ
Why is my Appcircle trigger not working and how can I fix it?β
First, ensure that the build profile triggers are set for the desired branches and actions. Please check the trigger settings from the Managing Triggers for Builds section in the documentation.
Appcircle is triggered via the Git provider's webhooks. To properly work with triggers, webhooks in the repositories are used by Appcircle. Also, ensure that the repository has webhook access to Appcircle. To connect webhooks, the Git provider connection must be set up properly while creating a build profile.
Certain Git actions to the repositories, such as push, merge, pull request, tag push, etc., activate a specified event with the repository's webhooks. It is necessary to ensure that the desired event is actually triggered by the action in the Git provider's repository.
If webhooks are disabled due to frequent use or connection-based errors, using test events may help re-enable webhooks in Git providers.
To ensure webhooks are set and working, the webhook history can be reviewed within the Git providers. Let's check the Git providers below. You can follow the steps in the Git provider's documentation to access the webhook event history.
- GitHub Webhook Deliveries
- GitLab Webhook Request History
- Azure DevOps Services Webhook History
- Bitbucket Webhook Documentations
A document detailing the history of webhooks is not provided by Bitbucket. To access the webhook history, please navigate to:
Bitbucket -> Repository -> Repository Settings -> Webhooks -> View Requests
View Requests has to be enabled before requests can be seen.
Once the webhook is created and confirmed to be properly set up and healthy in the Appcircle build profile, and it is verified to work correctly with the specific Git provider, the process works as follows:
- A Git action, such as pushing a code block, triggers a webhook event.
- This webhook event activates the trigger in Appcircle.
- Appcircle then automatically starts the build process.
You can also open External Webhooks in Appcircle to see the webhook events that Appcircle received, their status, and their payloads. See External Webhooks.
The webhook delivery is successful in my Git provider, but no build starts. Why?β
A successful delivery only means Appcircle accepted the request. Check the HTTP response code in the provider's delivery history:
- 204 No Content (or a 200 with no build) on a manual webhook URL means that no build profile is bound to this webhook. Open the build profile's Webhooks dialog and bind the profile, especially for profiles in sub-organizations that reuse a webhook created elsewhere.
- 401 Unauthorized means the webhook secret doesn't match. Copy the secret from the Webhooks dialog again.
- 400 Bad Request means the webhook URL is unknown or the webhook is no longer active. Copy the URL from the Webhooks dialog again.
- 200 OK usually means the event reached a bound build profile. Check that the trigger's branch, target branch, or tag pattern matches the event. For pull/merge request triggers, compare the source branch, target branch, and action in the payload with the trigger settings.
If everything matches, contact support with the delivery time and payload. Self-hosted customers can also send the build service logs for that time range.
Why does my tag trigger not start a build?β
Appcircle starts a tag build from a commit it already knows. If the tagged commit hasn't reached Appcircle through a push webhook or a repository refresh, the tag event is ignored. Make sure the tagged commit is pushed to a branch and visible in the build profile before you push the tag.
Why does my tag trigger start a build on a different branch?β
When you create a tag, it is applied to a specific commit, not a branch. The system does not have explicit branch information linked to the tag. Therefore, when the tag trigger starts a build in Appcircle, it uses the branch where Appcircle most recently recorded the tagged commit. If the commit exists on more than one branch, this can look random.
To control this behavior, push an empty commit to the desired branch and then apply the tag to this new commit. This ensures that the tag trigger starts from the intended branch.
Why isn't my scheduled build running at the expected time?β
Scheduled builds don't depend on webhooks, so the troubleshooting steps above for event-based triggers don't apply. Instead, check the following:
- Cron expression: Confirm the expression matches the schedule you intend. The plain-language summary shown under the Cron Expression field in the Scheduled tab is a quick way to verify this before saving.
- Time zone: Double-check the selected time zone β a schedule saved against the wrong offset will run at the correct cron time, just in a different time zone than expected.
- Branch, config, and workflow: Make sure the selected branch, build configuration, and workflow are still valid and haven't been renamed, moved, or removed since the schedule was created.
If the schedule and time zone both look correct and the build still doesn't start, check Build History and filter by the Schedule trigger type to confirm whether the build ran at all.
How to enable triggers for AWS CodeCommit repositories?β
Appcircle supports AWS CodeCommit triggers through an Amazon SNS topic.
For more information, please refer to: 
After you follow the steps in the referenced document above to create a trigger, you need to create a notification rule under CodeCommit Settings as shown below to add a webhook URL.
Then select the "Enable raw message delivery" option while adding the webhook URL as a subscription to the topic.
Why does a build show a different user than the commit author?β
Appcircle shows the user who triggered the build, not always the commit author. A tag build shows the user who pushed the tag. A manual build shows the Appcircle user who started it. A pull request build shows the identity the Git provider sends for the pull request. For the full list, see Build Initiator Shown in Appcircle.
Why do two pull request builds show the initiator differently?β
The initiator of a pull request build comes from the data the Git provider sends, and from the commit data Appcircle already has. Depending on the Git provider and on how the commit first reached Appcircle, the same field can show an email, a username, or an account name. This does not affect the build itself. For the values each provider sends, see Build Initiator Shown in Appcircle.
Need help?β
Get help from Appcircle's support team, or see how others are using Appcircle by joining our Slack Channel.