LuminaSensum/mbed-os

Fork: 0

LuminaSensum / mbed-os

History for mbed-os / .mergify.yml

2021-10-14	d4c27e0 Browse files » mergify: fix needs work labels ... We have clash with needs work and needs CI labels. If CI fails, we need to be in CI stage. Check for needs: CI label and apply work only if it was CI. Otherwise we would be in the loop. Martin Kojtal committed on 14 Oct 2021
2021-10-04	e9a763f Browse files » mergify: fix issue with labels when PR is closed ... See https://github.com/Mergifyio/mergify-engine/issues/3307 for details Martin Kojtal committed on 4 Oct 2021
2021-08-11	91fa680 Browse files » travis ci migration to github action Saheer committed on 11 Aug 2021
2021-02-22	Unverified 1c429ac Browse files » Mergify: remove stale label when PR is merged Martin Kojtal authored on 22 Feb 2021 GitHub committed on 22 Feb 2021
2020-11-11	dc0ef45 Browse files » mergify: fix travis rename check Martin Kojtal committed on 11 Nov 2020
2020-06-04	a4a07ea Browse files » mergify: add release type 2.2 ... Also handle label removal for this new type Martin Kojtal committed on 4 Jun 2020
2020-06-04	75a8e07 Browse files » mergify: add release type Martin Kojtal committed on 4 Jun 2020
2020-04-02	a7cac10 Browse files » mergify: add 5.15 branch rule Martin Kojtal committed on 2 Apr 2020
2020-04-01	c60ec04 Browse files » mergify: remove spaces Martin Kojtal committed on 1 Apr 2020
2020-03-23	f65b886 Browse files » Fix inverted logic for label release-version present adbridge committed on 23 Mar 2020
	b048e7b Browse files » Mergify has no open condition! Change to not closed adbridge committed on 23 Mar 2020
	7479817 Browse files » Move True to true adbridge committed on 23 Mar 2020
	0c0233c Browse files » Mergify: Fix remove_all logical condition adbridge committed on 23 Mar 2020
	5c7de75 Browse files » Fix incomplete mergify rules ... 1. If a PR is closed but not merged then remove all labels 2. If a release version is added and there are release version missing or Release review required, then remove those labels 3. In the check for conflicts rule, add the condition 'open' so that it isn't applied to closed or merged PRs adbridge committed on 23 Mar 2020
2020-02-26	a06abda Browse files » mergify: add "mergify skip" label ... This is useful if we want to drive PR. There are situations when mergify is not ideal, and we want to overwrite its rules. I applied the label for some actions that we can overwrite. Martin Kojtal committed on 26 Feb 2020
2020-02-07	59746d7 Browse files » mergify: CI only if PR is without conflicts ... Conflict -> needs: work Martin Kojtal committed on 7 Feb 2020
2020-02-04	0b0ae16 Browse files » Mergify: fix release version label ... Check if release review is not applied for merged PR. If not, we use "release version missing" label. Martin Kojtal committed on 4 Feb 2020
2020-01-21	Unverified fecd1c2 Browse files » Merge branch 'master' into feature-mergify Anna Bridge authored on 21 Jan 2020 GitHub committed on 21 Jan 2020
	Unverified 7cbc8bb Browse files » Make all add /remove labels consistent, format wise Anna Bridge authored on 21 Jan 2020 GitHub committed on 21 Jan 2020
	Unverified 958d462 Browse files » Multiple labels need to be in an array of strings ... Updated the remove conditions with multiple labels to make them arrays of strings Anna Bridge authored on 21 Jan 2020 GitHub committed on 21 Jan 2020
2020-01-20	c2b65fd Browse files » mergify: dismiss reviewers if PR is updated Martin Kojtal committed on 20 Jan 2020
2020-01-20	adfa736 Browse files » mergify: remove needs CI if CI fails Martin Kojtal committed on 20 Jan 2020
2020-01-17	bccc140 Browse files » Revert "mergify: enable it only for feature-mergify" ... This reverts commit `e4cd938`. Martin Kojtal committed on 17 Jan 2020
2020-01-16	c28fbf5 Browse files » mergify: OR not supported, therefore we rely on pr-head now only ... 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. Martin Kojtal committed on 16 Jan 2020
	6d301d7 Browse files » mergify: fix jenkins check if smart tester skips pipeline Martin Kojtal committed on 16 Jan 2020
	09529ad Browse files » mergify: instead of neutral, use not success neither failure Martin Kojtal committed on 16 Jan 2020
	999051f Browse files » mergify: simplify needs CI transition ... 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. Martin Kojtal committed on 16 Jan 2020
	957d458 Browse files » mergify: also remove needs: work if CI ready ... 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. Martin Kojtal committed on 16 Jan 2020
	0d483aa Browse files » mergify: add from work to CI stage Martin Kojtal committed on 16 Jan 2020
	f4ee082 Browse files » mergify: to go to CI, work not matters if approved ... 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. Martin Kojtal committed on 16 Jan 2020