-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📖 MAINTAINERS: Reflect active project contributors and affiliations #4521
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4521 +/- ##
==========================================
+ Coverage 66.80% 68.19% +1.39%
==========================================
Files 230 247 +17
Lines 16602 18635 +2033
==========================================
+ Hits 11091 12709 +1618
- Misses 4808 5083 +275
- Partials 703 843 +140 |
Signed-off-by: Stephen Augustus <[email protected]>
Signed-off-by: Stephen Augustus <[email protected]>
Co-authored-by: Spencer Schrock <[email protected]> Signed-off-by: Stephen Augustus <[email protected]>
@jeffmendoza @raghavkaul — we'll need your signoff here as well, as there are Steering changes, which require majority. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Thanks for the reviews, everyone! |
I've actioned on these GitHub team changes earlier today. |
What kind of change does this PR introduce?
📖 MAINTAINERS: Reflect active project contributors and affiliations
To all emeritus contributors, thank you immensely for making this project what it is today!
What is the current behavior?
What is the new behavior (if this is a feature change)?**
Which issue(s) this PR fixes
Special notes for your reviewer
@ossf/scorecard-admins — I'm presenting this PR ahead of making any changes to the GitHub teams.
@azeemshaikh38 @laurentsimon @naveensrinivasan @olivekl — explicitly tagging you as well.
If there are any questions, feel free to ask here or privately!
Does this PR introduce a user-facing change?
For user-facing changes, please add a concise, human-readable release note to
the
release-note
(In particular, describe what changes users might need to make in their
application as a result of this pull request.)