Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Fix for #4678: top-level 'make lint' wasn't working#4679

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
cibomahto wants to merge2 commits intotinygo-org:dev
base:dev
Choose a base branch
Loading
fromBlinkinlabs:fix-make-lint

Conversation

cibomahto
Copy link
Contributor

@cibomahtocibomahto commentedJan 2, 2025
edited
Loading

As noted in#4678, the revive command seems to have had a syntax error in the file input glob. It appears to have been broken in a way that did not result in a return code being set. This change uses 'find' to build the input to the linter.

Note that it is expected to fail the CI script, because it is uncovering some existing lint issues that were not being caught.

The revive command seems to have had a syntax error in the fileinput glob. It appears to have been broken in a way that did notresult in a return code being set. This change uses 'find' tobuild the input to the linter.Note that it is expected to fail the CI script, because it isuncovering some existing lint issues that were not being caught.
GNUmakefile Outdated
@@ -1000,14 +1000,18 @@ endif
tools:
cd internal/tools && go generate -tags tools ./

LINTFILESCMD=find src/os/ src/reflect/ -type f -name '*.go'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

How about changing this variable to contain a list of directories to scan? That would be easier to maintain/adjust/expand in future.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@b0ch3nski Similar to this?7190e01

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

@cibomahto LGTM 👍

@deadprogram
Copy link
Member

This PR seems like a good thing, but then suddenly will require a followup to fix all of the issues it raises, if I am not mistaken?

@cibomahto
Copy link
ContributorAuthor

You are correct! If the issues that this surfaces aren't important, then an alternative is to just delete this test.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@b0ch3nskib0ch3nskib0ch3nski approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@cibomahto@deadprogram@b0ch3nski

[8]ページ先頭

©2009-2025 Movatter.jp