theia
theia copied to clipboard
eclipse-theia
Deprecate @theia/git extension
As discussed in several dev calls, we would like to deprecate the @theia/git extension. It has a functional overlap with the VS Code built-in Git extension and it does not make sense to maintain our own Git extension anymore. This will reduce maintenance efforts. If you are an active user of the Theia Git extension, we recommend you to evaluate switching to the VS Code built-in. If you see any issues with the switch, please raise them here.
- [x] announce on mailing list
- [x] announce in news & noteworthy
- [x] announce in forum
- [x] blocker: unsupported menu paths: https://github.com/eclipse-theia/theia/issues/11730.
- [x] mark npm package as deprectated
- [ ] remove code (packages/git)
- [ ] add to migration guide
I'd suggest that in addition to the issue that @vince-fugnitto has mentioned, any issues related to getting the VSCode builtin Git extensions & Gitlens working should be linked here so that adopters can be confident that the deprecation of @theia/git won't mean a loss of Git-related functionality.
any issues related to getting the VSCode builtin Git extensions & Gitlens working should be linked here
Such as missing menu support for the git builtins: https://github.com/eclipse-theia/theia/issues/11730.
Didn't we have a repo where "community-supported" packages would live after removing them from the main repo?
Didn't we have a repo where "community-supported" packages would live after removing them from the main repo?
I'm not aware of any community-supported repo (although we can certainly create one if needed). I think the idea similarly to theia-cpp-extensions in the past is to move the package to it's own repository where interested parties can contribute and maintain the package.
Hi, is it still worth reporting and fixing issues related to @theia/git ?
I was planning to use the vs code extension but it's not working yet and we're getting too close to our release to perform the switch. We found a few issues in @theia/git but since the package is being deprecated I'm not sure if I should contribute the fix or just implement a workaround in our project until we can use the vs code extension.
@Hanksha I don't really think it's worth it. Instead, it would be more beneficial to report/fix issues with the vscode.git extension.
