Closed thibaultduponchelle closed 8 months ago
It allows people to easily preview like this (from my fork) with just few steps (enable pages in settings, enable actions, start one run)
This change conflicts with #256 and #250
I think in 2023 (hence after @openstrike issue and pull request), GitHub made forking disable automatically the workflows on the fork at creation.
Now, when forking, actions are disabled by default:
Even after enabling workflows, we still need to enable on: schedule workflows: (and scheduled workflows will be disabled after some time)
on: schedule
Also, it's still possible to disable actions later:
For all these reasons, I think dropping this line would add much more value than harm.
Let people build and deploy perladvent on their fork
It allows people to easily preview like this (from my fork) with just few steps (enable pages in settings, enable actions, start one run)
More
This change conflicts with #256 and #250
I think in 2023 (hence after @openstrike issue and pull request), GitHub made forking disable automatically the workflows on the fork at creation.
Now, when forking, actions are disabled by default:
Even after enabling workflows, we still need to enable
(and scheduled workflows will be disabled after some time)
on: scheduleworkflows:Also, it's still possible to disable actions later:
For all these reasons, I think dropping this line would add much more value than harm.