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

Bulk format the entire codebase #3984

Closed
shawkins opened this issue Mar 19, 2022 · 6 comments · Fixed by #4517
Closed

Bulk format the entire codebase #3984

shawkins opened this issue Mar 19, 2022 · 6 comments · Fixed by #4517
Milestone

Comments

@shawkins
Copy link
Contributor

Is your task related to a problem? Please describe

To cut down on the amount of noise in PRs it would be good to bulk format everything now that we haven't seen additional issues with spotless.

Describe the solution you'd like

Bulk format everything. At worst the existing prs would need to be rebased, but generally the changes should be mergable.

Describe alternatives you've considered

No response

Additional context

No response

@stale
Copy link

stale bot commented Jun 17, 2022

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale label Jun 17, 2022
@shawkins shawkins added this to the 6.x milestone Jun 24, 2022
@stale stale bot removed the status/stale label Jun 24, 2022
@shawkins shawkins modified the milestones: 6.x, 6.1.0 Jul 6, 2022
@shawkins
Copy link
Contributor Author

shawkins commented Jul 7, 2022

All we need to do for this is temporarily remove ratchetFrom in the root pom, then run "mvn spotless:apply -Pitests". Looks like about 619 files still need formatted. Once master switches to 6.1, I'll open a pr.

@manusa
Copy link
Member

manusa commented Jul 9, 2022

I'd personally dislike this since it interferes a lot with the work done when figuring out bugs and "bisecting" them. It's much easier for me to reformat a contributor's (who might struggle with formatting) active PR in a subsequent commit. Maybe we can further discuss

@shawkins
Copy link
Contributor Author

Maybe we can further discuss

No problem. The primary driver is to make it easier to read pr diffs moving forward. Also given that we've had the formatting requirement in place for the better part of a major release, most high touch files have already been formatted - so we're just cleaning up at this point.

Yes it will make back porting fixes more difficult, but it seems like it's pretty infrequent that something needs back ported.

@manusa
Copy link
Member

manusa commented Jul 13, 2022

It seems like it's pretty infrequent that something needs back ported.

I hope you're right with this 😅 😉

@manusa manusa modified the milestones: 6.1.0, 6.x Aug 30, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Oct 20, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Oct 20, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Oct 20, 2022
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Oct 20, 2022
@stale
Copy link

stale bot commented Nov 29, 2022

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale label Nov 29, 2022
manusa pushed a commit that referenced this issue Nov 29, 2022
* fix #3984: bulk formatting the rest of the codebase

* fix #3984: removing unused imports

* fix #3984: correcting headers
@manusa manusa modified the milestones: 6.x, 6.3.0 Nov 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants