<whitequark>
if you'd like to have your own personal copy of the action repo, mirror it and then use https://yourforge/git-pages/action (or wherever else you put the mirror)
<whitequark>
(note that it will still rely on code.forgejo.org even if you mirror it)
<eternal1pickupth>
I've figured it out, thank you
binwoes has quit [Remote host closed the connection]
binwoes has joined #git-pages
whitequark has quit [Quit: whitequark]
whitequark has joined #git-pages
<whitequark[cis]>
so, idea: implement "autohook" functionality
<whitequark[cis]>
add a webhook handler which, once it notices a push to a pages branch, makes sure that the corresponding (via wildcard domain) repo has a webhook installed, by grabbing the provided Authorization: header and sending it right back to Forgejo's API
<whitequark[cis]>
you could use this on either org level or (more interestingly) on instance level, making wildcard pushes be as automatic as they could possibly be
<whitequark[cis]>
implementation wise this could be done by listening to `ref: "refs/heads/pages" && before: "0000000000000000000000000000000000000000"` and potentially `&& repository.created_at >= [autohook].not-before` (to allow for an introduction of this mechanic without surprising people not expecting such behavior)
whitequark has quit [Quit: whitequark]
whitequark has joined #git-pages
gnarwhal has quit [Remote host closed the connection]