riyadhalnur / issuelabeler

A GitHub bot to label issues automatically based on title and body against list of defined labels. System status (https://stats.uptimerobot.com/DkY20U51GX)

issuelabeler's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Where to put the config file in an Organisation?

Where do I have to put the configuration file when selecting "All Repositories of Organisation" when installing the app?

Limiting the number of labels to consider is the wrong default

Describe the bug
The default setting for the robot should be to get all of the labels to compare with the issue title, not just 20.
This creates a dangerous solution where you get very strange results when you are using the robot successfully with 1 labels and then you add 4 labels and suddenly, the robot will not consider labels 21 and 22.

Instead the robot should default to downloading "all" labels and only worry about limiting the number of labels if that is configured.

I cannot think of a use case where you might have 45 labels but you would only want this functionality for 20 of them... especially if you cannot choose which 20 you want to use in this manner.

To Reproduce
n/a

Expected behavior
I would expect that the robot would always get all of the labels, rather than just twenty, and then IF there is a limit set in the yaml file... then and only then would the robot limit itself.

Screenshots
n/a

Desktop (please complete the following information):
n/a

Smartphone (please complete the following information):
n/a

Additional context
n/a

Possibility to specify keyword and label explicitly

Hi, thank you for your bot! It looks very handy but unfortunately I can't start using it as it lacks one feature that I need:

As a user I would like to be able to specify keywords and appropriate labels in the configuration file. In other words, I don't need the magick of recognition but I'd like to use my own static rules.

For example:

• "unit tests" in the title of the issue should be mapped into "area/unit tests" label
• "rename" or "extract" words in the issue title should be mapped to "refactoring" label

Also I'd like to specify where to look for these keywords because mentioning "rename" or "extract" in the issue's body doesn't mean that it's about refactoring. But if these keywords are in the title, then it's definitely an issue about refectoring.

Thanks!

Could do with a more detailed usage guide

This looks good an app, but I wouldn't want to install it unless there's a bit more detail on how it's typically used

unable to add a tag with spaces

Describe the bug
Unable to get a label to work when it has spaces and a - in it.

To Reproduce
Steps to reproduce the behavior:

  - location: body
    keywords:
      - 'Critcal'
    labels:
      - 'P1 - critical'

Expected behavior
a rule with a tag with spaces does not seem to work at all

Screenshots
bot does not do anything

Desktop (please complete the following information):
chrome

AWS Lambda support

Update bot to run on Lambda rather than standalone instances. Cheaper to deploy and maintain.

Some labels not applying when submitting an issue

Describe the bug
The custom labels that I've created in my repository are not getting applied when an issue is submitted. I would expect that if the text matches my labels exactly, the label would be referenced and applied.

Screenshots
Here are some screenshots to provide some additional context:

I copied the text the labels page and pasted into a new issue.

Desktop (please complete the following information):

• OS: Windows 10 Version 1803
• Browser: Microsoft Edge Version 79.0.309.51 (Official build) beta (64-bit)

Use NLP for better tagging

Looking to introduce NLP to tag issues better. IRL, not all issues will have text that will match labels present for a repo. With NLP hopefully, the bot can tag issues depending on sentiment and intent.

Allow more than one keywords as the yaml is pretending with keyword"s"

Is your feature request related to a problem? Please describe.
I would like to summarize many keywords to label them with the same label(s).
Without this feature I have to make many entries with location+keyword+labels 😞

Describe the solution you'd like
For example it should be possible to define something like that:

   - location: title
     keywords:
       - 'pi-hole'
       - 'pihole'
     labels:
      - pi-hole
      - adblocking

You can imagine that this description will got very long for many keywords and hard to maintain… 🤷🏻‍♂️

Describe alternatives you've considered
Alternatives right now are:

   - location: title
     keywords:
       - 'pi-hole'
     labels:
      - pi-hole
      - adblocking
   - location: title
     keywords:
       - 'pihole'
     labels:
      - pi-hole
      - adblocking

Additional context
There's no any other context or screenshots about the feature request here.

Allow regular expressions as keywords

Is your feature request related to a problem? Please describe.
This is related to #38
I'm always frustrated when I have to define many keywords that I could also define with a regex.

Describe the solution you'd like
For example it should be possible to define something like that:

   - location: title
     keywords:
       - 'pi?hole.*adblock*'
     labels:
      - pi-hole
      - adblocking

Describe alternatives you've considered
Alternatives right now are defining many keywords:

   - location: title
     keywords:
       - 'pi-hole'
     labels:
      - pi-hole
      - adblocking
   - location: title
     keywords:
       - 'pihole'
     labels:
      - pi-hole
      - adblocking

Additional context
There's no any other context or screenshots about the feature request here.

More explicit labeling

Just because someone mentioned the word "bug" in the description, it doesn't mean the issue should be labeled bug. Maybe it's a suggestion or question and the person writes "I don't think it's a bug, but...".
And if someone mentions an "invalid state", the issue should not be labeled invalid.

However, using GitHub's new multiple issue templates system, I can make sure that the template for bug reports contains the string label:bug in the front matter.

The behavior should be configurable in the yml file. excludeLabels still applies, because some labels should only be added manually by team members.

Match on empty body

Is your feature request related to a problem? Please describe.
When trying to control spam or poor quality issues. Large repos get a lot of just completely empty issues.

Describe the solution you'd like
Some way to match empty issues or do negative matching

Describe alternatives you've considered
None that I can think of

Additional context

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

• engines was only updated if it defined a single version, not a range.
• .nvmrc was updated to Node.js 10
• .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Upgrade to Probot v7

Contains support for TS

The bot not working when creating an issue

Describe the bug
Please check my project: Alanwang2015/Issue-Labeler-Bot#8 (comment)
I have installed the bot for my repo, but it didn't work.

Does not work in private repo with access to pull request

I think it makes sense to add pull request access since it needs its title to be able to label the pull request.

Sorry, I thought this bot works with PRs as well. :(