Skip to content
This repository was archived by the owner on Oct 1, 2024. It is now read-only.

PR should either be accepted or rejected, not left in limbo #1059

Closed
PeterWone opened this issue Jun 22, 2020 · 4 comments
Closed

PR should either be accepted or rejected, not left in limbo #1059

PeterWone opened this issue Jun 22, 2020 · 4 comments
Assignees

Comments

@PeterWone
Copy link
Contributor

You processed mine quite quickly, but for some reason some PRs have languished for literally years. In particular I can tell you the author of #767 is running out of patience with bringing his fork up to date for your merging convenience only to be ignored for two years.

If you don't want the PR then reject it. Don't leave him in limbo.

I know you do your best. You were actually pretty quick when I submitted a fix.

@hairlesshobo
Copy link

Hey, thanks! I appreciate you helping bring attention to this!

@PeterWone
Copy link
Contributor Author

No worries. As a matter of interest, I have made a feature request for vscode itself. Do me a favour and take a look microsoft/vscode#100534 see whether you think it's a good idea.

@phord
Copy link

phord commented Jun 24, 2020

Curiously, #676 was also abandoned for neglect. Coincidence?

@benmcmorran
Copy link
Member

We have more resources dedicated to this project now, and #1406 outlines our plan going forward. We'll be reviewing new issues and PRs at least weekly. Please feel free to comment on #1406 if you have any other questions or suggestions for how we can improve the governance of this project.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants