Is your feature request related to a problem?

Several of our actions run into the problem of working through the first X number of repos in an organization when they fail due to rate limiting or max action run times. If they could save state or remember what repos have been evaluated recently, that would be helpful for delivering more value for each action. This happens especially for OSPOs that are working on the "get clean" phase of any task rather than the "stay clean". ie. Every repo in an org of 10k repos needs a dependabot PR opened. (evergreen)

Related OSPO Tool

automatic-contrib-prs GitHub Action, cleanowners GitHub Action, evergreen GitHub Action, issues-metrics GitHub Action, stale-repos GitHub Action

Describe the solution you'd like

Ideas:

• A dump/file saved of repos processed and then an upload for the next run.
• Separate out the scan all repos/get repo list from the action that should be taken into separate actions
• database something something hand wave

Describe alternatives you've considered

No response

Additional context

No response