o {gO@sddgZddlZddlZddlmZddlmZmZddlm Z ddl m Z m Z dd l mZe rqS)r).0xrrw/var/www/bot.gig.net.ua/public_html/telegram/P1/HellBot/venv/lib/python3.10/site-packages/git/objects/submodule/root.py !szRootUpdateProgress.rN) __name__ __module__ __qualname____doc__ranger _num_op_codesREMOVE PATHCHANGE BRANCHCHANGE URLCHANGE __slots__rrrrrs cseZdZdZdZdZdfdd Zdd d Z   ddee e dfde de de de dedde de de ddfddZ dddZ ZS) rzA (virtual) root of all submodules in the given repository. This can be used to more easily traverse all submodules of the superproject (master repository). r__ROOT__repor returnNc s4tj||j|jd|j|jjdtj |j ddS)N)binshamodepathname parent_commiturl branch_path) super__init__ NULL_BIN_SHAk_default_mode k_root_nameheadcommitgitHead to_full_pathk_head_default)selfr  __class__rrr+<s  zRootModule.__init__cCsdS)zMay not do anything.Nrr5rrr _clear_cacheIszRootModule._clear_cacheTFprevious_commit recursive force_removeinitto_latest_revisionprogress)Nrdry_run force_reset keep_goingc ( s2|jjrtd|durt}d} |rd} |j} z2| jj} |durBz| | jdj}|j|j kr5t Wnt yA| }Ynw| |}|j | |d} | | }t | }t |}||}t |}t|D]C\}}t}|dkru|tO}||||| d|j|jf| jj|_|jd d ||d ||d kr|tO}||||| d |jqg||@}t |}t|D]\}}| |j}||jj|jkr|r|ttB||| dj|jjf|s|jjd d d|ttB||| djrIj|jkrd}}|j}t fdd|Ddkr|ttB||| dj|jjf|s|dd|DvsDJ||j}|j |dt fdd|j!Ddkrjt"dj#jfd}|D]}|j|jkr{|}nqn|durt |d kr|d}ntd|j|j} |$||%| j}!d }"|j!|j#}#|#j&D] }$|$j|!krd }"nq|"st'(dj)|#jj_|ttB||| djj*|j*krI|tt+B||| dj|j*j*f|s:}|j}%|%D] }|j |dqz t,j-j.|j#dd}&Wnt/y,t,-|j*}&Ynw|&0t1|%j#|&|j_2|tt+B||| djqWnt3yi}'z| sXt'4t5|'WYd}'~'nd}'~'ww|D]*jd |||||| d |rrt6|jd ||||||| d!ql|S)"a+ Update the submodules of this repository to the current HEAD commit. This method behaves smartly by determining changes of the path of a submodule's repository, next to changes to the to-be-checked-out commit or the branch to be checked out. This works if the submodule's ID does not change. Additionally it will detect addition and removal of submodules, which will be handled gracefully. :param previous_commit: If set to a commit-ish, the commit we should use as the previous commit the HEAD pointed to before it was set to the commit it points to now. If ``None``, it defaults to ``HEAD@{1}`` otherwise. :param recursive: If ``True``, the children of submodules will be updated as well using the same technique. :param force_remove: If submodules have been deleted, they will be forcibly removed. Otherwise the update may fail if a submodule's repository cannot be deleted as changes have been made to it. (See :meth:`Submodule.update ` for more information.) :param init: If we encounter a new module which would need to be initialized, then do it. :param to_latest_revision: If ``True``, instead of checking out the revision pointed to by this submodule's sha, the checked out tracking branch will be merged with the latest remote branch fetched from the repository's origin. Unless `force_reset` is specified, a local tracking branch will never be reset into its past, therefore the remote branch must be in the future for this to have an effect. :param force_reset: If ``True``, submodules may checkout or reset their branch even if the repository has pending changes that would be overwritten, or if the local tracking branch is in the future of the remote tracking branch and would be reset into its past. :param progress: :class:`RootUpdateProgress` instance, or ``None`` if no progress should be sent. :param dry_run: If ``True``, operations will not actually be performed. Progress messages will change accordingly to indicate the WOULD DO state of the operation. :param keep_going: If ``True``, we will ignore but log all errors, and keep going recursively. Unless `dry_run` is set as well, `keep_going` could cause subsequent/inherited errors you wouldn't see otherwise. In conjunction with `dry_run`, this can be useful to anticipate all errors when updating submodules. :return: self z-Cannot update submodules in bare repositoriesNr"z DRY-RUN: )r'rzRemoving submodule %r at %sFT) configurationmoduleforcer@rzDone removing submodule %rz/Moving repository of submodule %r from %s to %s)rErDz&Done moving repository of submodule %r__new_origin__csg|] }|jjkr|qSr)r(rrsmrrr z%RootModule.update..z*Changing url of submodule %r from %s to %scSsg|]}|jqSr)r&rHrrrrs)r?csg|] }|jjkr|qSr) remote_head branch_namerHrJrrrrLzISubmodule branch named %r was not available in new submodule remote at %rz,Couldn't find original remote-repo at url %rzCurrent sha %s was not contained in the tracking branch at the new remote, setting it the the remote's tracking branchz"Done adjusting url of submodule %rz-Changing branch of submodule %r from %s to %szbranch: Created from HEAD)logmsgz$Done changing branch of submodule %r)r;r=r>r?r@rFrB)r;r<r=r>r?r@rArB)7r barerrr/r0 log_entry oldhexshar#r, IndexError list_itemssetlen enumeraterBEGINupdater&abspath_parent_commitremoveENDr% module_existsrmover(rEremotesr create_remotefetchrefs ValueErrorrN delete_remoterenametraverse_loggerwarninghexshar)rr1r2createOSErrorset_tracking_branchr reference Exceptionerrorstrtype)(r5r:r;r<r=r>r?r@rArBprefixr cur_commitpsmssmsspsmsssmsrrsmlen_rrsmirsmopcsmslen_csmscsmpsmnnsmmrmtssmrrmt_for_deletionremote orig_namesmshafoundrrefcsmmrtbrerrrrJrrYOs|I                       ? zRootModule.updatecCs|jS)z8:return: The actual repository containing the submodules)r r8rrrrEszRootModule.module)r r r!N)r!N) NTFTFNFFF)r!r )rrrrrr.r+r9r r rqboolrYrE __classcell__rrr6rr1sN     )__all__loggingr1git.excrbaserrutilrtypingr r git.typesr git.repor git.utilr getLoggerrrhrrXr]rrrrrrrrrs(