Conversation
CONTRIBUTING.md
Outdated
| ## Submitting Pull Requests | ||
|
|
||
| - **DO** ensure submissions pass all Jenkins legs and are merge conflict free. | ||
| - **DO** ensure submissions pass all Azure Devops legs and are merge conflict free. |
There was a problem hiding this comment.
Should this make it clear that if you're unsure, just submit a draft PR? This otherwise mandates a standard that our own team doesn't meet.
There was a problem hiding this comment.
(don't let this question derail merging this fix, because this his hilariously bad.)
There was a problem hiding this comment.
I agree that someone should look at our contributing docs... This is a general pain point I feel on the team today: should I even bother running Test.cmd? Seems like most folks just submit PRs because Test.cmd has drifted so far from reality.
Co-authored-by: Jason Malinowski <jason.malinowski@microsoft.com>
|
This is part of #50579. |
|
@jaredpar or @RikkiGibson I keep getting this in the correctness leg Can't seem to find an existing bug on it. (an no logs are written out anywhere) has this ever been seen before? I can't imagine this markdown update is actually causing a build correctness problem |
|
@jaredpar has observed flakiness when rebuilding that and has disabled that rebuilding that project in another PR. Sorry for the inconvenience. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
No description provided.