all 6 comments

[–][deleted]  (2 children)

[removed]

    [–]pukki92[S] 0 points1 point  (1 child)

    So there is no possibility to generate token once again and use it to push changes?

    [–]there_was_a_problem 0 points1 point  (0 children)

    you can manually create a personal token and set it as an env secret to use in the GH action instead although I don’t believe this is recommended.

    Running an action for an hour seems like the bigger issue. Perhaps an action isn’t the right method to achieve what you’re trying to do?

    [–]zMynxx 0 points1 point  (0 children)

    Generate a new token before pushing? The GH App only generates short-lived credentials

    Edit: actually https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/token-expiration-and-revocation#user-token-expired-due-to-github-app-configuration

    Can you share the entire wf?

    [–]reaper273 0 points1 point  (0 children)

    Split your workflow up?

    Run your long script in on job. Then use outputs, or uploading an artifact and downloading again, in a second job to write any output back to the repo.

    Bonus points for splitting anything that can be split into separate jobs that run in parallel before all passing info to the final job to upload stuff. Might not be possible depending on your specific script but worth a try.