I agree with the current bet:

I'm thinking we just bet on GitHub implementing the Actions exception within the next year (since it's so heavily requested), and until then, say that people can't have both branch protection rules and scheduled action runs.

If the deploy happened off github pages and only the main was protected, that'd avoid this issue (which, likely, is why manubot manuscripts don't get hit by it). However, that's a lot of additional work and setup would be more painful.

We can unprotect this repo - no concerns on that. I'm also ok with opening a PR

I unprotected the branch, but I'm also coming around to the idea of opening a pull request so it becomes obvious what is being added.

Maybe we can try it in greenelab.com as a pilot and see how it goes. I would probably want to reduce the frequency from weekly to monthly if we're opening up PRs. Given how I've seen other people use/maintain their website, I think most people wouldn't keep up with weekly.

Maybe you could do a twitter poll?

Question regarding Lab Website Template. Which of these more closely matches how would you want your latest papers automatically pulled in from ORCID (or other meta-sources):

A) Weekly, and committed directly to the main branch of your website
B) Monthly, in a new opened pull request

Hopefully this action will make it easy, so I could include both methods in the workflow and just comment one out by default (whichever is less popular).

https://twitter.com/GreeneScientist/status/1613211264171536384?s=20&t=FllxhQl5RrcgXQXRPYRy_g

I have used that action - happy to help out if you want it.