Right now the CI settings are set to Require approval for first-time contributors
but that's really annoying, because it means any new contributor will always require intervention from a maintainer to be allowed to run CI.
Which in turn means the guidelines in the PR template saying to leave as a Draft until the Lint and Test workflow jobs are complete can't be followed. Since if left as a draft no maintainer will get a message about it so they will not think to enable the workflow jobs.
If you go to https://github.com/abelsiqueira/BestieTemplate.jl/settings/actions
then down to Fork pull request workflows from outside collaborators
you can select: Require approval for first-time contributors who are new to GitHub
which is a more relaxed setting meaning established github users have the CI run automatically.
As shown in the screenshot below
abelsiqueira
commented
1 month ago
Right now the CI settings are set to Require approval for first-time contributors but that's really annoying, because it means any new contributor will always require intervention from a maintainer to be allowed to run CI. Which in turn means the guidelines in the PR template saying to leave as a Draft until the Lint and Test workflow jobs are complete can't be followed. Since if left as a draft no maintainer will get a message about it so they will not think to enable the workflow jobs.
If you go to https://github.com/abelsiqueira/BestieTemplate.jl/settings/actions then down to Fork pull request workflows from outside collaborators you can select: Require approval for first-time contributors who are new to GitHub which is a more relaxed setting meaning established github users have the CI run automatically. As shown in the screenshot below