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.

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

Issues with GH Changelog updater (secondary usage API requests) #976

Closed
1 of 2 tasks
CasperWA opened this issue Oct 18, 2021 · 4 comments
Closed
1 of 2 tasks

Issues with GH Changelog updater (secondary usage API requests) #976

CasperWA opened this issue Oct 18, 2021 · 4 comments
Labels
CI Continuous Integration - GitHub Actions issues (NOT related to the repository Action) docs Issues pertaining to documentation.

Comments

@CasperWA
Copy link
Member

CasperWA commented Oct 18, 2021 •
edited

Two things:

  • A bug in the docs deployment (see this run).
  • GitHub is deploying their own "get changelog since last release" feature it seems (check out the new button when releasing), and together with this I am seeing a lot of "secondary usage" access denied for the GitHub API when using the changelog generator.
    It doesn't seem to be failing (the changelog generator action), however, I fear it will be severely reduced in capability going forward.
@CasperWA CasperWA added bug Something isn't working docs Issues pertaining to documentation. CI Continuous Integration - GitHub Actions issues (NOT related to the repository Action) labels Oct 18, 2021
@CasperWA
Copy link
Member Author

I'll take care of the first point, as I know the solution: Separate out these workflow steps into separate jobs.

@CasperWA
Copy link
Member Author

Note, I've manually deployed the v0.16.5 documentation.

@CasperWA CasperWA mentioned this issue Oct 18, 2021
Merged
@CasperWA CasperWA changed the title Deployment workflow failing Issues with GH Changelog updater (secondary usage API requests) Oct 20, 2021
@CasperWA CasperWA removed the bug Something isn't working label Oct 20, 2021
@CasperWA
Copy link
Member Author

I don't think this is still a relevant issue, or?

@ml-evs
Copy link
Member

ml-evs commented May 10, 2022

I don't think its relevant, no. I ran into the rate limit yesterday after some workflow re-runs but there's nothing we can do about it (just wait 5 mins then manually re-run).

@ml-evs ml-evs closed this as completed May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CI Continuous Integration - GitHub Actions issues (NOT related to the repository Action) docs Issues pertaining to documentation.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ml-evs @CasperWA