Skip to content

Commit 1bad089

Browse files
Sidi MerzoukSidi Merzouk
Sidi Merzouk
authored and
Sidi Merzouk
committed
Add Aaron's review
1 parent d648842 commit 1bad089

File tree

4 files changed

+5
-8
lines changed

4 files changed

+5
-8
lines changed

.gitignore

+1-1
Original file line numberDiff line numberDiff line change
@@ -27,4 +27,4 @@ _themes*/
2727
/docs/pipelines/apps/cd/azure/_img/azure-devops-project-nodejs/vstsazureinfo.png~HEAD
2828
/docs/pipelines/apps/cd/azure/_img/azure-devops-project-nodejs/vstsazureinfo.png~master
2929
release-notes/2020/.DS_Store
30-
release-notes/2020/media/.DS_Store
30+
release-notes/2020/media/.DS_Store

release-notes/2020/includes/pipelines/sprint-173-update.md

-3
Original file line numberDiff line numberDiff line change
@@ -51,6 +51,3 @@ In addition to these changes, the macOS 10.14 image will be added to [the virtua
5151
When you create a draft pull request in Azure Repos, we wouldn't trigger a PR validation pipeline configured in your branch policy. We consider a draft pull request to be just that - a draft for which we shouldn't automatically run validations. While this use case worked for Azure Repos, the same behavior didn't hold for GitHub repos.
5252

5353
With this change, we're making the experience consistent for GitHub repos as well. When you create a [draft pull request](https://docs.github.com/github/collaborating-with-issues-and-pull-requests/about-pull-requests#draft-pull-requests) in GitHub, we won't start a pipeline automatically even if you configure a pull request trigger for the target branch. In order to validate your changes in a draft pull request, you can manually start a pipeline pointing to the `ref` of the pull request.
54-
55-
56-

release-notes/2020/includes/repos/sprint-173-update.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.topic: include
88

99
### Default branch name preference
1010

11-
Azure Repos now offers a customizable initial branch name for Git. In repository settings, you may choose any legal branch name to use when a repository is initialized. Azure Repos has always supported changing the default branch name for an existing repository. Visit [Manage branches](https://docs.microsoft.com/azure/devops/repos/git/manage-your-branches?view=azure-devops) for more details.
11+
Azure Repos now offers a customizable default branch name for Git. In repository settings, you may choose any legal branch name to use when a repository is initialized. Azure Repos has always supported changing the default branch name for an existing repository. Visit [Manage branches](https://docs.microsoft.com/azure/devops/repos/git/manage-your-branches?view=azure-devops) for more details.
1212

1313
&nbsp;<img src="../../media/173-pipelines-1-0.png" alt='default-branch-name' width="500">
1414

release-notes/2020/sprint-173-update.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ author: sid-ah
44
ms.author: simerzou
55
ms.technology: devops-release-notes
66
ms.date: 08/03/2020
7-
description: With Sprint 173 Update, we have introduced a new option that allows customers to set their default branch name just by following a few easy steps.
7+
description: With Sprint 173 Update, we have introduced a new option that allows customers to set a custom default branch name for all new repositories.
88
---
99

10-
# Introducing default naming branch
10+
# Customize your default branch name
1111

12-
In this sprint, we have introduced a new option that allows customers to set their **default branch name** just by following a few easy steps.
12+
In this sprint, we have introduced a new option that allows customers to set a **custom default branch name** for all new repositories.
1313

1414
Check out the [Features](#features) list below for more information.
1515

0 commit comments

Comments
 (0)