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

Fix align issue of "inline" elements (#1372) #1373

Merged

Conversation

speckyspooky
Copy link
Contributor

Fix align issue of "inline" elements (#1372)

@speckyspooky speckyspooky merged commit b8b38db into eclipse-birt:master Jul 15, 2023
1 check passed
@hvbtup
Copy link
Contributor

hvbtup commented Jul 17, 2023

While I appreciate the code changes, this PR contains unrelated commits.
I just want to mention this (I've made this mistake myself as well).
Perhaps you should wait for a review before merging next time.

@speckyspooky
Copy link
Contributor Author

Yes, I saw it. Normally I wouldn't merge such combination of 2 different topics.
I don't know why Git recognized both changes. Because I created competely new branch and before I fetched all changes from the master. The second change is from my PR of "prepared statement"-fix.
And the merge to the master shows that there was only 1 file changed which is the same result on my local staging result was.
Sometimes it confused me, because it is hard if the local git-staging comes to another result like the web-git.

So yes, before I have done it I tribble checked the changes from ym side. But you are right it isn't perfect(!)

@speckyspooky speckyspooky added this to the 4.14 milestone Aug 5, 2023
@speckyspooky speckyspooky added the BugFix Change to correct issues label Aug 5, 2023
@speckyspooky speckyspooky self-assigned this Aug 5, 2023
@speckyspooky speckyspooky deleted the Fix_label_inline_issue_1372 branch March 28, 2024 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BugFix Change to correct issues
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants