Skip to content

Onboarding to GitOps.ResourceManagement#5690

Closed
microsoft-github-policy-service[bot] wants to merge 2 commits into
2.0from
onboarding-prIssueManagement
Closed

Onboarding to GitOps.ResourceManagement#5690
microsoft-github-policy-service[bot] wants to merge 2 commits into
2.0from
onboarding-prIssueManagement

Conversation

@microsoft-github-policy-service

Copy link
Copy Markdown

Add prIssueManagement.yml to onboard repo to GitOps.ResourceManagement as FabricBot replacement

@microsoft-github-policy-service microsoft-github-policy-service Bot requested a review from a team as a code owner June 15, 2023 11:46
@oliviacrain

oliviacrain commented Jun 16, 2023

Copy link
Copy Markdown

Should go through the main branch.

For internal folks curious about this change:
https://eng.ms/docs/more/github-inside-microsoft/policies
https://eng.ms/docs/more/github-inside-microsoft/overview/fabric-bot

@oliviacrain oliviacrain requested a review from a team June 16, 2023 17:10
@@ -0,0 +1,83 @@
id:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is there a reason we want to merge this into 2.0 and not main?

@PawelWMS PawelWMS changed the base branch from 2.0 to main June 19, 2023 21:19
@PawelWMS PawelWMS changed the base branch from main to 2.0 June 19, 2023 21:19
@PawelWMS

Copy link
Copy Markdown
Contributor

Created a main rebase in #5710. Closing this one.

@PawelWMS PawelWMS closed this Jun 19, 2023
@PawelWMS PawelWMS deleted the onboarding-prIssueManagement branch June 19, 2023 21:25
@markphip

Copy link
Copy Markdown

FWIW, the policy service looks at the default branch. In your case that is 2.0 not main. Committing the policy to main will not do anything

@oliviacrain

Copy link
Copy Markdown

Thanks @markphip- the main branch is the development branch that gets merged into 2.0, so this change will make its way to the 2.0 branch dependent on our release cadence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants