erichbehrens / pull-request-monitor

VS Code extension to monitor the state of your GitHub pull requests

Erich Behrens GitHub page

pull-request-monitor's Issues

An in-range update of vscode is breaking the build 🚨

The dependency vscode was updated from 1.1.30 to 1.1.31.

🚨 View failing branch.

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

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

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

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 🌴

Feature Suggestion: Add support for reading http.proxy setting

I found this plugin not reading the global configuration http.proxy, so I was unable to use this plugin when I'm inside the company, cuz the network in the company does not allow direct connection to the external network, it requires a proxy, so I suggest reading the global setting: http.proxy

Feature Suggestion: handle github enterprise

Hello,
thanks for this extension :)

It will be nice to allow enterprise users with a dedicated instance of github enterprise to use it too, I don't see any setting to declare the url of a specific github server.

[Question] Support for multiple github installations

My team currently has repos in github.com as well as github enterprise. Is there a way to monitor both? The instructions were not clear on this scenario.

Monitor should ignore archived projects

The Pull Request tfmt/googler#1 is showing up on my monitor list, despite the fact that the project has been archived, and I am physically incapable of closing said pull-request anymore.

This PR should be ignored, and not listed by Pull Request Monitor

Color coding stopped working

Starting sometime last week (or it could have been the previous one) the color coding is not working. All PRs stay green regardless of their status. Currently running on 1.7.1.

An in-range update of eslint-plugin-import is breaking the build 🚨

The devDependency eslint-plugin-import was updated from 2.17.1 to 2.17.2.

🚨 View failing branch.

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

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Commits

The new version differs by 5 commits.

• eddcfa9 Bump to v2.17.2
• b151d04 [fix] no-unused-modules: avoid crash when using ignoreExports-option
• 3512563 [fix] no-unused-modules: make sure that rule with no options will not fail
• 8e0c021 [Test] no-unused-modules add failing test case
• 9b7a970 [meta] add npm run mocha for easier unit testing

See the full diff

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 🌴

Feature Request: Different Color Ignore Drafts

It would be nice to be able to color draft pr's differently

Feature Suggestion: Allow to monitor when you are added as a reviewer of a pull request

Hey,
Nice tool.

I have a feature suggestion: Would it be possible to add the possibility to monitor also the PRs you are asked for reviewing?

i.e: Someone creates a new PR, add you as a reviewer, then you get a notification informing about this PR. #

feature suggest: add live virtual comments to lines of code changed in opened PRs

use case: "hm, I'm gonna fix indentation... oops, someone's pull request change that line too... let's look"

Feature Request: Set the monitored repository to the currently open project

I downloaded and found it useful, but my use case didn't seem to fit. Basically, I wanted to open my current project and see the pull request monitor set to the repository that is open, so I can easily monitor any active pull requests or issues on the project I'm actively in. I can't find any option to do this, as the directions seem to point towards me having to switch the monitored repository manually, but nothing about setting to the current repository that is open.

I'd like to put this in as a feature request.

New Option: Set Repository to Current Project Repository.

Cheers

Instructions a bit opaque

The instructions to install the extension include this line

Open the command palette and execute PullRequestMonitor.setToken

Seemed unclear to me how to execute that command. I tried typing Pull... but nothing appeared. Only found after a few min of trial and error.

Maybe simply write execute PR Monitor: Set Github Token?

Feature Request: Change colors in settings

It would be nice to be able to change the colors in settings, even if I had to do it in json.