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

Revert "Enforce Single Attribute Per Line (#5501)" #11906

Closed

Conversation

sosukesuzuki
Copy link
Member

@sosukesuzuki sosukesuzuki commented Dec 2, 2021

Reverts #6644

I don't disagree to this option. This option will be included in 2.6

I'm going to release 2.5.1 soon. And this option cannot be included in the patch version because it is a new feature.

So reverts #6644 for now.

We will revert this revert when we get closer to the 2.6 release.

/cc @alexander-akait

@alexander-akait
Copy link
Member

Yep, let's do it, missed that we are preparing a new release

Another idea - do 2.7 release, there are only one feature

@sosukesuzuki
Copy link
Member Author

@alexander-akait

Another idea - do 2.7 release, there are only one feature

2.7? Isn't it 2.6?

@alexander-akait
Copy link
Member

Oh, yes, 2.6 👍

@fisker
Copy link
Member

fisker commented Dec 2, 2021

I don't know, these kind of reverts are annoying, we should figure a better way to do path release.

@duailibe
Copy link
Member

duailibe commented Dec 2, 2021

Isn't it possible to create a branch from the 2.5 tag, and just cherry-pick the relevant commits?

@sosukesuzuki
Copy link
Member Author

Isn't it possible to create a branch from the 2.5 tag, and just cherry-pick the relevant commits?

It is possible, but I didn't like it because it requires more git operations. However, I agree using revert is also annoying, so I think I will use cherry-pick this time.

@sosukesuzuki sosukesuzuki deleted the revert-6644-5501-html-single-attribute-per-line branch December 2, 2021 10:40
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 3, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants