---
# System prepended metadata

title: Brain dump on shield
tags: [shield]

---

---
robots: nofollow, noindex 
tags: shield
---

# Brain dump on shield



## This is really GitHub repo health
- Shield is the first line of defense in repo health
- Sets the stage for a healthly repo
- What other expectations are there for the team in terms of GitHub repo health

## Pull Requests
- Should be high priority
- Codeowner should consider PR in thier area most important (more important than e-mail)
- SLA for turnaround on comments
- Role of shield and codeowner w.r.t pull requests
    - Previous: Shield secondary in charge of nagging
    - ??? Automation

## Issues 
- Sausage Making vs Customer Communication
- Close or Leave open
    - Close
- Someday maybe?
    - track this outside of issues per person
- Epic issue to track component updates
    - Close behavior/breaking changes
    - Reference in epic issues for that component

## Problems
- Behavior changes or breaking changes that we just can't do

## Codeowners
- Refresh this list
- other stuff?

## Partner owned packages

## Extra ideas
- Have triage assign to codeowner
- Should shield even do bug fixing?
- What about urgent...

