You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/policies/msgraph-sdk-dotnet-branch-protection.yml
+1-37Lines changed: 1 addition & 37 deletions
Original file line number
Diff line number
Diff line change
@@ -37,45 +37,9 @@ configuration:
37
37
requiredStatusChecks:
38
38
- build
39
39
- license/cla
40
-
# Require branches to be up to date before merging. Requires requiredStatusChecks. boolean
40
+
# Require branches to be up-to-date before merging. Requires requiredStatusChecks. boolean
41
41
requiresStrictStatusChecks: true
42
42
# Indicates whether there are restrictions on who can push. boolean. Should be set with whoCanPush.
43
43
restrictsPushes: false
44
44
# Restrict who can dismiss pull request reviews. boolean
45
45
restrictsReviewDismissals: false
46
-
47
-
- branchNamePattern: dev
48
-
# This branch pattern applies to the following branches as of 06/12/2023 10:31:13:
49
-
# dev
50
-
51
-
# Specifies whether this branch can be deleted. boolean
52
-
allowsDeletions: false
53
-
# Specifies whether forced pushes are allowed on this branch. boolean
54
-
allowsForcePushes: false
55
-
# Specifies whether new commits pushed to the matching branches dismiss pull request review approvals. boolean
56
-
dismissStaleReviews: true
57
-
# Specifies whether admins can overwrite branch protection. boolean
58
-
isAdminEnforced: false
59
-
# Indicates whether "Require a pull request before merging" is enabled. boolean
60
-
requiresPullRequestBeforeMerging: true
61
-
# Specifies the number of pull request reviews before merging. int (0-6). Should be null/empty if PRs are not required
62
-
requiredApprovingReviewsCount: 1
63
-
# Require review from Code Owners. Requires requiredApprovingReviewsCount. boolean
64
-
requireCodeOwnersReview: true
65
-
# Are commits required to be signed. boolean. TODO: all contributors must have commit signing on local machines.
66
-
requiresCommitSignatures: false
67
-
# Are conversations required to be resolved before merging? boolean
68
-
requiresConversationResolution: true
69
-
# Are merge commits prohibited from being pushed to this branch. boolean
70
-
requiresLinearHistory: false
71
-
# Required status checks to pass before merging. Values can be any string, but if the value does not correspond to any existing status check, the status check will be stuck on pending for status since nothing exists to push an actual status
72
-
requiredStatusChecks:
73
-
- build
74
-
- license/cla
75
-
# Require branches to be up to date before merging. Requires requiredStatusChecks. boolean
76
-
requiresStrictStatusChecks: true
77
-
# Indicates whether there are restrictions on who can push. boolean. Should be set with whoCanPush.
78
-
restrictsPushes: false
79
-
# Restrict who can dismiss pull request reviews. boolean
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,10 @@ Thanks for considering making a contribution! Read over our guidelines and we wi
6
6
There are a few different recommended paths to get contributions into the released version of this library.
7
7
8
8
## File issues
9
-
The best way to get started with a contribution is to start a dialog with us. Sometimes features will be under development or out of scope for this library and it's best to check before starting work on contribution, especially for large work items.
9
+
The best way to get started with a contribution is to start a dialog with us. Sometimes features will be under development or out of scope for this library, and it's best to check before starting work on contribution, especially for large work items.
10
10
11
11
## Pull requests
12
-
All pull requests should be submitted against the **dev** branch or a specific feature branch. The master branch is intended to represent the code released in the most-recent Nuget package.
12
+
All pull requests should be submitted against the **master** branch or a specific feature branch. The master branch is intended to represent the code released in the most-recent Nuget package.
13
13
14
14
## Commit message format
15
15
@@ -42,7 +42,7 @@ The recommended commit types used are:
42
42
43
43
Adding a footer with the prefix **BREAKING CHANGE:** will cause an increment of the _major_ version.
44
44
45
-
When a new package is about to be released, changes in dev will be merged into master. The package will be generated from master.
45
+
When a new package is about to be release, the release PR will be merged into master. The package will be generated from master.
0 commit comments