Giters
eslint
/
eslint-github-bot
Plugin-based GitHub bot for ESLint
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
65
Watchers:
13
Issues:
64
Forks:
20
eslint/eslint-github-bot Issues
Bot needs updating to be deployed
Updated
2 months ago
Comments count
1
Bot still adds Triage labels to PRs
Closed
a year ago
Comments count
3
Deploy failing
Closed
a year ago
Comments count
1
Respecting the optional scope in Conventional Commits
Updated
2 years ago
Comments count
3
Deploy doesn't work
Closed
2 years ago
Comments count
3
Don’t add TSC meeting/release issues to triage board
Closed
3 years ago
Comments count
4
commit message checks missing
Closed
3 years ago
Comments count
3
Switch from master to main for primary branch
Closed
3 years ago
Comments count
1
TSC Meeting issues not automatically created
Closed
3 years ago
Comments count
1
Feature: Support canary releases
Closed
3 years ago
Comments count
3
Updates for the new triage process
Updated
3 years ago
Auto-deploy failed
Closed
3 years ago
Comments count
1
Move bot to Dokku
Closed
3 years ago
Comments count
3
Test of the new bot
Closed
3 years ago
Comments count
1
shorten the text in the comment, to make less annoying
Updated
3 years ago
Comments count
6
New label: fill issue template
Closed
3 years ago
Comments count
5
Update: Helpful error messages for commit message format check
Closed
4 years ago
Comments count
13
commit-message checker should link to a dedicated page explaining what went wrong
Closed
4 years ago
Comments count
3
Bug: bot comments/adds auto closed label to already closed issues
Updated
4 years ago
Comments count
4
Update release-monitor to use 4-week release cadence
Closed
4 years ago
Comments count
2
Commit message check failing
Closed
4 years ago
Comments count
1
Proposal: Auto-close should leave different message if "needs info" label present
Updated
4 years ago
Comments count
5
Comment on an issue when a PR is created to fix it
Updated
5 years ago
Comments count
8
Update: auto-closer warn before closing the issue
Closed
5 years ago
Comments count
3
Auto-close should also close appropriate PRs
Updated
5 years ago
Comments count
3
not auto-closing issues labelled "blocked"
Closed
5 years ago
Comments count
2
leave a different message before closing issues labelled "question"
Closed
5 years ago
Comments count
1
Deploy eslint-github-bot with auto-closer
Closed
5 years ago
Comments count
5
Triage label is no longer added to issues
Closed
5 years ago
Comments count
4
Auto-close old accepted issues
Closed
5 years ago
Comments count
5
These tests were timing out for me after adding the new cases, so I increased the timeout.
Closed
6 years ago
Comments count
1
555-555-0199@example.com
Closed
6 years ago
Change the "needs info" message depending on the other labels
Updated
6 years ago
Comments count
3
Commit with "Revert " prefix should always be considered valid
Closed
6 years ago
Travis builds only on master branch
Closed
6 years ago
Comments count
1
WIP plugin should reapply status when new commits are pushed to a PR
Closed
6 years ago
Commit message check does not enforce "fixes"/"refs" in parentheses
Closed
6 years ago
Comments count
4
Travis failures due to issue-archiver unit test failures
Closed
6 years ago
Proposal: Count 👍 of the team
Updated
6 years ago
Comments count
6
Bot is not adding triage label to issues
Closed
6 years ago
Comments count
3
proposal: disallow merge pr labelled `evaluating`
Updated
6 years ago
Comments count
1
Augment release-monitor for breaking changes
Updated
6 years ago
Comments count
1
release-monitor only updates a maximum of 30 pull requests
Closed
6 years ago
Plugin/Status check for "do not merge" label?
Closed
6 years ago
Comments count
14
Proposal: Repo specific settings for eslint-bot
Updated
6 years ago
Comments count
9
Add "triage" label to new pull requests
Closed
6 years ago
Commit message check false positive
Closed
6 years ago
Comments count
1
release-monitor behavior is slightly inconsistent
Closed
6 years ago
Introducing `triage-new-issues` app
Closed
7 years ago
Comments count
6
Bot sometimes adds `triage` label to its own issues
Closed
7 years ago
Comments count
5
Previous
Next