-
Notifications
You must be signed in to change notification settings - Fork 2.1k
docs: Add clarifications for mergeable field in pull requests #3396
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
docs: Add clarifications for mergeable field in pull requests #3396
Conversation
d505fe2
to
ca738b7
Compare
It is now one single block comment @gmlewis |
Please run the scripts listed in step 4 of CONTRIBUTING.md and push the changes. That should fix the linter and tests. |
I will close this PR around the end of January, 2025 as "abandoned" if there is no further response. |
ca738b7
to
dd2c798
Compare
Done just in time :) |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3396 +/- ##
=======================================
Coverage 91.03% 91.03%
=======================================
Files 179 179
Lines 15535 15535
=======================================
Hits 14142 14142
Misses 1221 1221
Partials 172 172 ☔ View full report in Codecov by Sentry. |
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, @acouvreur !
LGTM.
Merging.
Comparing the OpenAPI spec for pull requests shows that these fields are not populated when listing (right), but they are through GET or webhook:

In their OpenAPI Spec they have
pull-request
andpull-request-simple
definitions.I think that would make sense to also have these structs instead of relying on comments for contextual field population.