Add release-please configuration

.github/release-please.yml

@@ -0,0 +1,3 @@
+manifest: true
+primaryBranch: master
+handleGHRelease: true

.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+  ".": "3.1.14"
+}

CONTRIBUTING.md

@@ -15,6 +15,36 @@ When a new package is about to be released, changes in dev will be merged into m
 
 Some things to note about this project:
 
+## Commit message format
+To support our automated release process, pull requests are required to follow the [Conventional Commit](https://www.conventionalcommits.org/en/v1.0.0/)
+format.
+
+Each commit message consists of a **header**, an optional **body** and an optional **footer**. The header is the first line of the commit and
+MUST have a **type** (see below for a list of types) and a **description**. An optional **scope** can be added to the header to give extra context.
+
+```
+<type>[optional scope]: <short description>
+<BLANK LINE>
+<optional body>
+<BLANK LINE>
+<optional footer(s)>
+```
+
+The recommended commit types used are:
+
+ - **feat** for feature updates (increments the _minor_ version)
+ - **fix** for bug fixes (increments the _patch_ version)
+ - **perf** for performance related changes e.g. optimizing an algorithm
+ - **refactor** for code refactoring changes
+ - **test** for test suite updates e.g. adding a test or fixing a test
+ - **style** for changes that don't affect the meaning of code. e.g. formatting changes
+ - **docs** for documentation updates e.g. ReadMe update or code documentation updates
+ - **build** for build system changes (gradle updates, external dependency updates)
+ - **ci** for CI configuration file changes e.g. updating a pipeline
+ - **chore** for miscallaneous non-sdk changesin the repo e.g. removing an unused file
+
+Adding a footer with the prefix **BREAKING CHANGE:** will cause an increment of the _major_ version.
+
 ### How the library is built
 The .Net client library has a handwritten set of core files and two folders of generated models and request builders. These models and request builders are generated using the [MSGraph SDK Code Generator](https://github.com/microsoftgraph/MSGraph-SDK-Code-Generator). **Changes made to the ```Models``` and ```Requests``` folders will be overwritten** the next time the generator is run. 
 

release-please-config.json

@@ -0,0 +1,22 @@
+{
+  "bootstrap-sha": "9903e0c129683979234f287d59f7468ca5cd7341",
+  "exclude-paths": [
+    ".git",
+    ".idea",
+    ".github",
+    ".vscode"
+  ],
+  "release-type": "dotnet-yoshi",
+  "include-component-in-tag": false,
+  "include-v-in-tag": true,
+  "packages": {
+    ".": {
+      "package-name": "src/Microsoft.Graph.Core/",
+      "changelog-path": "CHANGELOG.md",
+      "extra-files": [
+        "src/Microsoft.Graph.Core/Microsoft.Graph.Core.csproj"
+      ]
+    }
+  },
+  "$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json"
+}

src/Microsoft.Graph.Core/Microsoft.Graph.Core.csproj

@@ -20,7 +20,12 @@
     <DelaySign>false</DelaySign>
     <AssemblyOriginatorKeyFile>35MSSharedLib1024.snk</AssemblyOriginatorKeyFile>
     <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
+    <!-- x-release-please-start-version -->
     <VersionPrefix>3.1.13</VersionPrefix>
+    <!-- x-release-please-end -->
+    <!-- VersionPrefix minor version should not be set when the change comes from the generator. It will be updated automatically. -->
+    <!-- VersionPrefix minor version must be manually set when making manual changes to code. -->
+    <!-- VersionPrefix major and patch versions must be manually set. -->
     <VersionSuffix></VersionSuffix>
     <PackageReleaseNotes>
 - https://github.com/microsoftgraph/msgraph-sdk-dotnet-core/blob/dev/CHANGELOG.md