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

Extend GitHub VSCode Extension to integrate Pull Request Review Flows #10282

Closed
slemeur opened this issue Jul 5, 2018 · 2 comments
Closed

Extend GitHub VSCode Extension to integrate Pull Request Review Flows #10282

slemeur opened this issue Jul 5, 2018 · 2 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@slemeur
Copy link
Contributor

slemeur commented Jul 5, 2018

Description

With the version Che 6 (and prior), we had introduce a pull request panel which automated the creation of a pull request from the IDE.

The goal of this epic is to extend the GitHub VSCode extension (#11867) in order to integrate the different flows we were previously handling.

User Stories:

  • When a user is creating a pull request from Che, it will provide in the comment of the pull request a reviewer link (factory based on the dedicated devfile).
  • When the reviewer link is opened, it will directly checkout the proper PR branch and show the list of comments in the source code (using the capabilities on the GitHub VSCode Extension
@slemeur slemeur added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Jul 5, 2018
@ibuziuk
Copy link
Member

ibuziuk commented Jul 31, 2018

Initial implementation of the plugin would be done as part of the - redhat-developer/rh-che#778

@slemeur slemeur changed the title Pull request plugin for Che's Theia Extend GitHub VSCode Extension to integrate Pull Request Review Flows Mar 19, 2019
@l0rd l0rd mentioned this issue Mar 19, 2019
@che-bot
Copy link
Contributor

che-bot commented Dec 30, 2019

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 Dec 30, 2019
@che-bot che-bot closed this as completed Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants