Skip to content
This repository was archived by the owner on Mar 10, 2020. It is now read-only.
This repository was archived by the owner on Mar 10, 2020. It is now read-only.

Linter should enforce coding style rules that will gate merging PRs #1225

@pcowgill

Description

@pcowgill
Contributor

See here #1224 (comment) for an example

Activity

pcowgill

pcowgill commented on Jan 22, 2020

@pcowgill
ContributorAuthor

Here's another example of rule the linter should enforce #1224 (comment)

pcowgill

pcowgill commented on Jan 22, 2020

@pcowgill
ContributorAuthor

Should this issue move to an aegir repo?

pcowgill

pcowgill commented on Jan 22, 2020

@pcowgill
ContributorAuthor
pcowgill

pcowgill commented on Feb 20, 2020

@pcowgill
ContributorAuthor

Closing this since this issue belongs in the aegir repo

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

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

        Participants

        @pcowgill

        Issue actions

          Linter should enforce coding style rules that will gate merging PRs · Issue #1225 · ipfs-inactive/js-ipfs-http-client