Skip to content

Conversation

@gavinbarron
Copy link
Member

Pull updates on main to vNext in preparation for v3 release merge back to main

@gavinbarron gavinbarron requested a review from a team as a code owner June 22, 2023 22:38
@ghost
Copy link

ghost commented Jun 22, 2023

Thank you for creating a Pull Request @gavinbarron.

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)

@gavinbarron
Copy link
Member Author

gavinbarron commented Jun 22, 2023

@MIchaelMainer any idea what's happening here with the GitOps/Branches failure as I attempt update our feature branch from main?

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

@gavinbarron requiresStrictStatusChecks should be false if we don't have one or more status checks defined in requiredStatusChecks property. GitHub allows that setting, the policy service is more strict so the exported settings cause that conflict. I made the fix in the policy file.

@sebastienlevert sebastienlevert merged commit 6b1dc4d into next/fluentui Jun 23, 2023
@sebastienlevert sebastienlevert deleted the chore/merge-main-to-next branch June 23, 2023 00:57
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.

5 participants