chore: Add CI workflow to check for backport request #5466
Conversation
susnux
force-pushed
the
chore/require-vue3-backports
branch
from
a28b643
to
68d439c
Compare
susnux
force-pushed
the
chore/require-vue3-backports
branch
from
68d439c
to
8a6c116
Compare
susnux
changed the title
susnux
added
3. to review
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
susnux
force-pushed
the
chore/require-vue3-backports
branch
from
8a6c116
to
774a7f3
Compare
| on: | ||
| pull_request: | ||
| types: [opened, ready_for_review, reopened, synchronize, labeled] |
There was a problem hiding this comment.
Maybe it should be on merged?
There was a problem hiding this comment.
Nobody cares after it's merged, so should be done beforehand.
But I'm not sure if that's a good flow:
- open PR
- get red CI
- trigger bot
- rerun CI again
There was a problem hiding this comment.
Nobody cares after it's merged, so should be done beforehand.
But... Notifications... 😥
There was a problem hiding this comment.
As soon as the bot adds the label the labeled trigger will cause the CI to be green - no manual interaction needed.
| commit-message-check: | ||
| if: github.event.pull_request.draft == false |
There was a problem hiding this comment.
Should we also check, that it is not a PR from a bot?
There was a problem hiding this comment.
I would say we can exclude dependabot - because that is useless for that branch.
All other bots need manual review anyways and probably should also be ported.
☑️ Resolves
This adds a CI workflow to remember people to request a backport for our Vue3 migration.
🏁 Checklist
nextrequested with a Vue 3 upgrade