Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FabricBot: Onboarding to GitOps.ResourceManagement because of FabricBot decommissioning #4971

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dotnet-policy-service[bot]
Copy link

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

Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html

Please review and merge this PR to complete the process of onboarding to the new service.

…t as FabricBot replacement

 Details on the replacement service and the syntax of the new yaml configuration file is available publicly at: https://microsoft.github.io/GitOps/policies/resource-management.html

Please review and merge this PR to complete the process of onboarding to the new service.
@ghost
Copy link

ghost commented Feb 2, 2024

Thanks dotnet-policy-service[bot] for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

@ghost ghost requested review from michael-hawker and azchohfi February 2, 2024 19:25
Copy link

@jeffhandley jeffhandley left a comment

Choose a reason for hiding this comment

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

There are a lot of gaps on this config migration. This repository is not managed by the .NET team so it wasn't on our group's radar.

Owners of this repo are welcome to connect with me, @wtgodbe, and @mkArtakMSFT if they'd like to reference how we approached overcoming our feature gaps, but most of the issues surfaced in my review don't have clear solutions.

"subCapability": "IssuesOnlyResponder",
"version": "1.0",
"config": {
"taskName": "Add needs triage and bug label to new issues",

Choose a reason for hiding this comment

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

This task didn't get ported, presumably because it references isPartOfProject which is not supported.

"issues",
"project_card"
],
"taskName": "Add Voting to new Feature Requests",

Choose a reason for hiding this comment

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

This feature didn't get ported over because addReactionToIssue is not supported.

- addLabel:
label: 'needs attention :wave:'
- addReply:
reply: "This issue has been marked as \"needs attention \U0001F44B\" due to no activity for **15 days**. Please triage the issue so the fix can be established. "

Choose a reason for hiding this comment

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

Suggested change
reply: "This issue has been marked as \"needs attention \U0001F44B\" due to no activity for **15 days**. Please triage the issue so the fix can be established. "
reply: "This issue has been marked as \"needs attention :wave:" due to no activity for **15 days**. Please triage the issue so the fix can be established. "

action: Opened
then:
- addReply:
reply: "Thanks ${issueAuthor} for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request \U0001F64C"

Choose a reason for hiding this comment

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

Suggested change
reply: "Thanks ${issueAuthor} for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request \U0001F64C"
reply: "Thanks ${issueAuthor} for opening a Pull Request! The reviewers will test the PR and highlight if there is any conflict or changes required. If the PR is approved we will proceed to merge the pull request :raised_hands:"

- addLabel:
label: 'needs attention :wave:'
- addReply:
reply: "This PR has been marked as \"needs attention \U0001F44B\" and awaiting a response from the team. "

Choose a reason for hiding this comment

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

Suggested change
reply: "This PR has been marked as \"needs attention \U0001F44B\" and awaiting a response from the team. "
reply: "This PR has been marked as \"needs attention :wave:\" and awaiting a response from the team. "

"issues",
"project_card"
],
"taskName": "Remove milestone if the PR is removed from the project column",

Choose a reason for hiding this comment

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

Project board automation is not supported in the new service, so related tasks were not ported.

}
}
],
"taskName": "Move to In-progress column in the project once In-PR label applied"

Choose a reason for hiding this comment

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

Project board automation is not supported in the new service, so related tasks were not ported.

"issues",
"project_card"
],
"taskName": "Move to In-progress column in the project once In-PR label applied",

Choose a reason for hiding this comment

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

Project board automation is not supported in the new service, so related tasks were not ported.

"issues",
"project_card"
],
"taskName": "Move to In-progress column in the project once In-PR label applied",

Choose a reason for hiding this comment

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

Project board automation is not supported in the new service, so related tasks were not ported.

"issues",
"project_card"
],
"taskName": "Move to In-progress column in the project once In-PR label applied",

Choose a reason for hiding this comment

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

Project board automation is not supported in the new service, so related tasks were not ported.

@jeffhandley
Copy link

CommunityToolkit/.github#5 needs to be merged to add the policy service bot to the CLA bypass list.

@ghost ghost added the no-recent-activity 📉 Open Issues that require attention label Feb 25, 2024
@ghost
Copy link

ghost commented Feb 25, 2024

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 30 days of this comment.

@ghost ghost removed the no-recent-activity 📉 Open Issues that require attention label Feb 25, 2024
@ghost ghost added the no-recent-activity 📉 Open Issues that require attention label Mar 11, 2024
@ghost
Copy link

ghost commented Mar 11, 2024

This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 30 days of this comment.

@ghost ghost removed the no-recent-activity 📉 Open Issues that require attention label Mar 11, 2024
Copy link
Author

@dotnet-policy-service[bot] please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@dotnet-policy-service agree [company="{your company}"]

Options:

  • (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@dotnet-policy-service agree
  • (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@dotnet-policy-service agree company="Microsoft"
Contributor License Agreement

Contribution License Agreement

This Contribution License Agreement ( “Agreement” ) is agreed to by the party signing below ( “You” ),
and conveys certain license rights to the .NET Foundation ( “.NET Foundation” ) for Your contributions to
.NET Foundation open source projects. This Agreement is effective as of the latest signature date below.

1. Definitions.

“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to .NET Foundation under this Agreement.

“Project” means any of the projects owned or managed by .NET Foundation and offered under a license
approved by the Open Source Initiative (www.opensource.org).

“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”

“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.

2. Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.

3. Originality of Work. You represent that each of Your Submissions is entirely Your
original work. Should You wish to Submit materials that are not Your original work,
You may Submit them separately to the Project if You (a) retain all copyright and
license information that was in the materials as you received them, (b) in the
description accompanying your Submission, include the phrase "Submission
containing materials of a third party:" followed by the names of the third party and any
licenses or other restrictions of which You are aware, and (c) follow any other
instructions in the Project's written guidelines concerning Submissions.

4. Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.

5. Licenses.

a. Copyright License. You grant .NET Foundation, and those who receive the Submission directly
or indirectly from .NET Foundation, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable
license in the Submission to reproduce, prepare derivative works of, publicly display, publicly perform,
and distribute the Submission and such derivative works, and to sublicense any or all of the foregoing
rights to third parties.

b. Patent License. You grant .NET Foundation, and those who receive the Submission directly or
indirectly from .NET Foundation, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license
under Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.

c. Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.

6. Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3 ). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6 , THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

7. Notice to .NET Foundation. You agree to notify .NET Foundation in writing of any facts or
circumstances of which You later become aware that would make Your representations in this
Agreement inaccurate in any respect.

8. Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.

9. Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.

10. Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by .NET Foundation.

.NET Foundation dedicates this Contribution License Agreement to the public domain according to the Creative Commons CC0 1.

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

Successfully merging this pull request may close these issues.

2 participants