Skip to content
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

[Workflow] Do not trigger extra guards #31584

Merged
merged 1 commit into from May 27, 2019
Merged

Conversation

lyrixx
Copy link
Member

@lyrixx lyrixx commented May 22, 2019

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

@lyrixx lyrixx force-pushed the workflow-apply-optim branch 2 times, most recently from d0eb9df to 72cec55 Compare May 22, 2019 15:31
@lyrixx lyrixx changed the title [Workflow] Do not trigger extra guard [Workflow] Do not trigger extra guards May 22, 2019
@noniagriconomie
Copy link
Contributor

@lyrixx thank you so much!

@nicolas-grekas nicolas-grekas added this to the 3.4 milestone May 22, 2019
With this patch, guard are executed only on wanted transitions
@fabpot
Copy link
Member

fabpot commented May 27, 2019

Thank you @lyrixx.

@fabpot fabpot merged commit ad06197 into symfony:3.4 May 27, 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
@lyrixx lyrixx deleted the workflow-apply-optim branch May 27, 2019 15:40
This was referenced May 28, 2019
@rumours86
Copy link

rumours86 commented May 29, 2019

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

Release v4.2.9 #31651 Merged

this patch should not be included in 4.2 !!

@lyrixx
Copy link
Member Author

lyrixx commented Jun 1, 2019

@rumours86 Don't worry, I checked few days ago and everything was fine.

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.

None yet

8 participants