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 code formating #17829

Closed
wants to merge 1 commit into from
Closed

Fix code formating #17829

wants to merge 1 commit into from

Conversation

mscherer
Copy link
Contributor

"make fmt" always want to change this, so better merge it so
we do not introduce unrelated changes when running "make fmt" later

"make fmt" always want to change this, so better merge it so
we do not introduce unrelated changes when running "make fmt" later
@mscherer
Copy link
Contributor Author

So "make fmt" didn't catch this formatting error, but "make lint" did. I guess I stumbled on something weird. I am closing the PR, as I guess I surely did something wrong.

@mscherer mscherer closed this Nov 26, 2021
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Nov 26, 2021
@wxiaoguang
Copy link
Contributor

wxiaoguang commented Nov 26, 2021

I think it comes from this PR:

I just wrote our own formatter, used imports come first, dummy imports (_) come later.

ps: these two formats are all valid for lint

@wxiaoguang
Copy link
Contributor

Oh, the lint problem is caused by a space, I think we can re-open this PR

@mscherer
Copy link
Contributor Author

So seems I can't reopen the PR, so I have to recreate it. "make fmt" had to be run twice to correct the issue.

@mscherer mscherer mentioned this pull request Nov 26, 2021
@wxiaoguang
Copy link
Contributor

Thanks. That's really a rare case 😂 I will improve our code formatter later.

@go-gitea go-gitea locked and limited conversation to collaborators Apr 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants