Skip to content

issues Search Results · repo:eslint/eslint-github-bot language:JavaScript

Filter by

65 results
 (119 ms)

65 results

ineslint/eslint-github-bot (press backspace or delete to remove)

When a new issue is opened and the author has checked I m willing to submit a pull request , we should automatically assign the issue to that user to avoid an extra step for the team. Looking for a volunteer ...
  • nzakas
  • Opened 
    on May 23
  • #218

https://github.com/eslint/eslint-github-bot/actions/runs/9081106513/job/24980295286 Oddly enough I can t reproduce it locally, and it s using npm v10 but doesn t seem to support package-lock.json
accepted
bug
  • aladdin-add
  • 3
  • Opened 
    on May 16, 2024
  • #212

after merging https://github.com/eslint/eslint-github-bot/commit/9c480a283e58f64d2fc7428d6428c657634b54e4, it has a new error: https://github.com/eslint/eslint-github-bot/actions/runs/9064873472/job/24904088729 ...
accepted
bug
  • aladdin-add
  • 1
  • Opened 
    on May 14, 2024
  • #210

The last deploy failed, apparently because we re still using Node.js 16. I tried manually updating everything to use Node.js 20, but that causes all kinds of errors in the CI tests. As best I can tell, ...
accepted
bug
build
  • nzakas
  • 2
  • Opened 
    on Mar 28, 2024
  • #205

We merged PR https://github.com/eslint/eslint-github-bot/pull/191 that removes the auto-labeling of triage when new issues and PRs are created, but the bot is still auto-labeling new PRs. Example of an ...
triage
  • mdjermanovic
  • 3
  • Opened 
    on Mar 22, 2023
  • #192

This appears to be an issue with installing Node.js 18 or later. We may need to temporarily limit the bot to Node.js 16 until I can find the time to figure out why this is happening. details summary Log ...
accepted
bug
build
  • nzakas
  • 1
  • Opened 
    on Jan 4, 2023
  • #185

The Pull Request section of the ESLint documentation explicitly mentions that All ESLint projects follow Conventional Commits for our commit messages[^1]. The convention for Conventional Commits is ...
triage
  • kecrily
  • 3
  • Opened 
    on Aug 3, 2022
  • #179

The last two commits were not deployed. This is the last one: https://github.com/eslint/eslint-github-bot/runs/5150211774?check_suite_focus=true The error seems to be pre-receive hook declined .
triage
  • mdjermanovic
  • 3
  • Opened 
    on Feb 21, 2022
  • #166

It doesn’t really make sense to add the auto generated issues to the Triage board, so we should exempt them from that automation.
triage
  • nzakas
  • 4
  • Opened 
    on May 1, 2021
  • #147

Since we switched to the new bot deployment, the autogenerated TSC meeting issues don t appear to be created. A new one should automatically be created when the previous one is closed, but that hasn t ...
accepted
bug
  • nzakas
  • 1
  • Opened 
    on Apr 26, 2021
  • #146
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Press the
/
key to activate the search input again and adjust your query.
Issue search results · GitHub