Saravanan666/pypi-org huggingface dataset:
Package: gitvier
Gitvier is a CLI “component management” tool for when you’ve got a container repository and then that repository relies
on a bunch of components to operate, which you’re then actively working on those components. As such, it aims to allow
the user to try and manage these components, allowing for installing, updating, etc. as well as running commands over
some/all components. However, it differs from something like GitMan in that it will not explicitly revert dependencies
to specified revisions unless explicitly forced as most likely if you install a component on “master” and the
component is currently on branch “develop”, if you run “gitvier update”, you don’t expect that component to be put back
onto master, but rather that maybe just do a git pull on this component (and all others). I primarily built this
to support the usecase ofSubmittyand for my research projects.This borrows concepts heavily fromGitManwhich is a great dependency
manager with Git, but less useful as a “component manager” (hence the existance of this tool).DependenciesPython 3.5+GitOthers?InstallationFrom Pip:pip3 install gitvierFrom Source:git clone https://github.com/MasterOdin/gitvier
python3 setup.py installUsage$ gitvier --help
usage: gitvier [-h] [-V] <command> ...

A component manager based where your components live in Git.

positional arguments:
  <command>
    init         Initialize a new gitvier directory

optional arguments:
  -h, --help     show this help message and exit
  -V, --version  show program's version number and exitGitvier Config FileGitvier operates over a.gitvier.ymlconfig file which contains the various components of our system. At the root
level you can specify alocation(defaults to current directory if omitted) where all components would live andcomponentswhich is a list of components which contain the following elements:name: <component_name/subfolder where component will be installed to>
repo: <git_url>
rev: <branch or tag or commit hash or branch/tag@timestamp>
commands: <list of bash commands to run after install/update> (optional)An example of a.gitvier.ymlfile (taken fromSubmitty):location: .
components:
- name: RainbowGrades
  repo: https://github.com/Submitty/RainbowGrades
  rev: master
- name: grading
  repo: https://github.com/Submitty/AutoGrading
  rev: master
