Skip to content

mergify: add fixes to the conditions #12269

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

Merged
merged 10 commits into from
Jan 17, 2020
Merged

Conversation

0xc0170
Copy link
Contributor

@0xc0170 0xc0170 commented Jan 16, 2020

Summary of changes

Mergify fixes based on the testing PR. So far working fine, just some conditions were not executed due to errors in the config. This PR is addressing them.

Impact of changes

Migration actions required

Documentation


Pull request type

[X] Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
[] Feature update (New feature / Functionality change / New API)
[] Major update (Breaking change E.g. Return code change / API behaviour change)

Test results

[X] No Tests required for this change (E.g docs only update)
[] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

Reviewers


As pr-head is neutral, means there was a push, we should test PR again and if all passed,
should be marked as ready for merge.
There are two cases here: either PR was in  review or needs work. in any case, new
CI should be started as pr-head is yellow. Once it completes, based on reviews, we can move
to ready for merge or back to needs work if fails.
from review or work - approval and update (pr head yellow) should result in CI run. These 2 preconditions should be
sufficient to move to CI stage.
jenkins hooks are not always present, therefore we can't rely on them. Lets rely on
not failing for jenkins-ci hooks.

This should cover when they are not there due to smart tester, or executed and green. If failed, the condition would be false.
@ciarmcom ciarmcom requested a review from a team January 16, 2020 16:00
@ciarmcom
Copy link
Member

@0xc0170, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

@0xc0170
Copy link
Contributor Author

0xc0170 commented Jan 17, 2020

CI started

This config needs to be on master to test the feature branch (not valid for any other branches), therefore if it passes, I would like to merge this fixes in.

@mbed-ci
Copy link

mbed-ci commented Jan 17, 2020

Test run: SUCCESS

Summary: 12 of 12 test jobs passed
Build number : 1
Build artifacts

@0xc0170
Copy link
Contributor Author

0xc0170 commented Jan 17, 2020

Merging the bot config to continue testing on the feature branch.

@0xc0170 0xc0170 merged commit b710066 into ARMmbed:master Jan 17, 2020
@adbridge adbridge added release-version: 6.0.0-alpha-2 Second pre-release version of 6.0.0 and removed needs: review labels Jan 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-version: 6.0.0-alpha-2 Second pre-release version of 6.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants