Open RomanNikitenko opened 12 months ago
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.
We could add a simple command to the che-code devfile that will install git-subtree from sources.
We could add a simple command to the che-code devfile that will install git-subtree from sources.
Instead of adding a devfile command, could you add a single file like install-git-subtree.sh
into .rebase
directory?
Describe the bug
It's impossible to work on issues like this: https://github.com/eclipse/che/issues/22577 using che-in-che development because of
git: 'subtree' is not a git command
error.Che version
7.75@latest
Steps to reproduce
Follow these steps: https://github.com/che-incubator/che-code#fixing-the-rebase-insiders-workflow After execution of
rebase.sh
script you can see the error.Expected behavior
git subtree
command should be available for running within che-in-che development. I think theDev
container should contains the corresponding package to fix the current issue.Screenshots
Additional context
I've faced the problem on the Dogfooding instance.