mithro / autolabeler Goto Github PK

cc @mithro

The dependency js-yaml was updated from 3.12.0 to 3.12.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

js-yaml is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

EDIT: solved in comment below

Is it possible to publish this probot to npm?

background

I'm trying to get this probot onto our corporate github enterprise. It would be much easier if this were published on npm so that I could bundle this entire app as a dependency within a single package.json and simply make that available as a probot. E.g., instead of having multiple individual probots, I can combine them into one like so:

{
  "name": "probot-combo-value-pack",
  "private": true,
  "dependencies": {
    "probot-stale": "probot/stale",
    "probot-settings": "probot/settings",
    "probot-autoresponder": "probot/autoresponder",
    "probot-autolabeler": "probot/autolabeler"
  },
  "scripts": {
    "start": "probot run"
  },
  "engines": {
    "node": "10.x"
  },
  "probot": {
    "apps": [
      "probot-stale",
      "probot-settings",
      "probot-autoresponder",
      "probot-autolabeler"
    ]
  }
}

Thanks a ton for your time. I appreciate it

I'd love to use it even with just the basic simple functionality.

See https://github.com/mithro/HDMI2USB-litex-firmware/blob/probot-autolabeler/.github/autolabeler.yml for example :-)

It would be great if this worked with probot-config so I don't have to add a configuration file to each repo.

How come this bot is not the apps gallery section of the website? 🙂

Now that #17 is fixed. It would be good if the autolabeler repo was also using autolabeler bot!

/Got it deployed with Now, but not sure I have the app configuration or permissions right? Does the yaml need to be on the master branch?

My current workflow uses several branches for dev, stage and prod builds. It would be nice to be able to set labels based on target branch.

Would the project be open to changes that reduced the redundant labeling and / or removed labels that no longer match the paths in the changeset?

In the screenshot here, many of the label events in the conversation view are already applied to the PR. Would be nice to only add a label if the PR does not already include it.

Also, if one of the files that matched in an earlier commit is removed and no longer in HEAD, would be nice to remove that label. In other words, given all existing labels on PR, check if they still apply, removing any that don't.

Please add functionality to extend target repo config with config in central repository as described in probot docs

Hi,

I'm looking for something like autolabeler to automate tagging for me, the tagging based on file can allow me to distinguish between say documentation changes and source changes, but I can't distinguish between a new feature and a bugfix.

I was wondering how useful or easy it would be to enable autolabeler to check the first comment in a PR, like this one: BioJulia/BioGenerics.jl#2, and then based in some of the tick boxes in there, update the tags.

I took the code to my local machine and tried compiling it by running "npm install" followed by "npm start" but it throws an error.
I am not a react/node.js developer.
As per the documentation running, "npm install" followed by "npm start" should work an instance should be deployed on localhost but it doesn't. Can you please share some input here? Look at the log shared below.

Pushing a package.json that looks like this:

{
  "name": "probot-combo-value-pack",
  "private": true,
  "dependencies": {
    "probot-labeler": "probot/autolabeler"
  },
  "scripts": {
    "start": "probot run"
  },
  "engines": {
    "node": "10.x"
  },
  "probot": {
    "apps": [
      "probot-labeler"
    ]
  }
}

and getting an error within probot-config, which says context.github.repos.getContents is not a function:

