Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update the vscode GitHub Pull-Requests plugin to latest. #18661

Closed
1 of 3 tasks
vinokurig opened this issue Dec 18, 2020 · 3 comments
Closed
1 of 3 tasks

Update the vscode GitHub Pull-Requests plugin to latest. #18661

vinokurig opened this issue Dec 18, 2020 · 3 comments
Assignees
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system. status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage.

Comments

@vinokurig
Copy link
Contributor

vinokurig commented Dec 18, 2020

Is your enhancement related to a problem? Please describe.

To be able to build the plugin's binary ourselves we need to use at least 0.21.4 version, otherwise the build fails.

Describe the solution you'd like

  • Update the built-in vscode git plugin to latest (1.52.1)
  • Update the plugin version to latest (or 0.21.4 if the latest version requires any additional actions) in the plugin registry.
  • Update the FileDecoration vscode Plugin API, because it is used in the latest version of the git and GitHub plugins.

Describe alternatives you've considered

Additional context

@vinokurig vinokurig added the kind/enhancement A feature request - must adhere to the feature request template. label Dec 18, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 18, 2020
@yhontyk yhontyk added area/plugins severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Dec 18, 2020
@vinokurig vinokurig self-assigned this Dec 22, 2020
@ericwill ericwill mentioned this issue Mar 1, 2021
46 tasks
@ericwill ericwill added this to the 7.28 milestone Mar 2, 2021
@ericwill ericwill mentioned this issue Mar 18, 2021
46 tasks
@ericwill ericwill removed this from the 7.28 milestone Mar 24, 2021
@vinokurig
Copy link
Contributor Author

depends on #19804

@vinokurig vinokurig added the status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage. label Jun 1, 2021
@svor svor mentioned this issue Aug 12, 2021
30 tasks
@vinokurig
Copy link
Contributor Author

vinokurig commented Aug 30, 2021

depends on #20366, #20316

@svor svor mentioned this issue Sep 7, 2021
26 tasks
@che-bot
Copy link
Contributor

che-bot commented Mar 7, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 7, 2022
@che-bot che-bot closed this as completed Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P2 Has a minor but important impact to the usage or development of the system. status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage.
Projects
None yet
Development

No branches or pull requests

5 participants