;ELC
|
;;; Compiled
|
;;; in Emacs version 26.1
|
;;; with all optimizations.
|
|
;;; This file uses dynamic docstrings, first added in Emacs 19.29.
|
|
;;; This file does not contain utf-8 non-ASCII characters,
|
;;; and so can be loaded in Emacs versions earlier than 23.
|
|
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
|
|
|
(byte-code "\300\301!\210\300\302!\210\300\303!\210\304\305\306\307\310DD\311\312\313\314\315\316\317& \210\304\320\306\307\321DD\322\312\323\314\315\316\324& \210\304\325\306\307\326DD\327\312\330\314\315\316\331& \210\304\332\306\307\333DD\334\312\335\314\315\316\336& \210\304\337\306\307\340DD\341\312\342\314\315\316\343& \210\304\344\306\307\345DD\346\312\347\314\315\316\350& \207" [require magit magit-collab magit-reset custom-declare-variable magit-branch-read-upstream-first funcall function #[0 "\300\207" [t] 1] "Whether to read upstream before name of new branch when creating a branch.\n\n`nil' Read the branch name first.\n`t' Read the upstream first.\n`fallback' Read the upstream first, but if it turns out that the chosen\n value is not a valid upstream (because it cannot be resolved\n as an existing revision), then treat it as the name of the\n new branch and continue by reading the upstream next." :package-version (magit . "2.2.0") :group magit-commands :type (choice (const :tag "read branch name first" nil) (const :tag "read upstream first" t) (const :tag "read upstream first, with fallback" fallback)) magit-branch-prefer-remote-upstream #[0 "\300\207" [nil] 1] "Whether to favor remote upstreams when creating new branches.\n\nWhen a new branch is created, then the branch, commit, or stash\nat point is suggested as the default starting point of the new\nbranch, or if there is no such revision at point the current\nbranch. In either case the user may choose another starting\npoint.\n\nIf the chosen starting point is a branch, then it may also be set\nas the upstream of the new branch, depending on the value of the\nGit variable `branch.autoSetupMerge'. By default this is done\nfor remote branches, but not for local branches.\n\nYou might prefer to always use some remote branch as upstream.\nIf the chosen starting point is (1) a local branch, (2) whose\nname matches a member of the value of this option, (3) the\nupstream of that local branch is a remote branch with the same\nname, and (4) that remote branch can be fast-forwarded to the\nlocal branch, then the chosen branch is used as starting point,\nbut its own upstream is used as the upstream of the new branch.\n\nMembers of this option's value are treated as branch names that\nhave to match exactly unless they contain a character that makes\nthem invalid as a branch name. Recommended characters to use\nto trigger interpretation as a regexp are \"*\" and \"^\". Some\nother characters which you might expect to be invalid, actually\nare not, e.g. \".+$\" are all perfectly valid. More precisely,\nif `git check-ref-format --branch STRING' exits with a non-zero\nstatus, then treat STRING as a regexp.\n\nAssuming the chosen branch matches these conditions you would end\nup with with e.g.:\n\n feature --upstream--> origin/master\n\ninstead of\n\n feature --upstream--> master --upstream--> origin/master\n\nWhich you prefer is a matter of personal preference. If you do\nprefer the former, then you should add branches such as \"master\",\n\"next\", and \"maint\" to the value of this options." (magit . "2.4.0") (repeat string) magit-branch-adjust-remote-upstream-alist #[0 "\300\207" [nil] 1] "Alist of upstreams to be used when branching from remote branches.\n\nWhen creating a local branch from an ephemeral branch located\non a remote, e.g. a feature or hotfix branch, then that remote\nbranch should usually not be used as the upstream branch, since\nthe push-remote already allows accessing it and having both the\nupstream and the push-remote reference the same related branch\nwould be wasteful. Instead a branch like \"maint\" or \"master\"\nshould be used as the upstream.\n\nThis option allows specifing the branch that should be used as\nthe upstream when branching certain remote branches. The value\nis an alist of the form ((UPSTREAM . RULE)...). The first\nmatching element is used, the following elements are ignored.\n\nUPSTREAM is the branch to be used as the upstream for branches\nspecified by RULE. It can be a local or a remote branch.\n\nRULE can either be a regular expression, matching branches whose\nupstream should be the one specified by UPSTREAM. Or it can be\na list of the only branches that should *not* use UPSTREAM; all\nother branches will. Matching is done after stripping the remote\npart of the name of the branch that is being branched from.\n\nIf you use a finite set of non-ephemeral branches across all your\nrepositories, then you might use something like:\n\n ((\"origin/master\" \"master\" \"next\" \"maint\"))\n\nOr if the names of all your ephemeral branches contain a slash,\nat least in some repositories, then a good value could be:\n\n ((\"origin/master\" . \"/\"))\n\nOf course you can also fine-tune:\n\n ((\"origin/maint\" . \"\\\\\\=`hotfix/\")\n (\"origin/master\" . \"\\\\\\=`feature/\"))\n\nIf you use remote branches as UPSTREAM, then you might also want\nto set `magit-branch-prefer-remote-upstream' to a non-nil value.\nHowever, I recommend that you use local branches as UPSTREAM." (magit . "2.9.0") (repeat (cons (string :tag "Use upstream") (choice :tag "for branches" (regexp :tag "matching") (repeat :tag "except" (string :tag "branch"))))) magit-branch-rename-push-target #[0 "\300\207" [t] 1] "Whether the push-remote setup is preserved when renaming a branch.\n\nThe command `magit-branch-rename' renames a branch named OLD to\nNEW. This option controls how much of the push-remote setup is\npreserved when doing so.\n\nWhen nil, then preserve nothing and unset `branch.OLD.pushRemote'.\n\nWhen `local-only', then first set `branch.NEW.pushRemote' to the\n same value as `branch.OLD.pushRemote', provided the latter is\n actually set and unless the former already has another value.\n\nWhen t, then rename the branch named OLD on the remote specified\n by `branch.OLD.pushRemote' to NEW, provided OLD exists on that\n remote and unless NEW already exists on the remote.\n\nWhen `forge-only' and the `forge' package is available, then\n behave like `t' if the remote points to a repository on a forge\n (currently Github or Gitlab), otherwise like `local-only'.\n\nAnother supported but obsolete value is `github-only'. It is a\n misnomer because it now treated as an alias for `forge-only'." (magit . "2.90.0") (choice (const :tag "Don't preserve push-remote setup" nil) (const :tag "Preserve push-remote setup" local-only) (const :tag "... and rename corresponding branch on remote" t) (const :tag "... but only if remote is on a forge" forge-only)) magit-branch-popup-show-variables #[0 "\300\207" [t] 1] "Whether the `magit-branch-popup' shows Git variables.\nThis defaults to t to avoid changing key bindings. When set to\nnil, no variables are displayed directly in this popup, instead\nthe sub-popup `magit-branch-config-popup' has to be used to view\nand change branch related variables." (magit . "2.7.0") boolean magit-published-branches #[0 "\300\207" [("origin/master")] 1] "List of branches that are considered to be published." (magit . "2.13.0") (repeat string)] 10)
|
#@56 Popup console for branch commands.
|
|
(fn &optional ARG)
|
(defalias 'magit-branch-popup #[256 "\300\301\302#\207" [magit-invoke-popup magit-branch-popup nil] 5 (#$ . 7538) "P"])
|
(defvar magit-branch-popup (byte-code "\300\301\302\303\304\305\306\307\310\311\312\313\314\315\316\317\320\321\322\323\324\310\325#?\205 \326BBBBBBBBBBBB\327\330\331\332\333\334\257\207" [:variable magit-branch-arguments :man-page "git-branch" :variables #[0 "\205 \207" [magit-branch-popup-show-variables magit-branch-config-variables] 1] :actions (98 "Checkout" magit-checkout) nil (67 "Configure..." magit-branch-config-popup) (108 "Checkout local branch" magit-branch-checkout) (115 "Create new spin-off" magit-branch-spinoff) (109 "Rename" magit-branch-rename) (99 "Checkout new branch" magit-branch-and-checkout) (110 "Create new branch" magit-branch-create) (120 "Reset" magit-branch-reset) (119 "Checkout new worktree" magit-worktree-checkout) (87 "Create new worktree" magit-worktree-branch) (107 "Delete" magit-branch-delete) require forge t ((121 "Checkout pull-request" magit-checkout-pull-request) (89 "Create from pull-request" magit-branch-pull-request)) :default-action magit-checkout :max-action-columns 3 :setup-function magit-branch-popup-setup] 23))
|
(byte-code "\300\301!\210\302\303\304\305\306DD\307\310\311\312\313&\207" [magit-define-popup-keys-deferred magit-branch-popup custom-declare-variable magit-branch-arguments funcall function #[0 "\301\302\"\207" [magit-branch-popup plist-get :default-arguments] 3] "" :group magit-git-arguments :type (repeat (string :tag "Argument"))] 8)
|
(defalias 'magit-branch-arguments #[0 "\303=\203 \207\n\207" [magit-current-popup magit-current-popup-args magit-branch-arguments magit-branch-popup] 2])
|
(put 'magit-branch-arguments 'definition-name 'magit-branch-popup)
|
#@16
|
|
(fn VAL DEF)
|
(defalias 'magit-branch-popup-setup #[514 "\302\"\210\303\304!!\210\305\306\307\310!\"\211\2056 \211@\311\312\313! >\204( \314\315\316D\"\210\317H!\320\"\210A\266\202\202 \207" [magit-popup-mode-map cl-struct-magit-popup-event-tags magit-popup-default-setup use-local-map copy-keymap -filter magit-popup-event-p magit-popup-get :variables local-set-key vector type-of signal wrong-type-argument magit-popup-event 1 magit-invoke-popup-action] 10 (#$ . 9361)])
|
#@299 Checkout REVISION, updating the index and the working tree.
|
If REVISION is a local branch, then that becomes the current
|
branch. If it is something else, then `HEAD' becomes detached.
|
Checkout fails if the working tree or the staging area contain
|
changes.
|
|
(git checkout REVISION).
|
|
(fn REVISION)
|
(defalias 'magit-checkout #[257 "\300\301\"\203 \302\303\"\262\304\305\"\207" [string-match "\\`heads/\\(.+\\)" match-string 1 magit-run-git "checkout"] 4 (#$ . 9850) (byte-code "\300\301!C\207" [magit-read-other-branch-or-commit "Checkout"] 2)])
|
#@131 Create BRANCH at branch or revision START-POINT.
|
|
(git branch [ARGS] BRANCH START-POINT).
|
|
(fn BRANCH START-POINT &optional ARGS)
|
(defalias 'magit-branch-create #[770 "\300\301$\210\302\"\210\303 \207" [magit-call-git "branch" magit-branch-maybe-adjust-upstream magit-refresh] 8 (#$ . 10407) (magit-branch-read-args "Create branch")])
|
#@149 Create and checkout BRANCH at branch or revision START-POINT.
|
|
(git checkout [ARGS] -b BRANCH START-POINT).
|
|
(fn BRANCH START-POINT &optional ARGS)
|
(defalias 'magit-branch-and-checkout #[770 "\301\302\303\304#)\266\203\203 \305\306\307$\207\310\311\312%\210\313\"\210\314 \207" [inhibit-changing-match-data "^stash@{[0-9]+}$" nil t string-match magit-run-git "stash" "branch" magit-call-git "checkout" "-b" magit-branch-maybe-adjust-upstream magit-refresh] 10 (#$ . 10754) (magit-branch-read-args "Create and checkout branch")])
|
#@465 Hybrid between `magit-checkout' and `magit-branch-and-checkout'.
|
|
Ask the user for an existing branch or revision. If the user
|
input actually can be resolved as a branch or revision, then
|
check that out, just like `magit-checkout' would.
|
|
Otherwise create and checkout a new branch using the input as
|
its name. Before doing so read the starting-point for the new
|
branch. This is similar to what `magit-branch-and-checkout'
|
does.
|
|
(fn ARG &optional START-POINT)
|
(defalias 'magit-branch-or-checkout #[513 "\300\301\"\203 \302\303\"\262\211\203 \304\305 #\207\306!\207" [string-match "\\`heads/\\(.+\\)" match-string 1 magit-branch-and-checkout magit-branch-arguments magit-checkout] 6 (#$ . 11305) (byte-code "\300\301!\211\302!?\205 \303\304\"D\207" [magit-read-other-branch-or-commit "Checkout" magit-rev-verify-commit magit-read-starting-point "Create and checkout branch"] 5)])
|
#@937 Checkout an existing or new local branch.
|
|
Read a branch name from the user offering all local branches and
|
a subset of remote branches as candidates. Omit remote branches
|
for which a local branch by the same name exists from the list
|
of candidates. The user can also enter a completely new branch
|
name.
|
|
- If the user selects an existing local branch, then check that
|
out.
|
|
- If the user selects a remote branch, then create and checkout
|
a new local branch with the same name. Configure the selected
|
remote branch as push target.
|
|
- If the user enters a new branch name, then create and check
|
that out, after also reading the starting-point from the user.
|
|
In the latter two cases the upstream is also set. Whether it is
|
set to the chosen START-POINT or something else depends on the
|
value of `magit-branch-adjust-remote-upstream-alist', just like
|
when using `magit-branch-and-checkout'.
|
|
(fn BRANCH &optional START-POINT)
|
(defalias 'magit-branch-checkout #[513 "\211\204 \300!\207\301 \203 \302\303!\210\304\305 #\210\306!\205B \307!\211@A\211\232\205> |