2019-05-31T09:17:27.970-05:00 [APP/PROC/WEB/1] [OUT] at EventEmitter.events.on (/home/vcap/deps/0/node_modules/probot/lib/robot.js:102:17)
2019-05-31T09:17:27.970-05:00 [APP/PROC/WEB/1] [OUT] at robot.on (/home/vcap/deps/0/node_modules/probot-settings/index.js:9:26)
2019-05-31T09:17:27.970-05:00 [APP/PROC/WEB/1] [OUT] at getConfig (/home/vcap/deps/0/node_modules/probot-config/lib/index.js:114:24)
2019-05-31T09:17:27.970-05:00 [APP/PROC/WEB/1] [OUT] at loadYaml (/home/vcap/deps/0/node_modules/probot-config/lib/index.js:48:49)
2019-05-31T09:17:27.970-05:00 [APP/PROC/WEB/1] [OUT] �[90m TypeError: context.github.repos.getContents is not a function

Using GitHub Enterprise Server 2.16.2

Guessing this is related to a change in an upstream dependency (probot-config, probot itself, etc.) that has deprecated one of the modules used for retrieving content within GHE.

[issue moved from repository-settings/app#123]

Hi!

I have been using Autolabeler for a few weeks now, however, I am noticing that sometimes it adds the labels and sometimes it does not. Kind of seems like it only works when it wants to ;)

Here is a link to a PR that clearly has files in the autolabeler.yml config. But you can see, it never added any tags to that PR. doc-kits/react#89

Here is my config:

components: ['/src']
documentation: ['*.md']
example: ['/examples']
tooling:
  [
    '.babelrc',
    'jest.config.js'
    '*.json',
    '*.yml',
    '.github',
    '.ci',
    '.storybook',
  ]

Any ideas?

Thanks!

🚨 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, 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 integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Is it (or would it be) possible to use this on GitHub issues instead of or in addition to PRs?

No particular reason other than I'm feeling it's a lot more better and more comfortable for the (most?) users, and for me. There are some differences between the git ignore standard and the other available globbing.

The current app deployment is getting the following error;

ERROR	 (HttpError): Not Found
    HttpError: Not Found
        at /rbd/pnpm-volume/8f9a4cf4-b57a-45cf-93f2-37bc9eadfd05/node_modules/.registry.npmjs.org/@octokit/request/5.4.10/node_modules/@octokit/request/dist-node/index.js:66:23
        at processTicksAndRejections (internal/process/task_queues.js:88:5)
        at async sendRequestWithRetries (/rbd/pnpm-volume/8f9a4cf4-b57a-45cf-93f2-37bc9eadfd05/node_modules/.registry.npmjs.org/@octokit/auth-app/2.10.2/node_modules/@octokit/auth-app/dist-node/index.js:440:12)
        at async Job.doExecute (/rbd/pnpm-volume/8f9a4cf4-b57a-45cf-93f2-37bc9eadfd05/node_modules/.registry.npmjs.org/bottleneck/2.19.5/node_modules/bottleneck/light.js:405:18)

🚨 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

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

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, 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 integration’s white list on Github. You'll find this list on your repo or organiszation’s settings page, under Installed GitHub Apps.

Hi,

In repos with both the behaviorbot and the autolabeler bot, the autolabeler bots conflicts with the behaviorbot and the behaviorbot doesn't execute its workflow. Is this a known issue?

It looks like autolabeler is only ever adding a single label?

What is the format used for the autolabeler.yml file?
What are the rules it could follow? (i'm not sure if this is implemented yet)

Edit:
So the rules for labels seem to be defined as patterns to be matched using ignore.
if a pattern matches a label is added to the issue.
@bkeepers

Hey, default tests are failling

Looking at Github API 👉 https://docs.github.com/en/rest/issues/labels?apiVersion=2022-11-28#add-labels-to-an-issue

Body have to be:

{"labels": ["test", "config"]}

Noticing there are PRs from greenkeeper that haven't been touched in quite some time, and the last commit to master was April 4th, 2018.

Don't mean to sound entitled to OSS, just trying to be pragmatic:

Is probot/autolabeler all but deprecated?

Hi @mithro! Thank you so much for the wonderful PR autolabeler. 🙂

I work over on the Apache Iceberg project, and it appears that our autolabeler stopped working around 11 days ago. I checked the Apache Spark repo, which also uses this same autolabeler, and it looks as though the last time their autolabeler ran was about 10 days ago.

I admittedly don't have full access rights over there (the ASF infra team enabled it for us after we put in the config), so I tried opening a PR against my local fork where I do have full control and it also did not seem to run or generate any labels.

Here's the issue related to this in the Iceberg project.

Additionally, here's our config file in the official Apache Iceberg repo.

Finally, here's a link to the PR I opened in my own fork where I verified that the autolabeler did not run. The PR in question should have been labeled FLINK.

I will attach a screenshot of my forked repos configuration for this app to help debug.

We love having out PRs labeled, so any assistance or tips you could provide would be of great help. I'd be happy to also follow any troubleshooting steps in my local fork, where I have full permissions to adjust whatever I want, if you think that would help.

Thank you for the work you do on this project!