Create BestPractices.md #10074
Create BestPractices.md #10074
Conversation
Co-authored-by: Missy Messa <47990216+missymessa@users.noreply.github.com>
Updated based on feedback
Added information about closing issues.
Changes made based on feedback
| @@ -0,0 +1,19 @@ | |||
| # Best Practices for .NET Engineering Services | |||
There was a problem hiding this comment.
This is great @ilyas1974, thanks for writing it up. What do you think the best way to track how we're doing is? Should we start looking at metrics for our own CI build breaks? Other?
There was a problem hiding this comment.
Great question - let me think on that. Perhaps a note in a teams channel (maybe roll out or FR Internal) letting the team know that someone is working on a repo that is not "green"?
There was a problem hiding this comment.
Getting back around to this - we've been doing a good job of monitoring things through FR and I think we will continue to do so. We'll report on it during the weekly stand up. Hopefully we won't have to do this often as the team will start following up on the issues they are involved in.
markwilkie
left a comment
There was a problem hiding this comment.
lgtm - let's try this out and adjust as required.
To double check:
Feel free to make suggestions on best practices that you think should be added to this document.