Skip to main content
All CollectionsAutomationPipelinesTeam-shared pipelines
Which Git credentials are used for which actions in Pipelines?
Which Git credentials are used for which actions in Pipelines?

Expected behaviour for the use of individual versus team-shared Git credentials during automated Pipeline use.

George Marino avatar
Written by George Marino
Updated over a week ago

During the setup of a team-shared automated Pipeline, you're instructed to use an integration user within Git. These credentials are then used to create the Pipeline. Each user of the Pipeline is then expected to add their own individual Git credentials. It's these credentials that we use the majority of the time.

We do this so that the history of actions in Git is as accurate as possible. You'll know which user initiated which action.

However, we don't always use team-shared credentials for Pipeline actions (there are two exceptions when we don't), and this article confirms when to expect this to occur.

Manual indicates it's a user-initiated action. Automatic indicates that it's an automatic behaviour, not directly triggered by the users action. All of the actions listed below are actions taken in Gearset, rather than directly in Git.

Individual Git credentials:

  • The user who clicked the button:

    • Manual branch creation (and subsequent promotion branch creation)

    • Manual PR creation (and subsequent promotion PR creation)

    • Manual Release branch creation

    • Manual closing of PR

    • Manual Release PR merge/promotion

    • Automatic closing of PR (due to release branch creation)

  • The user who originally created the PR:

    • Manual PR promotion

    • Automatic reopening of PR (due to release branch abandon)

Integration Git credentials (team-shared):

  • Manual Sync-PR creation.

  • Automatic branch deletion.

Note: Should there be a change in the Gearset user (e.g. Someone removes their individual Git credentials or their whole user is removed etc), then Gearset may need to automatically revert to using the "Integration Git credentials" instead.

This will depend on the availability of the individual Git credentials.

Think of an action that isn't documented here? Please be sure to let our in-app support know!

Did this answer your question?