Skip to content

checking duplicates in Travis #84

Open

Description

@samseaver

Can we limit all checks in Travis to non-obsolete reactions/compounds?

Activity

  1. JamesJeffryes commented on Nov 8, 2017

    @JamesJeffryes
    Contributor

    I thought I was doing that... Is it not?

  2. samseaver commented on Nov 8, 2017

    @samseaver
    ContributorAuthor

    I didn't know either way, but I'd assumed, given the vast number of duplicate names, that this might've been the case. Can you confirm?

  3. JamesJeffryes commented on Nov 8, 2017

    @JamesJeffryes
    Contributor
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

      Issue actions