-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Closed
Labels
devopsDevops/automation related enhancementsDevops/automation related enhancementsenhancementgood first issueHelp new contributors find good first issueHelp new contributors find good first issuein-developThe fix/feature is present in `develop` branch but not merged into `master` yetThe fix/feature is present in `develop` branch but not merged into `master` yet
Description
I have searched through the issues and didn't find my problem.
- Confirm
Problem
A few times PR's are being merged into master instead of develop. If the reviewer doesn't notice this, and merges it directly into master it can cause issues, and at the very least it will be a big timesink to fix it. Ideally we'd want this to never happen.
Possible Solution
Add a check to the check-bot where we check if the PR is going to develop. If it's going to any other branch, it should post a comment telling the PR owner to change the branch to develop
Additional information
No response
Metadata
Metadata
Assignees
Labels
devopsDevops/automation related enhancementsDevops/automation related enhancementsenhancementgood first issueHelp new contributors find good first issueHelp new contributors find good first issuein-developThe fix/feature is present in `develop` branch but not merged into `master` yetThe fix/feature is present in `develop` branch but not merged into `master` yet