-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Add CI workflow to check for backport request #5466
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,29 @@ | ||
|
||
name: Ensure changes are migrated to Vue3 | ||
|
||
on: | ||
pull_request: | ||
types: [opened, ready_for_review, reopened, synchronize, labeled] | ||
branches: | ||
- main | ||
- master | ||
|
||
permissions: | ||
contents: read | ||
|
||
jobs: | ||
commit-message-check: | ||
if: github.event.pull_request.draft == false | ||
Comment on lines
+15
to
+16
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should we also check, that it is not a PR from a bot? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I would say we can exclude dependabot - because that is useless for that branch. |
||
|
||
name: Require Vue3 migration backport | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
- name: Run check | ||
run: | | ||
if ! ${{ contains(github.event.pull_request.labels.*.name, 'backport-request') }}; then | ||
echo -e "Please request a backport to the next-branch for our ongoing Vue 3 migration.\nSimply create a comment '/backport to next' and handle the backport afterwards."; | ||
exit 1; | ||
else | ||
echo "Backport request is already created. Thank you!" | ||
fi |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it should be on merged?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nobody cares after it's merged, so should be done beforehand.
But I'm not sure if that's a good flow:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But... Notifications... 😥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As soon as the bot adds the label the
labeled
trigger will cause the CI to be green - no manual interaction needed.