[go: up one dir, main page]

Skip to content
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 audit log rate limit category and make rate limit category getter public #3088

Merged
merged 3 commits into from
Mar 20, 2024

Conversation

Letiste
Copy link
Contributor
@Letiste Letiste commented Mar 1, 2024

When calling https://api.github.com/rate_limit, the endpoint returns a audit_log rate limit category as well. This is used for /audit-log endpoints:

This PR adds this new rate limit category.

I have a use case where I need to know the rate limit category before making the request so as to not reimplement what's already done in go-github, I made this logic public. Other users could also benefit of this change.
If you think it's not reasonable and it should be kept private, I will revert this change.

Copy link
codecov bot commented Mar 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.87%. Comparing base (2b8c7fa) to head (c483b01).
Report is 23 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #3088      +/-   ##
==========================================
- Coverage   97.72%   92.87%   -4.86%     
==========================================
  Files         153      170      +17     
  Lines       13390    11404    -1986     
==========================================
- Hits        13085    10591    -2494     
- Misses        215      723     +508     
  Partials       90       90              

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

@Letiste Letiste closed this Mar 1, 2024
@Letiste Letiste reopened this Mar 1, 2024
@Letiste Letiste marked this pull request as ready for review March 1, 2024 15:45
@Letiste
Copy link
Contributor Author
Letiste commented Mar 18, 2024

@gmlewis could you take a look at this when you have some time? 🙏 (I'm notifying you as you seem to review the recent PRs, sorry if you are not the correct person for that).
Let me know if I need to clarify some things.
Not sure as well why the codecov is failing here, I thought I added all the necessary tests related to my changes but maybe I missed some

@gmlewis
Copy link
Collaborator
gmlewis commented Mar 18, 2024

@gmlewis could you take a look at this when you have some time? 🙏 (I'm notifying you as you seem to review the recent PRs, sorry if you are not the correct person for that). Let me know if I need to clarify some things. Not sure as well why the codecov is failing here, I thought I added all the necessary tests related to my changes but maybe I missed some

Hi @Letiste - I apologize for not seeing this two weeks ago. I'm not sure how I missed it. 😞

Don't worry about the codecov - it has lately been really flakey.

I'll take a look at the PR.

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, @Letiste !
LGTM.

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

@gmlewis gmlewis added the NeedsReview PR is awaiting a review before merging. label Mar 18, 2024
@gmlewis gmlewis removed the NeedsReview PR is awaiting a review before merging. label Mar 20, 2024
@gmlewis
Copy link
Collaborator
gmlewis commented Mar 20, 2024

Thank you, @rpelliard !
Merging.

@gmlewis gmlewis merged commit dbf91ee into google:master Mar 20, 2024
9 of 13 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.

3 participants