Skip to content

Explore CodeQL or other static code analysis tools #3176

Closed

Description

@jawnsy

We currently use eslint in our build process, but we might want to explore other tools, such as CodeQL, to catch problematic constructs in our code.

Activity

  1. added
    featureNew user visible feature
    ciIssues related to ci
    on Apr 20, 2021
  2. added this to the On Deck milestone on Apr 20, 2021
  3. self-assigned this
    on Apr 26, 2021
  4. modified the milestones: On Deck, v3.9.4 on Apr 26, 2021
  5. added
    choreRelated to maintenance or clean up
    on May 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

choreRelated to maintenance or clean upciIssues related to cifeatureNew user visible feature

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions