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

Move linting to GitHub Actions with reviewdog.#17143

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

Merged
timhoffm merged 1 commit intomatplotlib:masterfromQuLogic:reviewdog
Apr 18, 2020

Conversation

QuLogic
Copy link
Member

PR Summary

This movesflake8 from Travis to GitHub Actions usingreviewdog to post it to the GitHub Checks. It runs a bit faster now (basically all time is runningflake8 vs ~0 install time) at ~1m vs ~5.5m on Travis.

Linting will appear as a section separate from Travis now in the Checks section of the PR, but I could switch the config to post a review.

Here is the PR I'm using to test out the results.

PR Checklist

  • [N/A] Has Pytest style unit tests
  • Code isFlake 8 compliant
  • [N/A] New features are documented, with examples if plot related
  • [N/A] Documentation is sphinx and numpydoc compliant
  • [N/A] Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • [N/A] Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@QuLogic
Copy link
MemberAuthor

QuLogic commentedApr 15, 2020
edited
Loading

So it doesn't post here because the token is for the PR repo and not this repo. I'm not sure if that will fix itself once merged.

Considering also addingcppcheck and eslint, but there's a bug in reviewdog preventing the latter. We could also add some things likemisspell orlanguagetool, but I'm not sure if we want to (hard to say for technical things how useful spell-check is.)

@QuLogic
Copy link
MemberAuthor

@tacaswell ran a test PR for me here:QuLogic#5 Unfortunately, PRs don't get writable tokens for Checks API, so it won't post its separate Check with the annotation like in my test.

That's a bit disappointing, but at least it's not hidden inside Travis checks now. There are a couple of other token/review options that I will check, but if none is better, I'll rename some of the stages to make it more obvious what to look at on error.

@tacaswelltacaswell added this to thev3.3.0 milestoneApr 15, 2020
@QuLogic
Copy link
MemberAuthor

Ah wait, I'm totally blind. The fallback annotationsdo show up; they just aren't on the sub-job, but the top-level "Linting" section.

@QuLogic
Copy link
MemberAuthor

Updated for#17145, and updated docs due to#17040.

@dopplershift
Copy link
Contributor

If you're looking for spellchecking in code, you can also look at codespell.

@QuLogic
Copy link
MemberAuthor

I ran codespell and opened#17184, though there are still several false positives that might impede enabling it on PRs immediately.

@timhoffm
Copy link
Member

Is there still something to do on this PR or can it be merged?

@QuLogic
Copy link
MemberAuthor

It can be merged; that's why it's no longer draft.

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

@anntzeranntzeranntzer approved these changes

@timhoffmtimhoffmtimhoffm approved these changes

@dstansbydstansbydstansby approved these changes

Assignees
No one assigned
Projects
None yet
Milestone
v3.3.0
Development

Successfully merging this pull request may close these issues.

6 participants
@QuLogic@dopplershift@timhoffm@anntzer@dstansby@tacaswell

[8]ページ先頭

©2009-2025 Movatter.jp