+
Skip to content

Add support for registry_package event #3545

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

Merged

Conversation

ptzianos
Copy link
Contributor

@ptzianos ptzianos commented Apr 9, 2025

as of the time of this writing, the Github documentation describes two events related to packages. One called package and one called registry_package. According to the documentation, users should switch to using the package event instead of the registry_package event. However, when working with the actual permissions and events, there is no package event but there is a RegistryPackage event that can be enabled for a Github App. It looks like the documentation is wrong and the registry_package event was added after the package event and it's the registry_package event that users should expect to receive.

Fixes: #3544.

as of the time of this writing, the Github documentation describes two
events related to packages. One called package and one called
registry_package. According to the documentation, users should switch to
using the package event instead of the registry_package event. However,
when working with the actual permissions and events, there is no package
event but there is a RegistryPackage event that can be enabled for a
Github App. It looks like the documentation is wrong and the
registry_package event was added after the package event and it's the
registry_package event that users should expect to receive.
Copy link

google-cla bot commented Apr 9, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link

codecov bot commented Apr 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.23%. Comparing base (3a3f51b) to head (2ea91ea).
Report is 8 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3545      +/-   ##
==========================================
- Coverage   91.29%   91.23%   -0.07%     
==========================================
  Files         184      183       -1     
  Lines       16169    16053     -116     
==========================================
- Hits        14762    14646     -116     
  Misses       1231     1231              
  Partials      176      176              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Collaborator

@gmlewis gmlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

Copy link
Collaborator

@gmlewis gmlewis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you, @ptzianos!
LGTM.

Awaiting second LGTM+Approval from any other contributor to this repo before merging.

@stevehipwell - might you have time for a code review? Thank you!

@gmlewis gmlewis added the NeedsReview PR is awaiting a review before merging. label Apr 9, 2025
Copy link
Contributor

@stevehipwell stevehipwell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ptzianos
Copy link
Contributor Author

ptzianos commented Apr 11, 2025

@stevehipwell @gmlewis thank you both for the prompt reviews, do I need to fix the codecov check to get the change merged?

@gmlewis
Copy link
Collaborator

gmlewis commented Apr 13, 2025

@stevehipwell @gmlewis thank you both for the prompt reviews, do I need to fix the codecov check to get the change merged?

No need, thank you.

Thank you, @stevehipwell!

Merging.

@gmlewis gmlewis removed the NeedsReview PR is awaiting a review before merging. label Apr 13, 2025
@gmlewis gmlewis merged commit 462cda4 into google:master Apr 13, 2025
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for registry_package events
3 participants
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载