This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the past we had a single context menu, that got applied to every RefItem - independent of it's type. At that time we only differed between a "Reference" and "Pseudo-Item" (aka header/folder).
Nowadays, we have more types available, (e.g. a Remote item). This requires us to split the menu according to the item type. Finally, this allows us to show the "right action at the right place".
Branch
,Remote
andTag
.RemoteBranch
.Branch
. Didn't check yet, but a "sub-type" should be available.Git::CheckoutOperation
with anRM::CheckoutService
. If done right, we should be able to simply provide theitem->object()
to RepoMan.