From db1311e3547d0312f75cef1978364f21012f7784 Mon Sep 17 00:00:00 2001 From: Santiago Fernandez Madero Date: Thu, 14 Jan 2021 11:28:34 -0800 Subject: [PATCH] Quick doc formatting update to test checkout without bundle. --- docs/issues-pr-management.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/issues-pr-management.md b/docs/issues-pr-management.md index 2357049547c04..10da88d1c9f2e 100644 --- a/docs/issues-pr-management.md +++ b/docs/issues-pr-management.md @@ -4,8 +4,8 @@ The purpose of this document is to help establish norms and best practices for d Here are a guiding set of principles of how to successfully combine the communities and teams which work together in dotnet/runtime. - Retain a 'one community/team' feel for dotnet/runtime - Leverage automation to label incoming/inflight to enable accountability -- area-* labels should align with a specific community/team for accountability -- Within an area-* there is leeway for community/team specific practices +- `area-*` labels should align with a specific community/team for accountability +- Within an `area-*` there is leeway for community/team specific practices # Details dotnet/runtime issues and pull requests are a shared resource. In alignment with the Principles the goal is to find a set of norms and best practices which enable a successful community within dotnet/runtime, understand what is expected, act as 'one community/team', and provide leeway at the area level.