Summary

(Summarize the bug encountered concisely)

Steps to reproduce

(How one can reproduce the issue - this is very important)

Pull Request URL

(If possible, please paste pull request URLs which have errors.)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

Possible fixes

(If you have any idea to solve the problem, please help us.)

"PR: unreviewd" should be "PR: unreview_e_d".
image is also used on https://probot.github.io/apps/pr-triage/

🚨 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.

Summary

About a week ago, the app stopped working for all repos within our yreceipts organisation. It no longer adds or changes any labels of any pull requests. I can confirm the app is still enabled and authorised.

Steps to reproduce

For example, request changes on a PR where the app is installed.

Pull Request URL

For example: https://github.com/yreceipts/yreceipts.com/pull/1809

What is the current bug behavior?

Nothing happens.

What is the expected correct behavior?

A label reflecting the current status of the PR should be added and the previous such label removed when said status changes.

Relevant logs and/or screenshots

No logs are available, as the app no longer leaves any noticeable traces.

Possible fixes

N/A

Additional context

• wip/app@d6603bb

Summary

A label is changed by editing PR.

Steps to reproduce

1. Create a PR (should have a PR: unreviewed label)
2. Change the PR's title
3. Oops, label is gone 👎

Pull Request URL

(If possible, please paste pull request URLs which have errors.)

What is the current bug behavior?

1. Create a PR (should have a PR: unreviewed label)
2. Change the PR's title
3. Oops, The label is gone 👎

What is the expected correct behavior?

1. Create a PR (should have a PR: unreviewed label)
2. Change the PR's title
3. Nothing happens 💯

Relevant logs and/or screenshots

N/A

Possible fixes

N/A

https://probot.github.io/docs/deployment/#error-tracking

pull request のワークフローをサポートするボット

Summary

