Triggers by event

Each trigger definition has four fields, including a type field. Each type of trigger corresponds to an event that causes that type of trigger to fire.

To learn more about creating trigger definitions, see Trigger definition.

Triggers on submit and populate

See Triggering on submit and populate.

Triggers on fixes

See Triggering on fixes.

  • fix-add

  • fix-delete

Triggers with graph depots

See Triggering with depots of type graph.

  • graph-push-start
  • graph-push-complete
  • graph-push-reference
  • graph-push-reference-complete
  • graph-lfs-push

Triggers on pushes and fetches

See Triggering on pushes and fetches.

  • push-submit

  • push-content

  • push-commit

Triggers on forms

See Triggering on forms.

  • form-save

  • form-out

  • form-in

  • form-delete

  • form-commit

Triggers for external file transfers

See Triggers for external file transfer.

  • pull-archive

  • edge-content

Triggers before or after commands

See Triggering before or after commands.

  • command

Triggers for external authentication

See Triggering to use external authentication.

  • auth-check

  • service-check

  • auth-check-sso
  • auth-set

  • auth-invalidate

Triggers on heartbeat

See Triggering on heartbeat (server responsiveness).

  • heartbeat-missing

  • heartbeat-resumed

  • heartbeat-dead

Triggers on journal rotation

See Triggering on journal rotation.

  • journal-rotate

  • journal-rotate-lock

Triggers for MFA

See Triggering for multi-factor authentication (MFA).

  • auth-pre-2fa
  • auth-init-2fa
  • auth-check-2fa

Triggers on failed-back

See Triggering on failed-back.

  • failed-back

Triggers on shelving

See Triggering on shelving events.

  • shelve-submit
  • shelve-commit
  • shelve-delete

Triggers to affect archiving

See Triggering to affect archiving.

  • archive

Triggers on failed-over

See Triggering on failed-over.

  • failed-over