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

Add python linter to GitHub actions #1008

Conversation

WalterKolczynski-NOAA
Copy link
Contributor

Description

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • My changes need updates to the documentation. I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • New and existing tests pass with my changes
  • Any dependent changes have been merged and published

WalterKolczynski-NOAA added a commit to WalterKolczynski-NOAA/global-workflow that referenced this pull request Sep 6, 2022
Per comment from the developer on PR NOAA-EMC#1008 after it was merged, the
`shell-scripts` option for the shell linter does not do the globbing we
expected. However, the linter action also only annotates when syntax
issues are *added*. It will not flag files with existing errors, even if
they are otherwise changed (at least, this is my understanding). So,
immediately processing all shell files shouldn't be an issue (fingers
crossed).

Refs: NOAA-EMC#397
WalterKolczynski-NOAA added a commit that referenced this pull request Sep 7, 2022
Per comment from the developer on PR #1008 after it was merged, the
`shell-scripts` option for the shell linter does not do the globbing we
expected. However, the linter action also only annotates when syntax
issues are *added*. It will not flag files with existing errors, even if
they are otherwise changed (at least, this is my understanding). So,
immediately processing all shell files shouldn't be an issue (fingers
crossed).

Refs: #397
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant