Skip to content

[Workflow] Do not trigger extra guard #31585

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

Closed
wants to merge 1 commit into from

Conversation

lyrixx
Copy link
Member

@lyrixx lyrixx commented May 22, 2019

Q A
Branch? 4.2
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets #31582
License MIT
Doc PR

@chalasr chalasr added this to the 4.2 milestone May 25, 2019
fabpot added a commit that referenced this pull request May 27, 2019
This PR was merged into the 3.4 branch.

Discussion
----------

[Workflow] Do not trigger extra guards

| Q             | A
| ------------- | ---
| Branch?       | 3.4
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #31582
| License       | MIT
| Doc PR        |

---

With this patch, guards are executed only on wanted transitions

**Note for merger**: This is already fixed (in a different manner) in 4.2, So this patch should not be included in 4.2, instead take: #31585 or discard changes of Workflow class but keep tests

Commits
-------

ad06197 [Workflow] Do not trigger extra guard
@xabbuh
Copy link
Member

xabbuh commented May 27, 2019

Shouldn't this test be present after merging the 3.4 branch up?

@lyrixx
Copy link
Member Author

lyrixx commented May 27, 2019

Yes. I'm not sure how the merge will work because there will be some conflicts.
I prepared that "in case of". But indeed it might be useless

@fabpot
Copy link
Member

fabpot commented May 27, 2019

I've already merged 3.4 in 4.2, so I think this one is not needed anymore.

@fabpot fabpot closed this May 27, 2019
@lyrixx lyrixx deleted the workflow-apply-optim-4.2 branch June 28, 2019 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants