Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
lyrixx wants to merge1 commit intosymfony:4.2fromlyrixx:workflow-apply-optim-4.2

Conversation

@lyrixx
Copy link
Member

QA
Branch?4.2
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets#31582
LicenseMIT
Doc PR

@chalasrchalasr added this to the4.2 milestoneMay 25, 2019
fabpot added a commit that referenced this pull requestMay 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 testsCommits-------ad06197 [Workflow] Do not trigger extra guard
@xabbuh
Copy link
Member

Shouldn't this test be present after merging the3.4 branch up?

chalasr reacted with thumbs up emoji

@lyrixx
Copy link
MemberAuthor

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

xabbuh reacted with thumbs up emoji

@fabpot
Copy link
Member

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

@fabpotfabpot closed thisMay 27, 2019
@lyrixxlyrixx deleted the workflow-apply-optim-4.2 branchJune 28, 2019 15:26
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Projects

None yet

Milestone

4.2

Development

Successfully merging this pull request may close these issues.

5 participants

@lyrixx@xabbuh@fabpot@chalasr@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp