azure pipelines

Pushing changes to repo from Azure Pipeline

Piotr Wachulec

31 Oct 2025 — 1 min read

From time to time, there is a need to touch git repository from the pipeline - push tag, push commit with release notes, whatever your process need.

To properly configure such functionality, you have to:

explicitly mark that pipeline must persists git authentication after repository checkout:

jobs:
  - job: myJob
    displayName: 'My job'
    steps:
      - checkout: self
        persistCredentials: true

on the repository level, in the Security tab, you need to assign Contribute permission for Project Collection Build Service ({OrgName}) user:

Error

The below error you will get, if you will not set the proper permission:

==============================================================================
Task         : Command line
Description  : Run a command line script using Bash on Linux and macOS and cmd.exe on Windows
Version      : 2.250.1
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/command-line
==============================================================================
Generating script.
========================== Starting Command Output ===========================
/usr/bin/bash --noprofile --norc /azp/_work/_temp/bfcd49a4-4f2e-4045-86ad-7eb13b6fdda9.sh
remote: 001f# service=git-receive-pack
remote: 0000000000aaTF401027: You need the Git 'GenericContribute' permission to perform this action. Details: identity 'Build\***', scope 'repository'.
remote: TF401027: You need the Git 'GenericContribute' permission to perform this action. Details: identity 'Build\***', scope 'repository'.
fatal: unable to access 'https://dev.azure.com/<org>/<project>/_git/<repo>/': The requested URL returned error: 403

If you are interested in the pipelines permissions and scopes, you can find more info in the documentation:

Multiline expressions in Azure DevOps pipelines

For better readability, it is nice to break the lines in bigger conditions in Azure DevOps Pipeline definition, but it is not clearly documented, how it should be done exactly. Below you will find three examples. Conditional template inclusion jobs: - job: myJob displayName: 'My fancy job' steps:

Manually triggered stage cannot be the single stage in pipeline

Azure Pipelines provides possibility to trigger stages manually by setting the flag in the stage definition like it is described in the below documentation: Stages in Azure Pipelines - Azure PipelinesLearn how to organize your jobs into stages, define dependencies, and set conditions. Understand how to implement deployment strategies and

Git push without setup remote branch

You are starting working on a new branch. You want to push some commit and you get such message: $ git push fatal: The current branch feature/my-branch has no upstream branch. To push the current branch and set the remote as upstream, use git push --set-upstream origin feature/my-branch Again,

Nullable types in Bicep

Sometimes you need to define nullable parameters in Bicep files. It is possible by adding ? character after the type of the parameter: param <param_name> <param_type>? For example - let's assume the case that you need to deploy subnet and assign the NSG

Error

Read more

Multiline expressions in Azure DevOps pipelines

Manually triggered stage cannot be the single stage in pipeline

Git push without setup remote branch

Nullable types in Bicep