Package: gitvtag
Simple and straightforward version tagging with Git. Version tags are
tags in the following format:v<major>.<release>.<build>(actually, the number of the components can be variable, we are only
dealing with the last component)InstallingTo install the released version:> pip install git-vtagRunningThe command has built-in help:> git vtagDevelopment versionTo install the code in development mode:> git clone <git-repository-address>
> cd git-vtag
> python setup.py developTip: if you are using virtual environment and autoenv, you may want
to set up the .env file, for example:env_dir=./.venv
echo activate $env_dir
source $env_dir/bin/activate`Apache LicenseCopyright (C) 2016Sasha OvsankinLicensed under theApache License, Version 2.0. See the file ‘LICENSE’ for details.
Package: gitwalker
What is this?gitwalkeris a tool for collecting data from git repositories. It automates
the process of checking out each revision, running some command and logging the
output to a JSON file. Additional commands can be added by writing Python classes.What can it do?Currently _gitwalker_ supports two built in commands:A LaTeX word countdu disk usage commandArbitrary shell commandsIts straightforward to add additional commands - see the filetools.pyThe included scriptgitwalk_plotuses the
[matplotlib](http://matplotlib.sourceforge.net/index.html) framework to produce
time-series graphs overlaying multiple data files.Getting ItIf you havepipinstalled, simplypip install gitwalkerUsageTo word count a git-tracked LaTeX project across all commits:gitwalk –wordcount myfile.tex –out wordcount.json /path/to/projectThis will clone the repository at/path/to/projectto a temporary directory
before checking out each revision and running a word count on the file
myfile.tex in the repository. The results will be output to the filewordcount.jsongitwalkeralso supports incremental update of a previously produced log file. To add newly committed revisions,gitwalk –update wordcount.json –wordcount myfile.tex /path/to/projectThere is an attached script to plot a number of such output files on the same
axes using matplotlib. e.g.gitwalk_plot –plot file1.json me red –plot you.json you blue wordcount/wordcountWill plot the filesfile1.jsonandfile2.jsonon the same axes using the
specified labels and colours. The value will be dug out from the JSON file via
the path format at the end of the command line - in this casewordcount/wordcount. One could also rungitwalk_plot –plot file1.json me red –plot you.json you blue wordcount/nfiguresto plot the number of LaTeX figures present in each commit.To run a shell command on each commit,gitwalk –shell=”ls | wc -l” /path/to/projectTodoAdd git-notes option
Package: gitwatch
gitwatchShort blurb about what your product does.One to two paragraph statement about your product and what it does.InstallationOS X & Linux:pip3installgitwatchWindows:pipinstallgitwatchUsage exampleA few motivating and useful examples of how your product can be used. Spice this up with code blocks and potentially more screenshots.For more examples and usage, please refer to theWiki.Development setupDescribe how to install all development dependencies and how to run an automated test-suite of some kind. Potentially do this for multiple platforms.pipinstall--editablegitwatchDocumentation-Read the Docs-WikiMetaStephen R A King :stephen.ra.king@gmail.comDistributed under the MIT license. Seelicensefor more information.https://github.com/Stephen-RA-King/gitwatch
Package: git-watcher
InstallTo install git-watcher, simply:$pipinstallgit-watcherUsageusage:git-watcher[-h][-v][-iIP][-pPORT]-uREPO_URL[-bBRANCH]-sSECRET[-dDIR]git-watcheroptionalarguments:-h,--helpshowthishelpmessageandexit-v,--versionshowprogram'sversionnumberandexit-iIPlistenipaddress-pPORTlistenport-uREPO_URLgitrepositoryurl-bBRANCHwatchbranch-sSECRETsecretkeyofwebhook-dDIRlocalrepositorydirectoryPlatform SupportLinux/Mac OS supportArticles利用git-watcher让百度索引你的github博客LicenseThe MIT License (MIT)Copyright (c) 2016 Michael JiangPermission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the “Software”), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Package: git-webhook
git-webhook is a web app base onPython Flask + SQLAchemy + Celery + Redis + React.Aims to deploy a git webhook platform easily,now supports  Github / GitLab / Gogs / GitOscHow to deploy & run ?> pip install git-webhookgitwebhook config : will init config into HOME dir, then modify itgitwebhook runserver : run web server, with default port 18340gitwebhook celery : run celery task> then visit ip:18340
Package: git-web-url
Welcome togit_web_urlDocumentationgit_web_urlis a CLI tool and also a Python library can print the url of a local file in a git repo so you can one-click to open it in web browser.Currently it supports:GitHubGitHub EnterpriseGitLabGitLab EnterpriseBitBucketBitBucket EnterpriseAWS CodeCommitUsage ExampleAuto-discover the git repo:cd into your git repo directory, or any folder inside, then rungwu, it prints the url for the current branch and the current directory:$gwu# or gitweburlhttps://github.com/your_account/your_repo/tree/your_branch/path/to/current_directoryExplicitly specify the file or folder:copy the absolute path of the file or folder in your local git repo, then rungwu ${absolute_path_here}:$gwu/Users/myusername/GitHub/your_repo/path/to/your_filehttps://github.com/your_account/your_repo/tree/your_branch/path/to/current_directoryInstallgit_web_urlis released on PyPI, so all you need is to:$pipinstallgit-web-urlTo upgrade to latest version:$pipinstall--upgradegit-web-url
Package: git-whatsup
# git-whatsupList up remote branches that conflict with the current working copy.Requires Python 3.5+ and pygit2.```$ brew install libgit2$ pip install git-whatsup$ git-whatsupconflicts with me------------------------------------------------------------origin/find-the-leaks (M!)spec/spec_helper.rb Capp/assets/cactus.png deleted by us```How it works:- Create a commit on top of the current index with all unstaged changes- Tag the commit with `whatsup-with-me`- For each remote branch,- Try merging with `whatsup-with-me`- If it conflicts, try merging with `origin/master`- Based on the results, classify into roughly these categories:no conflicts, conflicts with my changes, or conflicts with just master- Output those that conflict with my changes- Output conflicting diffs too if requested## Usage```$ git-whatsup --helpusage: git-whatsup [-h] [--remote REMOTE_NAME] [--master BRANCH_NAME][--branch BRANCH_NAME] [--all] [--diff][--format {plain,json}][repo_path]List up remote branches that conflict with the current working copy.positional arguments:repo_path             target Git repositoryoptional arguments:-h, --help            show this help message and exit--remote REMOTE_NAME  compare against branches in this remote--master BRANCH_NAME  master branch name--branch BRANCH_NAME, -b BRANCH_NAMEbranches to check. by default, all branches arechecked--all, -a             output all statuses if output format is `plain`--diff, -d            output diffs if output format is `plain`--format {plain,json}, -f {plain,json}json always includes diffs```## Assumptions and caveats- Remote branches in your local clone are assumed to be up-to-date (`git fetch` has been run)- Consider this alpha software
Package: git-wipe
The problemFrom time to time if you have many forks and do many pull requests it is inevitable that you will have stale branches. And as time marches on the number of these branches across forks can become big.The answergit-wipeis simple command line tool to cleanup your Github fork branches.Install$ pip install git-wipeUsageIn order to usegit-wipefirst you need to create yourPersonal Access Token.You can set this token to your environment variable:$ export GIT_WIPE_TOKEN=your_access_tokenAnd then you can easily:$ git-wipe cleanup
Searching for branches. This may take a while...
Founded branches:

povils/repo_1/Branch_1
povils/repo_1/Branch_2
povils/repo_2/Branch_1
povils/repo_3/Branch_1

Total: 4
Delete these branches? [y/N]: yOther options--token              instead of environment
--preview            just to preview merged branches
--timeout            set connection timeout. Default 30 seconds
--skip-repository    skip repository you don't want to search. Multiple
--skip-branch        skip branch you don't want to delete. Multiple
--no-interaction     do not ask any interactive questionExample:$ git-wipe cleanup --skip-repository=repo_1 --skip-branch=develop --no-interactionThis command will clean all merged branches without interaction, except from fork with name ‘repo_1’ and except all branches with name ‘develop’Note:Only forks where you areownerwill be involved in search. Alsomaster branches will never be deleted!
Package: git-word-blame
git-word-blameShow word-by-word authors of a fileDemoExecutinggit word-blame git.con thegitrepository we get:word-blame-by-commit.htmlword-blame-by-author.htmlauthors_stats.tsvcommit_stats.tsvInstallationpip install git-word-blameUsagegit word-blame <path/to/my/file>It will produce the following files (by default in/tmp/git-word-blame/):- author_stats.tsv         # top authors by number of characters attributed to them
- commit_stats.tsv          # same for commits
- word-blame-by-commit.html # hover on some text to see which commit created it
- word-blame-by-author.html # same for authors
- text-output # tokens grouped by authors as a grep-friendly outputAuthorship algorithmsTwo algorithms are available:wikiwho(default): coarse but more robustmwpersistence: precise but with more false-positivesTo change the engine used bygit word-blame:git config --global word-blame.engine mwpersistenceHTML outputYou can choose between 3 themes for the HTML output:black-and-white,solarized-dark,solarized-light.git config --global word-blame.theme solarized-darkBy default a git command is shown when clicking on the text, you can change this behavior and make it go to the diff online (Github/Framagit) directly:git config --global --bool word-blame.link-to-online-commit trueLimitsgit-word-blamedoesn't supportrenamesfor now and is only tested on files with a linear history.There's also a default maxmum of2000commits processed. This can be removed with this command:git config --global word-blame.limit 0.WikiWhodoes not yet, to my knowledge, support attributing white-space, it's attributed to the token coming after it.See alsohttps://github.com/wikiwho/WikiWho/andhttps://github.com/wikiwho/WhoColorA word-by-word blame for Wikipedia with a well tested algorithm for prose (default algorithm)
The HTML vizualisation of this project is heavily inspired by WhoColorhttps://github.com/mediawiki-utilities/python-mwpersistence/An alternative authorship algorithm detection made also for Wikipediahttps://github.com/d33tah/wordblameExport Wikipedia articles to git to perform a word-by-word blame, it does that by
putting each word in a separate line for each file in the historyhttps://github.com/lucadealfaro/authorship-trackingAnother altenative not yet integratedhttps://github.com/git-persistence/git-persistenceA character-by-character authorship oriented towards scoring the authors on a whole repository
Package: git-workout
Git WorkoutA git plugin to shift your commits out of work hours.Or at least it will be.Currently this command just prints "Hello, World."Ofcourseyou're a responsible developer, and you never work on your own stuff during working hours. Youneverget that craving to just throw something together late on a Friday afternoon.
But imagine youdid- you couldn't publish your git repo, because you committed during working hours!git workout... now your commits are shifted to after 6pm, and you're free to push to your public repo of choice,
without your boss ever finding out.
Package: gitwrapperlib
A lightweight wrapper around the git command using sh module.Documentation:https://gitwrapperlib.readthedocs.org/en/latestDevelopment WorkflowThe workflow supports the following stepslinttestbuilddocumentuploadgraphThese actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the projectOnce the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call$ _tag –minorwhich would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.So the full workflow after git is initialized is:repeat as necessary (of course it could be test - code - lint :) )codelinttestcommit and pushdevelop more through the code-lint-test cycletag (with the appropriate argument)buildupload (if you want to host your package in pypi)document (of course this could be run at any point)Important InformationThis template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of thisdo notsimple call$ python setup.py sdist bdist_eggas this will produce an unusable artifact with files missing.Instead use the provided build and upload scripts that create all the necessary files in the artifact.Project FeaturesTODOHistory0.0.1 (02-01-2018)First code creation0.9.3 (02-06-2021)Bumped dependencies.0.9.4 (07-07-2021)Added pipeline.0.10.0 (02-12-2021)Implemented optional tty output.0.10.1 (02-12-2021)Updated self referencial dependency for to pipeline tooling.0.10.2 (06-12-2021)Fix for tty_output in lambda contexts.0.10.3 (06-12-2021)Self reference update for pipeline.1.0.0 (21-03-2022)Removed references to master branch and implemented default remote retrieval, courtesy of Sten Spans <sspans@schubergphilis.com>1.0.1 (13-06-2023)Bump dependencies and update pipeline to python 3.9.1.0.2 (13-06-2023)Bump dependencies.1.0.3 (13-06-2023)Fix for branch and filename conflict.1.0.4 (12-01-2024)Bump dependencies.
Package: git-ws-repo
Documentation-PyPI-Sources-IssuesGoogle's git-repo replacement powered by git-ws-repoTODO📦 InstallationGit Workspace Repo is written in Python.RecommendedPlease install python and then try:curl-Lhttps://github.com/pypa/pipx/releases/latest/download/pipx.pyz-opipx.pyz&&python3pipx.pyzinstallgit-ws-repoMaybe you need run:python3pipx.pyzensurepathviapipxIf you already installedpipx(https://pypa.github.io/pipx/installation/) just run:pipxinstallgit-ws-repoMaybe you need run:pipxensurepathviapippipinstallgit-ws-repoFor testing you can try:repo--version
Package: gitx
A simple tool that help you speed up git clone.InstallDebian / Ubuntu:sudo pip install gitxCentOS / RedHat:sudo pip install gitxMAC OS:sudo pip install gitxUsageInit tool with proxy url,like:gitx proxy_set http://username:appkey@server:portSet git exec file path,like:gitx path_set /usr/bin/gitClone example respository:gitx clone https://github.com/jankari/exampleCheck gitx version:gitx --versionTestPlatform: Mac OS X 10.11,Ubuntu 16.04,CentOS 7
Package: git-x
LicenseCIPackagesgit-x - a set of handy git extensions.Installationpip install git-x --upgradeHow to UseShow help  messageRungit-x, or ignore the-ingit-x:gitxIt will output the help message, which showing all the available commands:$gitxUsage:git-x[OPTIONS]COMMAND[ARGS]...Options:-hShowthismessageandexit.Commands:aAddfilecontentstotheindexamendAmendfilesintorepositorybShowcurrentbranchnameciCommitalltheindexedfilesciaAddfilesintoindexandcommitclbCleanmergedlocalbranch.coCheckout/CreatebranchllgShowrecent<number>logsmMergecodesfrombranch<from>tocurrentbranchpPulllatestcodeprCreatepullrequestfromcurrentbranchto<to_branch>stShowtheworkingtreestatusupCreateremotebranchNote: If you have an exe likegit-x.exein windows, orgit-x.shin linux or mac, you can run the command withgit xdirectly. This is handled by git.Run commandsgit-xincludes a list of commands, let’s takestas an example:There are several ways to run the command:1. Run withgit-xRungitxst-hOr,git-xst-hIt will output the help doc ofstcommand:$ git x st -h
Usage: git-x st [OPTIONS]

  Show file status, same as 'git status'

Options:
  -h  Show this message and exit.2. Run withgit-orgitYou may see that in the Usage line, it showsgit-st, which means that you can run the commands listed above withgit-:git-st-hOr, even run withgit:gitst-hThey both output the help doc ofstcommand:$git-st-hUsage:git-st[OPTIONS]Showfilestatus,sameas'git status'Options:-hShowthismessageandexit.Usages of all commandsPlease read theUsageto see all the available commands.Notice:You need to install git cli tool first, as all the commands will call the native git commands eventually.Finally, happygit-ing withgit-x.
Package: gity
# gity[![Build Status](https://travis-ci.org/Mnw2212/gity.svg?branch=master)](https://travis-ci.org/Mnw2212/gity)```_ ___ _(_) |_ _   _/ _` | | __| | | || (_| | | |_| |_| |\__, |_|\__|\__, ||___/       |___/```The git magician for python. gity makes using git commands in python, a piece of cake.Most existing Python modules for for interacting with git repositories are extremely verbose and cumbersome.Python doesnt have a builtin module and with the existing ones it requires tremendous amount of documentation digging to get hold of the simplest functions.Things shouldn't be this way. Not in Python.![](http://i.imgur.com/Qn2jHxx.gif)## Features- Written in uncomplicated Python- Easy to [install](https://github.com/mnw2212/gity#installation)- Works on Linux and Mac## Current Support- git init- git clone- git status- git add- git commit- git push- git pull- git checkout## Installation### Option 1: [Pip](https://pypi.python.org/pypi/gity)```bash$ pip install gity```### Option 2: From source```bash$ git clone --recursive git@github.com:mnw2212/gity.git$ cd gity/$ python setup.py install```## Usage```pythonfrom gity import gityobj = gity()obj.git_add(deletion=True)message = "inital commit"obj.git_commit(message)```## Contributing#### Bug Reports & Feature RequestsPlease use the [issue tracker](https://github.com/mnw2212/gity/issues) to report any bugs or file feature requests.#### DevelopingPRs are welcome. To begin developing, follow this:```bash# make virtual env$ git clone --recursive git@github.com:Mnw2212/gity.git$ cd gity/$ python gity/gity.py```
Package: gitzip
gitzipExport all the changed files between two git commits or branches to a zip file including
the directory structure.gitzip usagegitzipallows to copy all files that changed between two commits (or branches) into a
zip file.Expect a git repository being at commit0c321f2. If two new files are created, e.g.README.mdanddocs/screenshot.jpg,git statusgives:$gitstatus
Onbranchmaster

