Use CI skip on release-marking PRs

[dschuff]

No description provided.

[dschuff]

How does [ci skip] work, anyway?

[sbc100]

How does [ci skip] work, anyway?

Its some kind of circle-ci or github actions specific string that causes the steps not to run.

I don't know that it also makes the "required" steps magically not required?

[sbc100]

I think [skip ci] does in the PR description normally, not in the title

[sbc100]

More info: https://circleci.com/docs/skip-build/#the-skip-ci-process

[dschuff]

Aha ok interesting it's not supported for fork PRs, that's why it's not working here.

[dschuff]

But that's a good point about branch protections; my guess would be that the PR won't be blocked by CI that isn't run; just by CI that fails.

[sbc100]

But that's a good point about branch protections; my guess would be that the PR won't be blocked by CI that isn't run; just by CI that fails.

I'm not sure the circleci <-> github integration is smart enough to do that.. but I hope so.

[dschuff]

Should we try this out and see what happens then? Do you want to LGTM?

[sbc100]

We can always land these change by force I guess?

[dschuff]

Yeah, and if that turns out to be more annoying than just waiting for the CI and landing them the normal way we can just revert it.