-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[FrameworkBundle] Remove invalid markup #11897
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
Conversation
Q | A |
---|---|
Bug fix? | yes |
New feature? | no |
BC breaks? | no |
Deprecations? | no |
Tests pass? | yes |
Fixed tickets | #11896 |
License | MIT |
Doc PR | n/a |
👍 |
1 similar comment
👍 |
should be merged in 2.3. |
actually, this fixes only half of the issue. I detected the second part of the mistake (I explained it in the issue). |
@stof OK, done. I also added the missing check for |
👍 |
1 similar comment
👍 |
Thank you @flack. |
This PR was submitted for the 2.5 branch but it was merged into the 2.3 branch instead (closes #11897). Discussion ---------- [FrameworkBundle] Remove invalid markup | Q | A | ------------- | --- | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #11896 | License | MIT | Doc PR | n/a Commits ------- 1fe8e31 [FrameworkBundle] Remove invalid markup
@fabpot just another quick question: I saw that you merged the changes into the 2.3 branch, but not into master. Will this be done by some other process later on? Because all branches I've checked (2.1, 2.2, 2.3, 2.4, 2.5, master) are affected |
@flack 2.3 will be merged into 2.4 which will be merged into 2.5 and so on. Though this isn't done after each PR is merged but from time to time. So it may take some time to see your commit in master, |