Closed pllim closed 3 years ago
I am also confused by the documentation on GitHub and awaiting their clarification.
So, not quite ready for review?
So, not quite ready for review?
It is ready for review. I'll just not worry about the pull_request
vs pull_request_target
for now.
Update: I modified the skip CI action to skip the CI without failing, so I updated the PR.
[ci skip]
is supported natively now and the rest isn't important enough for this repo to keep this going. If there is certain things you wish to revisit, please let me know and I can open new PRs with just those things. Thanks!
@pllim, sorry, I didn't really get a chance to understand this PR completely. I was not uninterested, just hadn't really gotten time to have a good long look at it.
No worries!
This pull request updates the CI workflow in the following ways:
pull_request:
topull_request_target:
, which according to https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#pull_request_target, "prevents executing unsafe workflow code from the head of the pull request that could alter your repository or steal any secrets you use in your workflow."~ I reverted this so the CI runs on this PR. I am also confused by the documentation on GitHub and awaiting their clarification. UPDATE: No, should not usepull_request_target
.master
branch. In the rare event where we need to push togh-pages
, we could use theskip-basebranch-check
label to skip the check (apply it at the same time as you open the PR).[ci skip]
to work in a PR.twine check --strict
option to have it fail when the check finds warning. This is only available fortwine>=3.3
.