External target repo

[burner1024]

How about allowing to sync not the current repo, but another one?
Meaning you'd have a dedicated "cron" repo, which would pull from some upstream and push to some fork.
That'd be more convenient to use in the fork, since cron actions only run in default branch, I think? So you either have to change default branch in the fork, or keep getting merge commits into main.

I wonder if that would also help with #44.

[aormsby]

So you either have to change default branch in the fork

In my opinion, this is often the wise choice anyway. But yeah, I see what you mean.

I'm not opposed to this, but I'm not really putting the time into it right now. If anyone wants to provide support, I'm open to helping and reviewing. A few notes from me:

1. Keep in mind the Action was designed around syncing the repo the workflow lives in. This kind of change is outside that scope, and it could require more than just a 'repo redirect' kind of feature. Don't know offhand. 🤷
2. The Action and is users would have to manage authentication of multiple repos, which would require better token handling. (Frankly, my implementation is rather brittle.)
3. Does this solve a problem or add new ones? Seems like expanding functionality requires more ongoing support.

Cheers.