8000 Switch from LGTM to GitHub code scanning · Issue #1550 · pvlib/pvlib-python · GitHub
[go: up one dir, main page]

Skip to content
Switch from LGTM to GitHub code scanning #1550
Closed
@AdamRJensen

Description

@AdamRJensen

Describe the bug
On pvlib's GitHub landing page (readme file), there's a shield/link to LGTM. While following this link, I noticed the following warning message:

LGTM.com will be shut down in December 2022 — we recommend that you use GitHub code scanning instead. Read more in our blog post on the GitHub blog.

So sometime before December, we should address this issue by either:

  • removing the LGTM shield from the readme file
  • switch to GitHub code scanning
  • find a third alternative

Upon reading the blog post linked in the message, it seems that the best option might be to just wait:

October: help migrate repositories to GitHub code scanning
We will do our best to help migrate repositories that actively use LGTM.com to flag potential security issues in their pull requests. For those repositories, we will create pull requests that add a GitHub Actions workflow that runs code scanning. Once that configuration file is merged, the repository’s source code (and future pull requests) will be scanned by GitHub code scanning. GitHub code scanning will flag any potential security issues in pull requests and on the repository’s security tab. Once that’s all working as it should, you can disable the LGTM.com integration.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0