Skip to content

Conversation

@MIchaelMainer
Copy link
Contributor

@MIchaelMainer MIchaelMainer commented Jun 9, 2023

PR Type

  • Other... Please describe: policy

Description of the changes

Capture current policy state so that we can make versioned changes to branch protection policies. This will enable policy history, auditing, review, standardization, and templatization. We will update policy in later PR.

We can ignore the rule that states: At least one value under RequiredStatusChecks must be specified when RequiresStrictStatusChecks is true. This is getting removed

PR checklist

  • Project builds (yarn build) and changes have been tested in at least two supported browsers (Edge + non-Chromium based browser)
  • All public APIs (classes, methods, etc) have been documented following the jsdoc syntax
  • Stories have been added and existing stories have been tested
  • Added appropriate documentation. Docs PR:
  • License header has been added to all new source files (yarn setLicense)
  • Contains NO breaking changes

Other information

Need to add this before we remove this repo from the org policy so that capture all of our existing branch policy.

@MIchaelMainer MIchaelMainer requested a review from a team as a code owner June 9, 2023 21:45
@ghost
Copy link

ghost commented Jun 9, 2023

Thank you for creating a Pull Request @MIchaelMainer.

This is a checklist for the PR reviewer(s) to complete before approving and merging this PR:

  • I have verified a documentation PR has been linked and is approved (or not applicable)
  • I have ran this PR locally and have tested the fix/feature
  • I have verified that stories have been added to storybook (or not applicable)
  • I have tested existing stories in storybook to verify no regression has occured
  • I have tested the solution in at least two browsers (Edge + 1 non-Chromium based browser)

@MIchaelMainer
Copy link
Contributor Author

gavinbarron
gavinbarron previously approved these changes Jun 12, 2023
Copy link
Member

@gavinbarron gavinbarron left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

musale
musale previously approved these changes Jun 13, 2023
Copy link
Contributor

@musale musale left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@gavinbarron gavinbarron dismissed stale reviews from musale and themself via 6ffcdf6 June 13, 2023 13:50
@MIchaelMainer MIchaelMainer merged commit d98b823 into main Jun 13, 2023
@MIchaelMainer MIchaelMainer deleted the branchprotectionpolicy branch June 13, 2023 20:53
@microsoft-github-policy-service
Copy link
Contributor

4 invalid rules

  • RequiredStatusChecks must have at least one value when RequiresStrictStatusChecks is true.
  • RequiredStatusChecks must have at least one value when RequiresStrictStatusChecks is true.
  • RequiredStatusChecks must have at least one value when RequiresStrictStatusChecks is true.
  • RequiredStatusChecks must have at least one value when RequiresStrictStatusChecks is true.

Total execution time: 0.19 seconds

sebastienlevert pushed a commit that referenced this pull request Jun 23, 2023
* fix: remove react peer dependency (#2389)

* fix: add top to the caching key to allow varying values with different page sizes (#2406)

Signed-off-by: Martin Musale <[email protected]>

* chore: capture all branch protection policy (#2430)

* chore: capture all branch protection policy
* wrap pattern in quotes

* fix: set requiresStrictStatusChecks to false

requiresStrictStatusChecks should be false if we don't have one or more status checks defined in requiredStatusChecks property.

---------

Signed-off-by: Martin Musale <[email protected]>
Co-authored-by: Musale Martin <[email protected]>
Co-authored-by: Michael Mainer <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants