Saravanan666/pypi-org huggingface dataset:
Package: git-tidbit
# git-tidbitGit a tidbit everytime you successfully commit to a repo.![Showcase](https://github.com/savala/git-tidbit/blob/master/screenshots/screenshot.png)#Install```pip install git-tidbit```*If you have trouble on OS X due to permissions, try out `pip install --user git-tidbit`Once installed, you'll need to run `git init` in your existing repositories to pull in ourpost-commit hook. If you'd like to do this for all of your existing repos, use the following:`find /my/dev/folders -name .git -type d -prune -execdir git init \;`#UninstallOnce uninstalled, git-tidbit will clean up after itself. You can double check it's cleanliness by looking at your git config for the `init.templatedir` entry.#Develop1. Clone the repo2.```shgit clone https://github.com/savala/git-tidbit.git```3.```shsudo pip install -e ./git-tidbit```# UsageUse your normal git workflow. Whenever you commit, you'll learn something new!```shgit commit -m "I'm really just doing this to get a snapple fact"```# Tidbit SourcesAll tidbit modules **must** implement a `get_tidbit` functionthat returns a string. They are free to implement that functionality however they please~## RedditReddit service fetches a random TIL (Today I learned)## SnappleRandom snapple cap fact## FortuneYou'll need `fortune` installed. You can get it with your favorite package manager:```brew install fortuneyum install fortuneapt-get install fortune fortune-modpacman -S fortune-mod```####### *Try out cowsay!*
Package: git-tidy
git-tidyis a set of git extensions for:Keeping your git logs tidy with ease.gittidy-commitguides
users through a structured commit with a configurable schema.gittidy-squashsquashes messy commits into one tidy commit.Linting a commit log.gittidy-lintverifies that commits
match the schema. If a user usesgittidy-commit, commits
willalwaysvalidate.Rendering a commit log.gittidy-logcan render commits from
any range and can render structured commits from a configurableJinjatemplate.
Want to automatically generate release notes?gittidy-logcan
be configured to group and render commits based on the schema.DocumentationView the git-tidy docs herefor a complete tutorial on usinggit-tidy.Installationgit-tidycan be installed a number of ways. The preferred way
on OSX is withhomebrewbrew tap jyveapp/homebrew-tap
brew install git-tidyIf not on OSX, one can installgit-tidysystem-wide withpipx:pipx install git-tidygit-tidycan also be installed with pip. Be sure to install it system-wide
so thatgit-tidy’s execution is not tied to a virtual environment:pip3 install git-tidyNotegit-tidydepends on git at a version of 2.22 or higher. OSX
users can upgrade to the latestgitversion withhomebrewusingbrew install git.Contributing GuideFor information on setting up git-tidy for development and
contributing changes, viewCONTRIBUTING.rst.Primary Authors@wesleykendall (Wes Kendall)@tomage (Tómas Árni Jónasson)
Package: git-timemachine
git-timemachineA command-line tool that helps you record commits onGitrepositories at
any time node.FeaturesShow commit logs of a repository in specified format.Record a commit on repository at the specified time node.Review commit logs.Limit maximum commits per day.InstallationTo install git-timemachine, you can:Install git-timemachine viapip:pip install --user --upgrade git-timemachineDownload fromReleases, make sure commandgit-timemachineis in
your$PATHenvironment variable.LicenseCopyright (C) 2022 Garrett HEgarrett.he@hotmail.comThe GNU General Public License (GPL) version 3, seeCOPYING.
Package: git-timespent
git-timespentEstimate worked hours per author in a git repo. Python 3, no dependencies.Installationpipinstallgit-timespentUsage# defaults to current directory$python-mtimespent#  1. Giovanni Paolo                35m51s (   7 commits)# or specify a path and number of authors$python-mtimespent/tmp/numpy-k5#  1. Charles Harris                  5w3d (7030 commits)#  2. Travis Oliphant                2w22h (2047 commits)#  3. Eric Wieser                    1w12h (1288 commits)#  4. Pearu Peterson                  1w3h (1126 commits)#  5. Mark Wiebe                     5d15h ( 798 commits)
Package: git-timewarp
git-timewarpOftentimes it's neccessary to go back to a previous commit. Perhaps you broke sometime and want to see where, or perhaps you want to benchmark an old version of a function. It's easy togit checkout, but what if you want to use two different versions of a functionin the same script? Or use your latest testing/benchmarking code to run your old function? Fear not!git-timewarpallows you to temporarily import modules from a specified commit, performing all the git magic under the hood.Here's how you use it. First, import theGitTimeWarpobject. And the (current) version of a function you want to test.fromgit_timewarpimportGitTimeWarpfromtestimporttest_funcLet's see the output of the current functionprint(test_func())new function outputGreat. But what was the output of that function at an earlier commit? By entering aGitTimeWarpobject, we can time travel to discover what it was. All in the same script!withGitTimeWarp("a704acc5f651331645ee5850ff1cda0539cc23df")astw:fromtestimporttest_funcprint(test_func())old function outputZounds! A ghost has appeared!How does this work, you ask? TheGitTimeWarpobject simply checks out the old code in thetimewarps/folder (remember to add to your.gitignore!). It then modifiessys.pathand does some more spicy python magic to ensure all imports in the block will reference the code in this other folder.
Package: gittivity
gittivityMac desktop notifier for git browser activityInstallationMake sure you havepythonandpipinstall in your machine.pip install gittivityQuick StartFor helpgittivityRunnohup gittivity-start <your_github_handle> [<setting>] &example: nohup gittivity-start s1s1ty &Note :setting is optional here, by defaultnwhat is setting?If you want to get only your repo related notifications then putyotherwisenNOTE: you don't get follow event notifications. Because github restricted it.Stop gittivitygittivity-stop** If anyone want to contribute, please send me PR on mydevelopmentbranch.
Package: gitto
gittoAutomate git commits.A minuscle python package to automate:git add .
git commit -m bump
git pushInstallationpip install gittoUsageFrom the command line, in a git repository:gitto -m commit_name -f file1 file2 file3 -pBoth-m(commit message) and-f(committed files) areoptional.
If-mis omitted the commit will be called "bump", if-fis omittedallchanged files will be added to the commit.If-pis omitted, the commit will be staged but not pushed to the upstream branch.The results might look something like:That's it!
Package: git-todo
A small script to manage TODO-entries inside a git repository. A personal
project, with sparse documentation. Trygit-todo--helpto get detailed
information about each command.IntegrationWhengit-todois found via$PATH, git will find it if you rungit todo. This is useful when using it from inside arepl.ExamplesInitializing a new TODO list and edit entries:gittodonewgittodoeditA valid list:x Do dishes.
* Cleanup apartment.
* Achieve world domination.
! Call mum on her birthday.Runninggit todo, which is a shortcut forgit todo list, yields the
following (colorful) results:gittodo! Call mum on her birthday.
* Cleanup apartment.
* Achieve world domination.
x Do dishes.Note that completed tasks (x) have been moved to the end and important
(!) tasks to the front.HeadingsHeadings can be added in a format similar toReStructured Text.Chores
------
x Do dishes.
* Cleanup apartment.
! Call mum on her birthday.

Project X
---------
! Get started.
* Achieve world domination.
x Dream Big.HistoryTODOs are kepy in a regular git branch that contains a single file:gitlog--format=onelinetodo29e941f005de2fa998939b674ed7c4be47a93649 Updated TODO
8330b8167b4393f07ccc0f712301f0630f470a9e Initial commit for TODO branch
Package: gittoolbox
Git ToolboxA library and tools for working with git.Toolsgit-heatmap: Get a heatmap of which source file and which test files are changed together.Contributors GuideTestingTesting is done viapytest.To run the test with code coverage:$ pip install -r requirements.txt
$ pytest --cov=src --cov-report=htmlThis will generate an html coverage report inhtmlcov/directory.
Package: gittrail
gittrail- Linking data pipeline outputs to git historyVersioning of code with git is easy, versioning data pipeline inputs/outputs is hard.GitTrailhelps you to maintain a traceable data lineage by enforcing a
link between data files and the commit history of your processing code.Like blockchain, but easier.How it worksGitTrailis used as a context manager around the code that executes your data processing:withGitTrail(repo="/path/to/my_data_processing_code",data="/path/to/my_data_storage",):# TODO: download the pipeline inputs to [data]Inbetween GitTrail sessions you may edit your pipeline code, make commits etc.When your next data processing stage is ready:withGitTrail(repo="/path/to/my_data_processing_code",data="/path/to/my_data_storage",):# TODO: run data analysis on inputs from [data]# TODO: save results to [data]Upon entering the contextGitTrailattaches a log handler to re-route all logging into a*.logfile in a subdirectory of [data].
When the context exits, the logger is detached and session metadata is stored in a*.jsonfile.
The metadata includes the current git commit of your [repo], as well MD5 hashes of the files inside [data].Within the context, the following two rules are enforced:The working tree of your code [repo] must be clean (no uncommitted changes).All files currently found in [data] must have been created/changed in a previousGitTrailcontext.Taken together this means that:You're not allowed to add/edit/anything in [data] by hand.Your data processing code may continue to evolve as you're moving forward through your pipeline.You can amend/rewind/rewrite git commits of your processing code, but the corresponding files in [data] and the audit trail session file must be deleted.All files in the [data] are linked to the processing code that produced them.LimitationsGitTrailcan't police everything, so keep the following in mind:Data outside of [data], for example a database, is not tracked.
If you're reading/writing data outside of [data] think about how you can trace that in your git history and/or [data] audit trail.Code outside of [repo] is not tracked.
Unless your [repo] specifies exact dependency versions, your code may not be 100 % reproducible.Audit trail files are not cryptographically signed, so if you mess with them that's not tracked.
Package: git-truckfactor
Git-truckfactorGit-truckfactor is a library that assits in the analysis of git repositories. It allows for calculation of Truck Factor scores and code contribution metrics.The tool closely resembles the algorithm proposed byAvelino et al.to estimate the Truck Factor.InstallationGet the latest version by running:pip install git-truckfactorDependenciesGit-truckfactor requires the following python libraries:NumPyNetworkXPlotlyIn addition git-truckfactor makes use of the ruby library Linguist. That means you will also need Ruby installed.LinguistUsageThe git-truckfactor package is intended to be used as a module.Import the module into the python environment:import git_truckfactorClone git repositorycommand:git_truckfactor.clone_repository(<github_repository_url>, <local_repository_path>)example:git_truckfactor.clone_repository('https://github.com/pandas-dev/pandas.git', './github_repos/pandas')returns: local_repository_pathCalculate truckfactorcommand:git_truckfactor.truck_factor_repo(<local_repository_path>, <cur_wd>, <start_date>, <end_date>)example:cur_wd = os.getcwd()
git_truckfactor.truck_factor_repo('./github_repos/pandas', cur_wd, '2020-01-01', '2021-01-01')returns: truckfactor score + creates a directory ‘truckfactor_results’ with truck factor statistics stored in a CSV-fileSee thedemo.ipynbfile for examples on how to use git-truckfactor for multiple repositories.
Package: git-uff
git-uffPrints the forge URL for a given file of a Git repository checkout.IntroHave you ever been discussing with colleagues over IRC/Slack/Matrix/whatever about source code and found yourself needing to point them to a particular file in a git repository?This is tedious to do.One solution is to tell them the path in their checkout, hoping they are on the same branch as you.Another solution is to point your browser to the forge hosting your git repository, select the right branch, navigate the file hierarchy, find your file and copy the file URL.A better (in my opinion 😉) solution is to usegit-uff. This tool adds anuff(short for "URL for file") git sub-command, which takes the path to a file in your repository checkout and prints the matching forge URL.For example to print the URL of thesrc/linux/nanonote.desktopfile from myNanonoteproject:$ git uff src/linux/nanonote.desktop
https://github.com/agateau/nanonote/blob/master/src/linux/nanonote.desktopYou can also point them to a specific line with the-largument:$ git uff src/linux/nanonote.desktop -l 10
https://github.com/agateau/nanonote/blob/master/src/linux/nanonote.desktop#L10git-uffhas a few other available options. Here is its--helpoutput:usage: git-uff [-h] [-b BRANCH] [-p] [-c] [-l LINE] path

Prints the forge URL for a given file or path of a Git repository checkout.

positional arguments:
  path                  File for which we want the URL

optional arguments:
  -h, --help            show this help message and exit
  -b BRANCH, --branch BRANCH
                        Use branch BRANCH instead of the current one
  -p, --permalink       Replace the branch in the URL with the commit it
                        points to
  -c, --copy            Copy the result to the clipboard
  -l LINE, --line LINE  Line to point to

New forges can be declared in git configuration. You can do so using
`git config`, like this:

    git config --global uff.<forge_base_url>.forge <forge>

Where <forge> must be one of: cgit, github, gitlab, sourcehut.

For example to declare that example.com uses GitLab:

    git config --global uff.example.com.forge gitlabWhat if my code is not on GitHub?git-uffis not tied to GitHub. It supports GitLab, SourceHut and CGit forges.To declare a new forge, add it to your git configuration with:git config --global uff.<forge_base_url>.forge <forge>For example to declare that example.com uses GitLab:git config --global uff.example.com.forge gitlabSee the output ofgit uff --helpfor the valid<forge>values.InstallationThe recommended method to installgit-uffis to usepipx:pipx install git-uffBut you can also install it withpip:pip install --user git-uffLicenseApache 2.0
Package: gituhubu
gituhubuCLI tool for speeding up searching repositories in your organization.It fetches your organization repository list and store it in local cache file,
then utilizefuzzy search finderthroughiterfzfto speed up finding specific repository you'll need to clone, preview, or check it's changelog.Installationpip3 install gituhubuConfigurationAt first launchgituhubuwill ask you to create a fileconfig.jsonin specific location for your OS.Example configuration:{"organization":"ORGANIZATION_NAME","token":"API_TOKEN"}You can also use environment variables as a alternative:GITHUB_ORGANIZATION=ORGANIZATION_NAME
GITHUB_TOKEN=API_TOKENWhere ORGANIZATION_NAME is a github organization you want to search and API_TOKEN is a github personal access token with minimum scope ofrepos.More details about creating such token you can find ingithub docs.UsageCLI modegituhubuto invoke search list. Type any part of repository name you'll searching for and hit enter to select it.After selection you will get a short details about repo and possible actions:Repository Name - last update: 2020-09-25T07:51:48Z #TODO fix that date 
Actions: 
- (o)pen in browser
- (c)lone
- view c(h)angelogo- will open given repository in your default browserc- will clone through ssh given repository to current working directoryh- will try to open/CHANGELOG.mdrepository file in your default browserRofi modeFor those usingrofias application launcher, you can use gituhubu as a custom mode.rofi -modi gituhubu:"gituhubu --rofi" -show gituhubuSelecting given repository in rofi mode opens it in your default browser.
Package: gitup
gitup(thegit-repo-updater)gitup is a tool for updating multiple git repositories at once. It is smart
enough to handle several remotes, dirty working directories, diverged local
branches, detached HEADs, and more. It was originally created to manage a large
collection of projects and deal with sporadic internet access.gitup should work on macOS, Linux, and Windows. You should have the latest
version of git and either Python 2.7 or Python 3 installed.InstallationWithpip:pip install gitupWithHomebrew:brew install gitupFrom sourceFirst:git clone git://github.com/earwig/git-repo-updater.git
cd git-repo-updaterThen, to install for everyone:sudo python setup.py installor for just yourself (make sure you have~/.local/binin your PATH):python setup.py install --userFinally, simply delete thegit-repo-updaterdirectory, and you're done!Note:If you are using Windows, you may wish to add a macro so you can
invoke gitup in any directory. Note thatC:\python27\refers to the
directory where Python is installed:DOSKEY gitup=c:\python27\python.exe c:\python27\Scripts\gitup $*UsageThere are two ways to update repos: you can pass them as command arguments,
or save them as "bookmarks".For example:gitup ~/repos/foo ~/repos/bar ~/repos/bazwill automatically pull to thefoo,bar, andbazgit repositories.
Additionally, you can just type:gitup ~/reposto automatically update all git repositories in that directory.To add bookmarks, either of these will work:gitup --add ~/repos/foo ~/repos/bar ~/repos/baz
gitup --add ~/reposThen, to update all of your bookmarks, just run gitup without args:gitupDelete a bookmark:gitup --delete ~/reposView your current bookmarks:gitup --listYou can mix and match bookmarks and command arguments:gitup --add ~/repos/foo ~/repos/bar
gitup ~/repos/baz            # update 'baz' only
gitup                        # update 'foo' and 'bar' only
gitup ~/repos/baz --update   # update all three!Update all git repositories in your current directory:gitup .You can control how deep gitup will look for repositories in a given directory,
if that directory is not a git repo by itself, with the--depth(or-t)
option.--depth 0will disable recursion entirely, meaning the provided paths
must be repos by themselves.--depth 1will descend one level (this is the
old behavior from pre-0.5 gitup).--depth -1will recurse indefinitely,
which is not recommended. The default is--depth 3.By default, gitup will fetch all remotes in a repository. Pass--current-only(or-c) to make it fetch only the remote tracked by the current branch.Also by default, gitup will try to fast-forward all branches that have
upstreams configured. It will always skip branches where this is not possible
(e.g. dirty working directory or a merge/rebase is required). Pass--fetch-only(or-f) to skip this step and only fetch remotes.After fetching, gitup willkeepremote-tracking branches that no longer exist
upstream. Pass--prune(or-p) to delete them, or setfetch.pruneorremote.<name>.prunein your git config to do this by default.For a full list of all command arguments and abbreviations:gitup --help
Package: git-up-all
Git-Up all your projects!Why usegit-up-all?Tired of going into each repo andpulling/rebasing/stashingin order to updateTired of updating all branches over all the repos you have following the above tactics?Need one custom action for sourcetree for eg? Just addgit-up-all--sourcetreeand you are good to goHow it worksReads a json file (or SourceTree list OSX) containing the list of repos you want to keep updated (could also be sourced controlled).Iterates over each folder containing the repos provided and executes git-up as a modulePrints results for each repoNote that it will skip any fails and leaves it up to the user to manually resolve the conflicts.SetupInstall viapip installgit-up-allCreate aprojects.jsoncontaining a list of projects (see example below) or use--sourcetreeRungit-up-allon that folder containing the projects.json or use--sourcetreeprojects.jsonThis file should contain a list with projects/repos as below:{"gitup":{"name":"PyGitUp","git_url":"https://github.com/msiemens/PyGitUp.git","absolute_path":"/Users/jimmykane/projects/pygitup"},"gitupall":{"name":"PyGitUpAll","git_url":"https://github.com/jimmykane/PyGitUpAll.git","absolute_path":"/Users/jimmykane/projects/pygitupall"}}Changelogv0.3.1.1 (2014-08-03)Add results printingSome help is needed with the windows version of the SourceTree config filev0.3.0 (2014-08-01)(BETA) Support for reading from SourceTree on OSX systems for now. Run with--sourcetreeLogic fixesv0.2.0.1 (2014-07-29)This is a pre-release. I will start most of the work in this section after tests are done@TODONeed help to find how to parse windows SourceTree files!!!Check for branchoriginvalidityPatchPyGitUpto use dir paths as arguments let it do the chdir kind or the work is chdir is not neededAdd the tests finallyRethink about structure and integration withPyGitUpAcknowledgementsThanks to the original port of GitUp in python (PyGitUp) by msiemensgit:https://github.com/msiemens/PyGitUp.git
Package: gitupload
gituploaderA Python package to upload a local repository to Github from your Local Machine without
writing  git commands in shellUsage:This package will upload your repository from your local machine to github
by  using github URL of your repository.Package's function push() needs 4 parameters:1.gitrepositoryurl :  URL of new repository created on github2.scriptname :  Name of the script in which this package is being used3.Username : github username4.Email:  github emailUser need to run ascript of this package in a directory from where local Repository are to be uploaded to githubExample:user = GithubUseremail = GithubEmailscriptname = 'setup.py'giturl = 'https://github.com/user/project1'gituploader.push(user, email, scriptname, giturl)Version 1.0.1:This version is compatible with Windows OS onlyNext release will focus on other OSRequirement:Python version>=3.6Git has to be installed in local machine as this package is based on Git
Package: git-upload
I don’t want to care about the type of repositories when pushing a
patch.DescriptionWhen you use thisgit uploadcommand in a repo managed by Gerrit
(supported only OpenStack repos, currently), this command runsgit review. And when you use this command in a repo managed by the
others, this command runsgit push origin $CURRENT_BRANCH(you can
specify the remote repo and branch, of course :).InstallationFrom source$ git clone https://github.com/masayukig/git-upload
$ cd git-upload
$ sudo pip install -e .
or
$ virtualenv ~/venv; source ~/venv/bin/activate; pip install .From PYPI$ pip install git-upload
or
$ virtualenv ~/venv; source ~/venv/bin/activate; pip install git-uploadUsage$ git upload [<remote-repo>] [<branch>]
or you can use varioush options for `git push` or `git review`.
Package: git-upm-publisher
This package is deprecated in favor ofgit-upm-publisher-2.The new package is written in JS. It is much more stable and doesn't have the annoying package resolution bugs of python.git-upm-publisherAutomate UPM package releases for Git repositories containing Unity plugins.Modulesconfig_maker.py: searches forpackage.json files within a repository, and saves the selected one to aconfig.jsonfilepackage_json_creator.py: creates apackage.jsonfile from scratchpackage_json_updater.py: updates an existingpackage.jsonpartially (or completely)upm_publisher.py: automates the whole UPM publishing process explained here:https://www.patreon.com/posts/25070968main.py: runs all the necessary modules in order, so you don't have toInstallationhttps://pypi.org/project/git-upm-publisher/pip install git-upm-publisherUsageRungupin your command line.Advancedgup-mainrunsmain(equaivalent ofgup)gup-config-makerrunsconfig_makergup-package-json-creatorrunspackage_json_creatorgup-package-json-updaterrunspackage_json_updatergup-upm-publisherrunsupm_publisherLicenseMIT license. Refer to theLICENSEfile.
Copyright (c) 2019 S. TarÄ±k Ã‡etinThis application usesgit-snapshot command from mob-sakai.
Take a look and give them some love.