-
-
Notifications
You must be signed in to change notification settings - Fork 844
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
Generating changelog is really slow #1018
Comments
The rate limit seems to happen with As far as I see the code, issue events are only used to detect the closed date by |
thanks for your answer! i'm not sure if there is any different between closed_at and merged_at for PRs, they should be same if I understand it correctly? |
Yes, closed_at and merged_at for PRs are mostly the same. On the other hand, rails/rails#45885 is merged on Sep. 10, but the commit date is Aug. 25. github-changelog-generator will label You can get the same result on GitHub GraphQL Explorer with this query. query {
repository(name: "rails", owner: "rails") {
pullRequest(number: 45885) {
mergedAt
closedAt
commits(last: 1) {
edges {
node {
commit {
id
author {
date
email
name
}
}
}
}
}
}
}
} |
Describe the bug
A clear and concise description of what the bug is.
When I try to generate changelog for my project, it's really slow after printing out
Fetching closed dates for issues
and stuck on here, it might reach the rate-limit of our GHE. But I don't know how to check more detailsTo Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: