Skip to main content

Git Advanced Trigger

This trigger is only available in the Smithy SaaS.

The Git Advanced trigger is the simplest way to set up a workflow if the target repositories are not in your GitHub organisation. When you add this trigger to your workflow, the git-target component is added automatically behind the scenes. The git-target parameters are then populated by the Git trigger with every run.

The trigger will target the default branch of each repo and scan all code in it.

It can target private repositories if you supply your username and SSH token.

One Git trigger can target multiple repositories. If it does, each repository is a separate target and will launch a separate run.

This trigger can only be launched manually.

Global component settings​

Go to the /integrations page and find the git-target. You need to set it up with the following settings:

Reference:      {{ .context.trigger.event.reference }}
Username:       {{ .context.trigger.auth.username }}
Token:          {{ .context.trigger.auth.token }}
Base reference:	{{ .context.trigger.event.target_branch }}
Repo URL:       https://{{ .context.trigger.event.host }}/{{ .context.trigger.event.organisation }}/{{ .context.trigger.event.repository }}

UI Settings​

Repo URL: The HTTPS or SSH URL of a git repo. You can add multiple of these.
Username: Username on the host Git system, e.g. a github username.
Token: SSH token. This is the same as the token for cloning a repo locally. You can create one by following the instructions here.

Here is what the trigger looks like when you set it up correctly:

Git trigger settings screenshot

Running the workflow​

To run a workflow with this trigger, press "Launch Workflow" on the workflow page. You will get a choice of which target repositories you want to scan. Then each selected target will launch into its own Run.

Git trigger launch screenshot