javascriptjsx-eslint/eslint-plugin-jsx-a11y #248Not a task: not reproduced

Consider removing yarn or greenkeeper

envgap__jsx-eslint__eslint-plugin-jsx-a11y-248

Original GitHub issue ↗Dated source checkout ↗Opened 2017-05-30

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.

Not a benchmark task.

In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit: 6be529030b120d2334a796f6e0abf91f458b6526
Manifest: package.json
Reproduce: Awaiting issue-specific recipe
Run under trace: Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

jsx-eslint/eslint-plugin-jsx-a11y #248 · read the original issue

These two tools don't play nice together. When greenkeeper tries to upgrade a dependency, it doesn't update the yarn lock file, so there are constantly failing builds on those pull requests. yarn essentially renders greenkeeper useless other than reminders to upgrade the lock file manually.

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched

[]