The bot forgot (a few times) to remove the PR: unreviewed either when it was mistakenly added alongside PR: reviewed-approved (shouldn't that label be PR: review-approved?) like in here or and simply forgot to remove it when a review was approved or changes were requested.

Steps to reproduce

Have someone or a bot open a PR, have a bot (say access-lint) approve the review and watch.

Pull Request URL

What is the current bug's behaviour?

It seems to be activating two events causing a mix of labelling which could persist even after the PR was closed or merged.

What is the expected correct behaviour?

The bot should add and remove the correct label whether a bot or human approved a PR or requested changes to it.

Relevant logs and/or screenshots

There are other repos where that bug occurred but it can be reflected by the example above.

Possible fixes

Possibly adding more checks to ensure that PRs, where multiple reviews are requested that it takes into account when one is an approval and the other one, is either blank (read unreviewed) or requesting changes.

see #45

ref: https://github.com/webpack/webpack/labels

🚨 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.

Summary

Please add the ability to customize the labels that will be used. PR: unreviewed, PR: review-approved and PR: reviewed-changes-requested doesn't match our style. While we can obviously fork the app and make the changes, it would be great to make them configurable.

If this feature is done, I would use probot-config to allow for a .github/pr-triage.yml file.

In order to keep the labels under control, if this is implemented, it would be great if it would automatically migrate the existing label names. Do a check to see if the original name exists, and then replace it with the configured name. This way we don't have a ton of PRs that don't have the correct label.

I cannot notice when new issue is created immediately. I do not want users or contributors to wait 24 hours. I want to replay something immediately If I am up 😄 I do not want to use bot. It is not useful in this situation.

When a bot such as Dependabot opens a PR, it is not being triaged (labeled). These cases are still useful because we still need to review these, and it helps us mark what PRs may or may not be reviewed.

These assets are under MIT License.

Sketch compressed file

sidekick.sketch 2.zip

!!PLEASE READ IT!!

To make it easier for us to treat your feedback,
we have made a template you can fill out.

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label.

• https://github.com/sotayamashita/labeling-droid/labels/bug

and verify the issue you're about to submit isn't a duplicate.
Please make separate posts for each feature request or bug report.
Please remove this notice if you're confident your issue isn't a duplicate.

Summary

Add PR: reviews-approved label even though nobody approve PR.

Steps to reproduce

1. Create a PR
2. Leave a single comment

Pull Request URL

skip because of permission 😢

What is the current bug behavior?

Add PR: reviewed-approved

What is the expected correct behavior?

Do nothing

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

Possible fixes

(If you have any idea to solve the problem, please help us.)

🚨 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.

idea

• PullRequestGuard = pull request + lifeguard
• kuroko

Hi @sotayamashita! This bot looks really useful. Should we give it a try on some electron repos? You think it's stable enough?

Add draft status label.

package.json should be :

"coverageThreshold": {
      "global": {
          "functions": 100,
          "lines": 100
      }
},

Summary
Add status for merged pull requests without approval.

Issue type: Suggestion

Current Behavior:

Expected behavior (Suggestion)

Current CONTRIBUTION is not great for beginner for Probot.

Summary

Steps to reproduce

1. Merge PR
2. Comment

Pull Request URL

N/A

What is the current bug behavior?

PRTriage remove PR: Merged if user comment.

What is the expected correct behavior?

PRTriage should only check commit

Relevant logs and/or screenshots

Possible fixes

(If you have any idea to solve the problem, please help us.)

Summary

The bot does not seem to be doing anything. I have it installed on a test repo, and no matter what, it does not label anything. Neither a needs-review, or reviewed and needs to be fixed, nothing.

I also looked at the one PR opened on this project, and it doesn't look like the bot is being used here, or it isn't working.

I have not changed the code but it seems it does not work.
I apologize for the inconvenience. 🙇 🙇

--- Update ---
Problem

• Glitch cannot handle engine field
• Glitch cannot find library.

Solution
I use NOW instead of Glitch. It works well so far.

Reference
Error log on Glitch

• https://gist.github.com/sotayamashita/fba096a660cac3ac8fd2d77fb5365253

Summary

When a review is dismissed, the status should update based on other reviews. If there are no other reviews, it should go back to unreviewed. If there are other reviews, the status should depend on them.

Steps to reproduce

Review a PR and approve it. Then dismiss the review.

What is the current bug behavior?

The label stays the same.

What is the expected correct behavior?

The label is removed and goes back to unreviewed.

🚨 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.

ref #22

I have created my stand alone deployment for Github Enterprise and I got the following error

08:55:33.581Z ERROR event: {"message":"A JSON web token could not be decoded","documentation_url":"https://developer.github.com/enterprise/2.13/v3"} (id=220e4f40-a132-11e8-9db5-d4be22122988)
  HttpError: {"message":"A JSON web token could not be decoded","documentation_url":"https://developer.github.com/enterprise/2.13/v3"}
      at response.text.then.message (/pr-triage/node_modules/@octokit/rest/lib/request/request.js:72:19)
      at <anonymous>
      at process._tickDomainCallback (internal/process/next_tick.js:228:7)
  --
  event: {
    "event": "pull_request_review.submitted",
    "id": "220e4f40-a132-11e8-9db5-d4be22122988",
    "installation": 21,
    "repository": "xxxxxxxxx/yyyyyyyy"
  }
08:55:33.581Z  INFO http: POST / 200 - 141.73 ms (id=220e4f40-a132-11e8-9db5-d4be22122988)
09:01:21.185Z DEBUG github: GitHub request: GET /app/installations - 401 undefined (installation=undefined)
  params: {
    "per_page": 100,
    "baseUrl": "https://github.xxxxx.com/api/v3",
    "request": {
      "timeout": 0
    }
  }

• Use built in logger instead of debug

🚨 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.

🚨 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.

In the current implementation, PRTriage prioritize WIP over draft. I think It just doesn't feel right to me. What do you think?

*** Update ***
I am leaving it open for at least 14 7 days to give time for you to raise any concerns.
(14 days is too long)

https://github.com/apps/pr-triage