You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scm-history view does not work when using the vscode builtin extensions, there is a message stating that history does not work for git source control (the same is true when an individual file is selected to display it's history):
It looks like it was never actually supported #6381, the vscode api for extensions does not provide history, but it does provide timeline information. I believe it was the reason to have some @theia/scm-extra (which I had forgotten about).
@msujew I believe there is no issue, if we use the builtin we should not use @theia/git or @theia/scm-extra.
if we use the builtin we should not use @theia/git or @theia/scm-extra
Since the Theia Blueprint uses the builtin Git extension instead of @theia/git, does that mean it should remove @theia/scm and @theia/scm-extra? I'm happy to open a PR if so.
Since the Theia Blueprint uses the builtin Git extension instead of @theia/git, does that mean it should remove @theia/scm and @theia/scm-extra? I'm happy to open a PR if so.
@danepowell@theia/scm is necessary is necessary for source-control support in which vscode.git is a contribution. The @theia/scm-extra can be safely removed I believe as it only contributes the history-view at this time.
Bug Description:
The
scm-history
view does not work when using the vscode builtin extensions, there is a message stating that history does not work for git source control (the same is true when an individual file is selected to display it's history):Steps to Reproduce:
remove
@theia/git
from the example application(s)use the git builtins (tested with
1.53.2
):start the application with a folder that is under version control
confirm that version control works (scm-view), but not the history view
The text was updated successfully, but these errors were encountered: