Git trees
Use the REST API to interact with tree objects in your Git database on GitHub.
About Git trees
A Git tree object creates the hierarchy between files in a Git repository. You can use the Git tree object to create the relationship between directories and the files they contain. These endpoints allow you to read and write tree objects to your Git database on GitHub.
Create a tree
The tree creation API accepts nested entries. If you specify both a tree and a nested path modifying that tree, this endpoint will overwrite the contents of the tree with the new path contents, and create a new tree structure.
If you use this endpoint to add, delete, or modify the file contents in a tree, you will need to commit the tree and then update a branch to point to the commit. For more information see «Create a commit» and «Update a reference.»
Returns an error if you try to delete a file that does not exist.
Parameters for «Create a tree»
Setting to application/vnd.github+json is recommended.
The account owner of the repository. The name is not case sensitive.
The name of the repository without the .git extension. The name is not case sensitive.
Objects (of path , mode , type , and sha ) specifying a tree structure.
The file referenced in the tree.
The file mode; one of 100644 for file (blob), 100755 for executable (blob), 040000 for subdirectory (tree), 160000 for submodule (commit), or 120000 for a blob that specifies the path of a symlink.
Can be one of : 100644 , 100755 , 040000 , 160000 , 120000
Either blob , tree , or commit .
Can be one of : blob , tree , commit
The SHA1 checksum ID of the object in the tree. Also called tree.sha . If the value is null then the file will be deleted.
Note: Use either tree.sha or content to specify the contents of the entry. Using both tree.sha and content will return an error.
The content you want this file to have. GitHub will write this blob out and use that SHA for this entry. Use either this, or tree.sha .
Note: Use either tree.sha or content to specify the contents of the entry. Using both tree.sha and content will return an error.
The SHA1 of an existing Git tree object which will be used as the base for the new tree. If provided, a new Git tree object will be created from entries in the Git tree object pointed to by base_tree and entries defined in the tree parameter. Entries defined in the tree parameter will overwrite items from base_tree with the same path . If you’re creating new changes on a branch, then normally you’d set base_tree to the SHA1 of the Git tree object of the current latest commit on the branch you’re working on. If not provided, GitHub will create a new Git tree object from only the entries defined in the tree parameter. If you create a new commit pointing to such a tree, then all files which were a part of the parent commit’s tree and were not defined in the tree parameter will be listed as deleted by the new commit.
Источник
Красивое git дерево в консоли (терминале)
Все кто работает с Git через какой-либо IDE, например, PhpStorm уже привыкли к виду
и забыли как работать с Git через консоль. А, как говорила моя учительница: «Если не знать, да еще и забыть. «.
В общем, PhpStom, конечно, штука хорошая, но чтобы посмотреть красивое дерево коммитов на удалённом сервере, к которому есть только ssh connect, PhpStorm не поможет. На этот случай можно воспользоваться следующей командой:
git log --graph --pretty=oneline --abbrev-commit --all --decorate Чтобы не забывать эту длинную команду, можно её запомнить:
alias gitlog='git log --graph --pretty=oneline --abbrev-commit --all --decorate'
Вместо gitlog вы можете вписать любой алиас, который потом будете использовать.
Эта команда позволяет показывать коммиты из локальных и удаленных веток в текстовом формате.
$ gitlog * 342e16b (HEAD, master) Up to 8.17 | * eafaa80 (origin/master) Drupal up to 8.1.5 |/ * eaa6150 Merge branch 'master' of /home/***/repos/mbaev.com |\ | * ac9bace Add highlight for css * | 738fc2a Fix for VideoEmbedWysiwyg (rss) |/ * 9d8f642 Disallow translations and admin pages from index * d6d35af Disallow translations and admin pages from index * 327d112 Update modules * 0c0b925 Updated modules * 0671c01 Up to 8.1.1 and add video embed * 6e7bbc3 Theming search * 9be03a0 Beautify theme .
Бонус
Чтобы отобразить определенное количество коммитов необходимо указать флаг -n.
Источник
Просмотр ветвей в репозитории
Ветви являются центральным элементом совместной работы в GitHub, и их лучше всего просматривать на странице ветвей.
- На GitHub.com перейдите на главную страницу репозитория.
- В представлении дерева файлов слева выберите раскрывающееся меню ветвь
, а затем щелкните Просмотреть все ветви. Вы также можете найти раскрывающееся меню ветви в верхней части интегрированного редактора файлов.
- Ваши ветви. В репозиториях, в которых у вас есть доступ на отправку, в представлении Ваши отображаются все ветви, в которые вы отправляли код, за исключением ветви по умолчанию. Ветви упорядочены по самым новым.
- Активные ветви**. В** активном представлении отображаются все ветви (за исключением ветвь по умолчанию), которые кто-либо зафиксировал в течение последних трех месяцев, упорядоченные по ветвям с самыми последними фиксациями.
- Устаревшие ветви. В представлении Устаревшие отображаются все ветви, в которые никто не отправлял фиксации за последние три месяца. Ветви упорядочены по самым старым фиксациям. Используйте этот список, чтобы определить, какие ветви следует удалить.
- Все ветви. В представлении Все отображается ветвь по умолчанию, а затем все остальные ветви, упорядоченные по ветвям с самыми новыми фиксациями.
Дополнительные материалы
Источник
Github посмотреть дерево веток
Changes in the git-ls-tree manual
- 2.36.1 → 2.41.0 no changes
- 2.36.0
04/18/22 - 2.30.1 → 2.35.8 no changes
- 2.30.0 12/27/20
Check your version of git by running
NAME
git-ls-tree — List the contents of a tree object
SYNOPSIS
git ls-tree [-d] [-r] [-t] [-l] [-z] [--name-only] [--name-status] [--object-only] [--full-name] [--full-tree] [--abbrev[=]] [--format=] […]
DESCRIPTION
Lists the contents of a given tree object, like what «/bin/ls -a» does in the current working directory. Note that:
- the behaviour is slightly different from that of «/bin/ls» in that the denotes just a list of patterns to match, e.g. so specifying directory name (without -r ) will behave differently, and order of the arguments does not matter.
- the behaviour is similar to that of «/bin/ls» in that the is taken as relative to the current working directory. E.g. when you are in a directory sub that has a directory dir, you can run git ls-tree -r HEAD dir to list the contents of the tree (that is sub/dir in HEAD ). You don’t want to give a tree that is not at the root level (e.g. git ls-tree -r HEAD:sub dir ) in this case, as that would result in asking for sub/sub/dir in the HEAD commit. However, the current working directory can be ignored by passing —full-tree option.
OPTIONS
Show only the named tree entry itself, not its children.
Show tree entries even when going to recurse them. Has no effect if -r was not passed. -d implies -t .
Show object size of blob (file) entries.
\0 line termination on output and do not quote filenames. See OUTPUT FORMAT below for more information.
List only filenames (instead of the «long» output), one per line. Cannot be combined with —object-only .
List only names of the objects, one per line. Cannot be combined with —name-only or —name-status . This is equivalent to specifying —format=’%(objectname)’ , but for both this option and that exact format the command takes a hand-optimized codepath instead of going through the generic formatting mechanism.
Instead of showing the full 40-byte hexadecimal object lines, show the shortest prefix that is at least hexdigits long that uniquely refers the object. Non default number of digits can be specified with —abbrev=.
Instead of showing the path names relative to the current working directory, show the full path names.
Do not limit the listing to the current working directory. Implies —full-name.
A string that interpolates %(fieldname) from the result being shown. It also interpolates %% to % , and %xx where xx are hex digits interpolates to character with hex code xx ; for example %00 interpolates to \0 (NUL), %09 to \t (TAB) and %0a to \n (LF). When specified, —format cannot be combined with other format-altering options, including —long , —name-only and —object-only .
When paths are given, show them (note that this isn’t really raw pathnames, but rather a list of patterns to match). Otherwise implicitly uses the root level of the tree as the sole path argument.
Output Format
The output format of ls-tree is determined by either the —format option, or other format-altering options such as —name-only etc. (see —format above).
The use of certain —format directives is equivalent to using those options, but invoking the full formatting machinery can be slower than using an appropriate formatting option.
In cases where the —format would exactly map to an existing option ls-tree will use the appropriate faster path. Thus the default format is equivalent to:
%(objectmode) %(objecttype) %(objectname)%x09%(path)
This output format is compatible with what —index-info —stdin of git update-index expects.
When the -l option is used, format changes to
%(objectmode) %(objecttype) %(objectname) %(objectsize:padded)%x09%(path)
Object size identified by is given in bytes, and right-justified with minimum width of 7 characters. Object size is given only for blobs (file) entries; for other entries — character is used in place of size.
Without the -z option, pathnames with «unusual» characters are quoted as explained for the configuration variable core.quotePath (see git-config[1]). Using -z the filename is output verbatim and the line is terminated by a NUL byte.
It is possible to print in a custom format by using the —format option, which is able to interpolate different fields using a %(fieldname) notation. For example, if you only care about the «objectname» and «path» fields, you can execute with a specific «—format» like
git ls-tree —format=’%(objectname) %(path)’
FIELD NAMES
Various values from structured fields can be used to interpolate into the resulting output. For each outputing line, the following names can be used:
The type of the object ( commit , blob or tree ).
The size of a blob object («-» if it’s a commit or tree ). It also supports a padded format of size with «%(objectsize:padded)».
The pathname of the object.
Источник