-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add "organization" field to more events #2949
Conversation
This should cover all events that GitHub says have an organization field.
Codecov Report
@@ Coverage Diff @@
## master #2949 +/- ##
=======================================
Coverage 98.19% 98.19%
=======================================
Files 145 145
Lines 12720 12720
=======================================
Hits 12490 12490
Misses 156 156
Partials 74 74
|
github/event_types.go
Outdated
|
||
// The following field is only present when the webhook is triggered on | ||
// a repository belonging to an organization. | ||
Organization *Organization `json:"organization,omitempty"` |
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.
Let's please name them all Org
.
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.
I left the existing ones, as I wasn't sure if you wanted a breaking change here or not. Happy to go change them all if you don't mind the breakage.
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.
Oh, sorry! That will teach me to do code reviews on my Android phone. 😂
Hmmm... consistency is nice as long as we document our changes.
Sure, let's be consistent and I'll mark this as a breaking API change. 😁
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.
Hmmm... I'm no longer on my phone, and I'm not understanding this statement:
I left the existing ones, as I wasn't sure if you wanted a breaking change here or not. Happy to go change them all if you don't mind the breakage.
I don't see any existing organization
fields in any of the structs you modified, so I don't think this is a breaking API change afterall, correct?
This field is inconsistently named throughout this file, but updating the old instances would be a breaking change, so they got left.
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.
Thank you, @billnapier !
LGTM.
Awaiting second LGTM+Approval from any other contributor to this repo before merging.
Thank you, @WillAbides ! |
This should cover all events that GitHub says have an organization field.
Fixes #2950