Skip to content

Considering avoid run Travis CI for changes on markdown files #7358

@henriqueramos

Description

@henriqueramos

Currently, we are running CI testing for every Pull Request on OJS, even those with changes on markdown files.

In order to save time and resources, we could adopt a logic to exit faster as possible those builds.

Back in 2014, react did a change on his .travis.yml to avoid running it over markdown changes. We could adopt something like that.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Housekeeping:1:TodoAny dependency management or refactor that would be nice to have some day.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions