Why are experimental commands git restore and git switch suggested in CLI output?

From: Erik Huizinga <hidden>
Date: 2020-05-02 07:18:39

Hello!

Lately I've noticed that when I checkout a branch or show the working
tree status, then the CLI output suggests that I can perform certain
actions with new commands (since v2.23 if I'm not mistaken) restore
and switch. This is very nice, because I like to see these UI
enhancements. However, reading the help pages for these commands shows
'THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.' This is
somewhat discouraging use, because I don't want to learn to use these
commands if their behavior may change. This could mean that what I
learn about these command may not be usable on future git versions.

My questions about this are:

1. What is the git maintainers' policy regarding experimental features
like restore and switch? Apparently, they are there to be discovered
in plain sight, while experimental. Using experimental features may
not be what the user wants.
2. What exactly may change about these commands' behavior? Are the
superficially suggested actions stable? Are they stable within a patch
or minor git version only? Are existing use cases stable, or can they
be removed or incompatibly change under this experimental policy?

In other words: how can I, an individual end user, know what I can
safely learn about these commands, and what can not?

Thank you in advance for your time and answers. :)
Erik Huizinga
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help