* 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.
* Deleting fabricbot.json
---------
Co-authored-by: dotnet-policy-service[bot] <123482357+dotnet-policy-service[bot]@users.noreply.github.com>
Fixes#9513
Context
Creation of CODEOWNERS file as per request in issue. Having a code owners file would also be generally useful when opening PRs in this repo, as it can sometimes be difficult and time consuming to determine who should be included as a reviewer.
Changes Made
Added @dotnet/source-build-internal as code owners for SB files
Added @dotnet/kitten as code owner for some of files and folders.
Testing
No testing
We need to look at feature requests and approve them or reject them as appropriate. This adds a label to ensure we notice it as part of our triage process.
This updates the bot that currently posts whenever any action is taken on a PR targeting 17.4 (i.e., opened, closed, reopened, commented on, etc.) to only post when the action is to open or reopen a PR. It also extends the branches for which this takes effect to include a number of vs* branches, including some that don't currently exist.
I think this is the final or penultimate iteration. Specifically, I don't think it will fire if you target main, then retarget to vs* without closing and reopening it...unfortunately, retargeting isn't something fabric bot understands. We can add "label added:Servicing-approved" to the list of options as a proxy. That isn't perfect, but it would make it slightly more robust and slightly noisier. I'm open to doing that or not doing that.
This may not work as intended, primarily because vs* may not expand to vs17.4/etc. I'm proposing merging this, since it shouldn't hurt, then checking to see if it works and tweaking it if not.
Fix other broken links.
Fixes#8438
Context
The primary branch for msbuild (and a number of other projects) has been migrating from 'master' to 'main'. A number of links reference the old 'master' branch name and are broken.
Changes Made
This PR updates those that have changed to 'main', along with updating a couple of other broken links.
Testing
Relying on the CI tests :)
Notes
It's my first MSBuild PR, apologies if there I've missed anything!
Context
Introduces backport GitHub action for automation-aided propagation of changes between branches.
usage:
comment
/backport to <target bracnh>
on PR that needs to be backported (ideally after merging). New PR will be created backporting to the requested branch.
TL;DR; Requesting to add FabricBot configuration associated with your repository to .github/fabricbot.json.
Context
FabricBot is now a config-as-code-only platform. As a result, while you can still use the FabricBot Configuration Portal to modify your FabricBot configuration, you can no longer save the changes. The only way to save changes to your configuration at the moment is to export configuration from the portal and upload the exported configuration to .github/fabricbot.json in your repository. In this pull request, we are adding your FabricBot configuration to your repository at .github/fabricbot.json so that you can make changes to it going forward.
While the FabricBot Configuration Portal is the only way to modify your FabricBot configuration at the moment, we have a feature on our backlog to publish the JSON schema defining the structure of the FabricBot configuration file. With the JSON schema, you can (1) use a plaintext editor of your choice to modify the FabricBot configuration file and use the schema to validate the file after editing or (2) configure VS Code to use the schema when editing FabricBot configuration file to take advantage of convenience features such as automatic code completion and field description on mouseover.
Pull Request Create, a MerlinBot Extension, was used to automatically create this pull request. If you have any questions or concerns with this pull request, please contact MerlinBot Expert DRI.
Guidance from dnceng is to use Dependabot instead of Darc/Maestro to manage updating packages to non-.NET or GA versions of packages (anything that's not "the current development build").
This commit introuduces Dependabot and moves some of our dependencies to be managed by it--specifically the ones that are build/test-time only and the ones that are embedded into our outputs. We should have free reign to control the versions of those any time without introducing downstream dependency problems.
Updating untriaged to needs-triage was done for consistency (needs-attention/design/more-info), ease of search/use (no spaces, all lowercase). Not to mention `untriaged` eventually meant some combination of "find a bucket this fits in" and "this needs attention".
However updating the label requires an update to our bug templates that apply those labels.
* Initial commit on a better issue template.
* Updated format and placed the templates in the proper folder
* Update folder structure, add PR template.
* Config.yml and PR adjustments
Emojis for different templates
Regression is its own section
Added warning for sharing binlogs
* Emoji for bug report
* Added runtime option for issue creation.
* First draft "My Build is Broken" template
* Responding to PR feedback
* Responding to PR feedback.
Notable adding a PR template for shiproom PRs.
Gang Wang
AR-May
dotnet-policy-service[bot]
Forgind
Jenny Bai
Vlada Shubina
adr26
Jan Krivanek
Ben Villalobos
msftbot[bot]
Forgind
Rainer Sigwald
Immo Landwerth
Ben Villalobos
Ben Villalobos
Mihai Codoban