Jacob Keller fab466f91d completion: add test showing subpar git switch completion
When provided with no options, git switch only allows switching between
branches. The one exception to this is the "Do What I Mean" logic that
allows a unique remote branch name to be interpreted as a request to
create a branch of the same name that is tracking that remote branch.

Unfortunately, the logic for the completion of git switch results in
completing not just branch names, but also pseudorefs like HEAD, tags,
and fully specified <remote>/<branch> references.

For example, we currently complete the following:

 $git switch <TAB>
 HEAD
 branch-in-other
 master
 master-in-other
 matching-branch
 matching-tag
 other/branch-in-other
 other/master-in-other

Indeed, if one were to attempt to use git switch with some of these
provided options, git will reject the request:

 $git switch HEAD
 fatal: a branch is expected, got 'HEAD

 $git switch matching-tag
 fatal: a branch is expected, got tag 'matching-tag'

 $git switch other/branch-in-other
 fatal: a branch is expected, got remote branch 'other/branch-in-other'

Ideally, git switch without options ought to complete only words which
will be accepted. Without options, this means to list local branch names
and the unique remote branch names without their remote name pre-pended.

 $git switch <TAB>
 branch-in-other
 master
 master-in-other
 matching-branch

Add a test case that highlights this subpar completion. Also add
a similar test for git checkout completion that shows that due to the
complex nature of git checkout, it must complete all references.

Signed-off-by: Jacob Keller <jacob.keller@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-05-28 12:53:24 -07:00
2020-03-25 13:57:43 -07:00
2020-04-22 13:42:58 -07:00
2020-04-22 13:43:01 -07:00
2020-03-21 18:26:56 +08:00
2020-03-05 10:43:02 -08:00
2020-03-25 13:57:41 -07:00
2020-03-25 13:57:41 -07:00
2019-11-20 13:29:02 +09:00
2019-11-18 15:21:28 +09:00
2019-11-18 15:21:28 +09:00
2020-03-30 10:59:08 -07:00
2020-02-19 09:37:15 -08:00
2020-04-22 13:42:49 -07:00
2019-12-25 11:21:58 -08:00
2019-12-06 16:31:39 +01:00
2019-12-01 09:04:36 -08:00
2020-03-25 13:07:47 -07:00
2019-11-10 16:00:54 +09:00
2019-12-16 13:08:39 -08:00
2020-03-05 10:43:02 -08:00
2019-12-25 11:21:58 -08:00
2020-03-10 11:41:40 -07:00
2020-03-10 11:41:40 -07:00
2020-04-19 16:31:07 -07:00
2020-04-19 16:32:24 -07:00
2020-04-22 13:42:44 -07:00
2020-01-15 12:14:51 -08:00
2019-11-18 15:21:28 +09:00
2019-11-10 16:00:54 +09:00
2019-12-01 09:04:35 -08:00
2020-04-19 22:05:56 -07:00
2019-11-18 15:21:28 +09:00
2020-03-02 15:07:20 -08:00
2020-04-22 13:42:49 -07:00
2020-03-28 16:50:40 -07:00
2019-12-01 09:04:35 -08:00
2020-04-22 13:42:49 -07:00
2020-03-26 17:11:20 -07:00
2019-12-16 13:08:39 -08:00
2019-12-02 08:48:56 -08:00
2019-11-27 10:57:10 +09:00
2020-04-22 13:42:55 -07:00
2019-11-18 15:21:28 +09:00
2020-04-19 16:32:24 -07:00
2019-11-10 16:00:54 +09:00
2020-03-26 17:11:20 -07:00
2019-11-13 10:09:10 +09:00
2019-11-18 15:21:29 +09:00
2020-03-05 10:43:02 -08:00
2019-11-18 15:21:29 +09:00
2019-11-10 16:00:54 +09:00
2019-12-25 11:21:59 -08:00

Build Status

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-<commandname>.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://lore.kernel.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 663 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%