Changesnotstagedforcommit:(use"git add <file>..."toupdatewhatwillbecommitted)(use"git restore <file>..."todiscardchangesinworkingdirectory)modified:README.mdnew:docs/screenshot.jpgAfter committing those changes, the commandpython -m gitzip export.zip 0c321f2will create aexport.zipfile. This file contains all files that changed between commit0c321f2and the currentmasterbranch. So in the given example, the zip file will
have the following structure:📦export.zip
 ┣ 📂docs
 ┃ ┗ 📜screenshot.jpg
 ┗ 📜README.mdThe files will have the contents that are currently checked out in the repository.InstallationViapippipinstallgitzipFrom sourceTo run this program from the code directly,pythonandpoetry(pip install poetry) are required. Clone or
download the repository.To install all the dependencies, use your command line and navigate to the directory
where thisREADMEfile is located in. Then runpoetryinstallFor developmentFor development installation perform theFrom sourceinstallation.For installing new packages, always runpoetry add <pip-package-name>instead ofpip install <pip-package-name>.Launch the program either check out theExecutionsection or use theRun and Debug-side panel of VSCode.If the interpreter of the virtual environment does not show up in VSCode, add it manually. The virtual environments are located in{cache-dir}/virtualenvs/<venv-name>/Scripts/python.exewhere the{cache-dir}depends on the operating system (~/.cache/pypoetry,~/Library/Caches/pypoetryorC.\Users\%USERNAME%\AppData\Local\pypoetry\Cache).ExecutionTo execute the program usepoetryrunpython-mgitzip