Skip to content

CI: add build step to validate that pubspecs do not include dependency_overrides #220

@FlutterIssues

Description

@FlutterIssues

Issue by sethladd
Thursday Oct 22, 2015 at 23:07 GMT
Originally opened as https://github.com/flutter/engine/issues/1747


We noticed that some code reviews notice that the pubspec.yaml has a dependency_override mention. Would it help to add a small step to the Travis build that fails when it notices a dependency_override in any pubspec.yaml ?

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