Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/api-doc-tools.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Köplinger <alex.koeplinger@outlook.com>2021-03-04 18:17:29 +0300
committerGitHub <noreply@github.com>2021-03-04 18:17:29 +0300
commit5f850662b2c0b81f3e21680e8039100179a02169 (patch)
treea9c600cc6bd2f14eba95b3f8fdcd6062451430e4
parent928f6ed10627de42509a4f9d900eb0c65fc362fc (diff)
parent9131f85afa4d4183b00184ad6a7552f6d50675bb (diff)
Merge pull request #538 from mono/master-to-mainmdoc-5.8.2
Change master branch to main
-rw-r--r--CONTRIBUTING.md2
-rw-r--r--azure-pipelines.yml2
-rw-r--r--mdoc/mdoc.nuspec2
3 files changed, 3 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c2e35304..5ace2d3c 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -37,7 +37,7 @@ If you are working in an area of the code that has transitioned to the new codin
This project tries to avoid chatty in-progress commits that are common during development. Once you’ve completed your development and are ready to move to the next stage of the contribution workflow, collapse your changes into as few feature-scoped commits as possible. Ideally if possible, every commit should pass all unit tests and be standalone.
-You can do so either by using an interactive rebase of your branch if you need multiple commits, or simply doing a soft reset `git reset origin/master —soft` … which will stage all of your changes and let you create a new single commit that contains all changes.
+You can do so either by using an interactive rebase of your branch if you need multiple commits, or simply doing a soft reset `git reset origin/main —soft` … which will stage all of your changes and let you create a new single commit that contains all changes.
The commit message should be verbose enough to explain what behavior is changing, bug is being fixed, or feature being added. It should also contain a reference to the github issue being resolved, as [described here](https://github.com/blog/1386-closing-issues-via-commit-messages).
diff --git a/azure-pipelines.yml b/azure-pipelines.yml
index 2cf30a7b..07838959 100644
--- a/azure-pipelines.yml
+++ b/azure-pipelines.yml
@@ -99,7 +99,7 @@ steps:
- task: PowerShell@2
name: 'mdocVersion'
displayName: 'Checking remote and local version of mdoc'
- condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/master'))
+ condition: and(succeeded(), eq(variables['Build.SourceBranch'], 'refs/heads/main'))
inputs:
filePath: 'mdoc/CheckNugetPublish.ps1'
diff --git a/mdoc/mdoc.nuspec b/mdoc/mdoc.nuspec
index 49518168..c4a8a9fb 100644
--- a/mdoc/mdoc.nuspec
+++ b/mdoc/mdoc.nuspec
@@ -7,7 +7,7 @@
<authors>Microsoft</authors>
<owners>Microsoft</owners>
<projectUrl>https://github.com/mono/api-doc-tools</projectUrl>
- <licenseUrl>https://github.com/mono/api-doc-tools/blob/master/LICENSE.md</licenseUrl>
+ <licenseUrl>https://github.com/mono/api-doc-tools/blob/main/LICENSE.md</licenseUrl>
<requireLicenseAcceptance>true</requireLicenseAcceptance>
<description>.NET API Documentation toolchain</description>
<copyright>© Microsoft Corporation. All rights reserved.</copyright>