Dark Mode

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: add limit-commits option#67

Draft
ruyadorno wants to merge 1 commit intomainfrom
add-limit-commits-option
Draft

feat: add limit-commits option#67
ruyadorno wants to merge 1 commit intomainfrom
add-limit-commits-option

Conversation

Copy link
Member

ruyadorno commented Mar 1, 2024

Last time I had to fight GitHub API secondary rate limits for a very long-lived LTS release I ended up writing this (based on knowledge shared from @BethGriggs) to help me unblock retrieving a list of commits from branch-diff.

Although it might be functional, the current API here is very clunky and requires the user to find out how many commits are already ignored in order to provide that value to skip-commits and from a combination of skip-commits and limit-commits hopefully cut out a limited enough series of commit that will not trigger GitHub API limits.

Opening this as a draft so that we can discuss better alternatives.

Adds a new option that can be used to set a maximum number of commits
that branch-diff should work with prior to starting requesting GitHub
APIs.

This is an essential feature to help releasers avoid exceeding
GitHub API secondary rate limit.
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

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant