Skip to content

Split user Member Activity History file to avoid rate limits #8263

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.

Sign up for GitHub

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

Jump to bottom
Merged
t-will-gillis merged 4 commits into from
Aug 10, 2025
Merged

Split user Member Activity History file to avoid rate limits #8263

t-will-gillis merged 4 commits into from
Aug 10, 2025

Conversation

@t-will-gillis
Copy link
Member

@t-will-gillis t-will-gillis commented Aug 10, 2025 •
edited
Loading

DO NOT REVIEW

Fixes #8261

What changes did you make?

Why did you make the changes (we will use this info to test)?

  • (hopefully) to avoid github rate limits.

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Screenshot 2024-10-28 154514

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

  • I have checked this PR for CodeQL alerts and none were found.
  • I found CodeQL alert(s), and (select one):
    • I have resolved the CodeQL alert(s) as noted
    • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
    • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)
Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

  • no visual changes

@t-will-gillis t-will-gillis added role: back end/devOps Tasks for back-end developers Feature: Onboarding/Contributing.md Complexity: Small Take this type of issues after the successful merge of your second good first issue size: 2pt Can be done in 7-12 hours labels Aug 10, 2025
@t-will-gillis t-will-gillis mentioned this pull request Aug 10, 2025
Closed
5 tasks
@t-will-gillis t-will-gillis merged commit 2849e90 into hackforla:gh-pages Aug 10, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

Complexity: Small Take this type of issues after the successful merge of your second good first issue Feature: Onboarding/Contributing.md role: back end/devOps Tasks for back-end developers size: 2pt Can be done in 7-12 hours

Projects

P: HfLA Website: Project Board
Archived in project

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Split user Member Activity History file to avoid rate limits

1 participant

@t-will-gillis