git-br | simple interactive cli tool to handle your local git | Command Line Interface library

If you want to change the prompt for Zsh:

PROMPT="⚡️%{$fg[red]%} ☣︎☯︎⚰︎☤⚚♱♚☨☥☥☨♚♱⚚☤⚰︎☯︎☣︎ %{$fg[red]%}⚡%{$fg[green]%}%T⚡️%{$fg[green]%}%{$fg[yellow]%}%d%{$fg[yellow]%} ⚡️"

^This is just an example of the difference between bash and zsh when setting prompt.^

for your case check this link:

https://www.themoderncoder.com/add-git-branch-information-to-your-zsh-prompt/

or change to bash using:

chsh -s /bin/sh

It's hard to provide an answer that addresses your specific issues, as you haven't provided much information. However, I can give you some background on how this is typically done.

Concerning what you've provided, you cite a document about decorating pull requests, which has a lot of information. It's not clear at all which error you are referring to.

The way you use SonarQube and Jenkins to block the merging of pull requests if SonarQube has "errors", is with the Quality Gate, and the configuration of the BitBucket repository.

You define the SonarQube quality gate with rules for when the scan is to be defined as "failing". For instance, you can define a minimum percentage of unit test code coverage, or the maximum number of vulnerabilities, or other issue types.

In Jenkins, you need to use the "withSonarQubeEnv()" and "waitForQualityGate()" pipeline steps. The former specifies the name of the SonarQube instance to use, which extracts the SonarQube credentials and url from the Jenkins configuration (you should define them in the Jenkins configuration, not in the build job, as you have done). The latter waits for SonarQube to produce the quality gate analysis, which is performed in a background job in SonarQube. When the background job completes, it will call the "Webhook", the url of which has to be configured in SonarQube, to point to Jenkins (often something like "http://{jenkinshost}:{jenkinsport}/jenkins/sonarqube-webhook"). In the Jenkins pipeline script, you check the return value from "waitForQualityGate()", and if the "status" property of that object is not equal to "OK", then the quality gate failed, and your script should call "error" to fail the build.

Run the following command in the cmd task of the pipeline:

People can set an alternate email address in their profile.

If your account is linked to AAD, that email should automatically flow from Azure Active Directory, if the contact email is configured there.

You can also edit your notification subscription settings and set an alternate email address for a specific notification class:

This is only possible for non-default subscriptions. So you may need to disable a global notification and create a personal notification subscription in order to set the custom email address.

You can recognize the global subscriptions by the 🌐 icon.

1. The "dev" branch doesn't exit on Gerrit, you just created it locally in your machine.

2. When you pushed to "refs/heads/dev" you tried to create the "dev" branch on Gerrit but you don't have permission to create branches. You need to have "Create Reference" permission on "refs/*".

3. It's not possible to push to "refs/for/dev" (create a review on Gerrit) because the "dev" branch doesn't exist in Gerrit (see 1. above).

You should double-check your Info.plist, You might have included something like this Privacy - Tracking Usage Description

My preferred way of working with remotes is to never use pull, but always use fetch followed by a merge/rebase. pull does the same behind the scenes, but I like to be able to inspect the history before that.

Fetch from all remotes, checkout your branch, rebase your branch:

You're on the right track.

You'll want to update your git command to include "origin" before the branch name and you'll probably want to push the changes after running your pull, or they'll just remain staged locally on the Build Agent.

This should do the trick:

One way to automate this is with bash: