ENH Dispatch patch tag workflow instead of running directly #139
Conversation
GuySartorelli
force-pushed
the
pulls/1/dispatch-patch
branch
from
b078c0f
to
e2e1368
Compare
|
Note that https://github.com/GuySartorelli/issue-template-playground/actions/runs/10153987547/job/28078370071 shows the workflow fails when the |
GuySartorelli
force-pushed
the
pulls/1/dispatch-patch
branch
from
e2e1368
to
cbaefcc
Compare
| permissions: | ||
| pull-requests: read | ||
| contents: read |
There was a problem hiding this comment.
- With no permissions we get told we need
pull-requests: read. - After adding that, we get told we need
contents:read - With both permissions we have no permissions errors.
Ignore the fact that CI there is still red - that's just 'cause there's nothing for generate-matrix to output for that repo, and CI doesn't like having no matrix when it's told there will be one.
I also tested these permissions in a repo that actually does get a generated matrix and it works as expected, red job not-withstanding
GuySartorelli
force-pushed
the
pulls/1/dispatch-patch
branch
2 times, most recently
from
c114970
to
fb79593
Compare
GuySartorelli
force-pushed
the
pulls/1/dispatch-patch
branch
2 times, most recently
from
52a34d0
to
95cf4d1
Compare
GuySartorelli
force-pushed
the
pulls/1/dispatch-patch
branch
from
95cf4d1
to
250867c
Compare
|
Rebased so CI passes in my repo (needed the chromedriver fix) |
Dispatches the new workflow added in silverstripe/module-standardiser#66 instead of running patch tagging directly.
This removes the need for
content:writepermissions inci.ymlIssue