Saravanan666/pypi-org huggingface dataset:
Package: git-submodule-updater
# git-submodule-updaterA tool to automate making GitHub Pull Requests about updating
git submodules.You should be able to just give it the name of a repo (e.g.mozilla/kuma)
and it finds out which submodules there are and looks to see if they can be
updated.## DemoNot really a demo but [this pull request](https://github.com/mdn/stumptown-renderer/pull/62)
was entirely made from this script.## Limitations and caveatsAt the time of writing,this is a prototype. It’s doing the least possible
to make the most basic thing work.It requires that you’re allowed to push branches to the origin.It only really works with GitHub.comIt’s doing thegitclone with SSH. So not sure how to make this work in
a server.It’s only a CLI at the moment.There’s no good way to auto-close now out-of-date older PRsNo unit testsNot tested beyond the defaults ofmasterandoriginIt can only make 1 PR per the difference between the head and the submodule.To see what the difference in a submodule update you have to rely on GitHub’s
“Files changed” tab on the PR.## Getting startedYou’ll need a GitHub access token.
Go to [github.com/settings/tokens](https://github.com/settings/tokens) and create a token,
copy and paste it into your.envfile or useexport. E.g.cat .env
GITHUB_ACCESS_TOKEN=a36f6736…pip install git-submodule-updater
gsmu github.com/mdn/stumptown-renderer  # for exampleIf you don’t use a.envfile you can use:GITHUB_ACCESS_TOKEN=a36f6736… gsmu myorg/myrepo## GoalThis tool should be possible to run as a CLI and as a web server
so it can be connected to a GitHub repo Webhook.## ContributingClone this repo then run:pip install -e “.[dev]”That should have installed the CLIgsmugsmu –helpIf you wanna make a PR, make sure it’s formatted withblackand passesflake8.
Package: gitsubrepo
Git Subrepo Python WrapperIn the same way that`GitPython<https://pypi.python.org/pypi/GitPython/>`__ wrapsgit, this library provides easy access togit
subrepoin Python.How to usePrerequisitesgit >= 2.10.0 (on path)git-subrepo >= 0.3.1python >= 3.6InstallationStable releases can be installed viaPyPI:$pipinstallgitsubrepoBleeding edge versions can be installed directly from GitHub:$pipinstallgit+https://github.com/wtsi-hgi/python-git-subrepo.git@${commitIdBranchOrTag}#egg=gitsubrepoTo declare this library as a dependency of your project, add it to yourrequirement.txtfile.APIThe library currently supports 3git subrepooperations:clone,pullandstatus. Please see the documentation for specific
information on how to use these methods.Example usage:importgitsubreporemote_repository="https://github.com/colin-nolan/test-repository.git"repository_location="/tmp/repo"subrepo_location=f"{repository_location}/subrepo"branch="develop"commit_reference=gitsubrepo.clone(remote_repository,subrepo_location,branch=branch)updated_commit_reference=gitsubrepo.pull(subrepo_location)subrepo_remote,subrepo_branch,subrepo_commit=gitsubrepo.status(subrepo_location)assertsubrepo_remote==remote_repositoryassertsubrepo_branch==branchDevelopmentSetupInstall both library dependencies and the dependencies needed for
testing:$pipinstall-q-rrequirements.txt$pipinstall-q-rtest_requirements.txtTestingTo run the tests and generate a coverage report with unittest:./test-runner.shIf you wish to run the tests inside a Docker container, buildDocker.test.LicenseMIT license.Copyright (c) 2017 Genome Research Limited
Package: git-subrepo
Git subrepo python packageProvides easy deployment forgit subrepo.
Read thechangesfor current release.How to usePrerequisitesgit >= 2.10.0 [set in PATH variable]python >= 3.6InstallationStable releases can be installed viaPyPI:$pipinstallgit-subrepoUsageRun the subrepo command to see usagesubrepo<command><argument><options>You can show help for any commandsubrepohelpstatusshell supportIf you need to use subrepo asgit subrepocommand use the init scriptsBash$sourcegit-subrepo-init.sh
$gitsubrepoversionCmd>git-subrepo-init.bat
>gitsubrepoversionPowerShellPS>.\git-subrepo-init.ps1
PS>gitsubrepoversionLicenseMIT license.
Package: git-substatus
git-substatusA command-line tool to inspect the status of git repositories from a directory,
e.g., a projects folder keeping all of your git projects. You can inspect:statusadded, removed, modified, renamedmerge conflictsetc.stashworktreeUsageSee atgit-substatus --help:usage: git-substatus [-h] [-v] [--include-hidden] [--fetch] [path]

See subdirectories' git status
==============================

The output consists of four columns:

repo name | branch head | status | git stashes (if any)

The string (*WT) seen next to the repo names shows that the
repo has some git worktrees. See more:
<https://git-scm.com/docs/git-worktree>

positional arguments:
  path              a path to where you want to see git substatuses. If empty, the
                    current working directory is selected.

options:
  -h, --help        show this help message and exit
  -v, --version     show program's version number and exit
  --include-hidden  repositories starting with a dot (.) are included.
  --fetch           perform git fetch from remote on all sub repositories.InstallationInstall from thePyPI:pipinstallgit-substatusInstall from the repo:pipinstallgit+https://github.com/strboul/git-substatus.gitAlternatively, theDockerimage can be used:dockerrun--rm-t-v"$(pwd)":/"$(pwd)"-w"$(pwd)"strboul/git-substatus:latestTo shorten the command, it's also possible to add an alias in the.bashrcor.zshrc, e.g.:_git_substatus(){dockerrun--rm-t-v"$(pwd)":/"$(pwd)"-w"$(pwd)"strboul/git-substatus:latest"$@"}aliasgit-substatus="_git_substatus"Benchmark: it's measured that the container solution is ~70% slower than the
native operation due to the overhead; however, the container solution is still
useful for portability matters.DevelopmentThis tool hasno module dependencyoutsideThe Python Standard Library.Development docsVersioning and releaseBump up the__version__ingit_substatus/__init__.pyand commit the
change in the batch where you changed the files.(For the codeowners) This step is only onmaster. Create a version tag
withmake tag-createtarget. Push the tag to the origin withmake tag-push. Upon the push, the release CI workflow will be triggered that
will distribute the new version to the platforms, such asPyPI,DockerHub.pre-commitRun pre-commit git hooks on every commit that run checks against the files
added to a commit.Upon cloning the repo, set uppre-commit:Install pre-commithttps://pre-commit.com/#installationRunpre-commit installthat installs the hook scripts at.git/hooksAdd testsWrite/update unit tests (if relevant). You can start by adding/modifying a
case to generator file ofscripts/generate_test_repos.sh.Run tests && debuggingvirtualenvvenvsourcevenv/bin/activate# deactivatepipinstall-rdev-requirements.txt# pip freeze > dev-requirements.txtmakePut abreakpoint()at a relevant place and run:maketestAdd new methodsUse the reference to name the functions/methods in the module:https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitglossary.html
Package: git-sumi
Documentation|Websitegit-sumiThe non-opinionated Rust-based commit message linterTransform your commit practices with flexible linting for consistently high-quality Git commit messages that adhere to your project's standards.sumi (墨, /sɯmi/): ink, especially the type used intraditional ink wash painting.🎥 DemoSee how git-sumican help you write better commit messages:https://github.com/welpo/git-sumi/assets/6399341/1e21f237-0122-47e5-b79b-6972a0b9e23f✨ Main featuresCustomizable rules: Tailor git-sumito each project's specific requirements. Easily configurerulesto enforceConventional Commits, length limits, gitmoji usage, and more through asimple TOML file.Clear error reporting: git-sumi's detailed error reporting makes fixing commit messages straightforward and educational.Seamless integration: git-sumiis asingle binary, making it easy tointegrate into your existing workflowwith minimal setup.📝 DocumentationLearn how to use git-sumifrom thedocumentation.Quick setupConfigurationRulesExamplesIntegrationFrequently Asked Questions👥 ContributingPlease do! Contributions are always welcome. We appreciate improvements to the documentation, development of new rules, code cleanup, resolving issues, requesting or developing new functionality…Take a look at ourContributing Guidelinesfor more information on how to get started.📄 LicenseThis project is licensed under the terms of both theMIT licenseand theApache License (Version 2.0), at your option.
Package: gitsummary
gitsummaryPure python utility to print a one-line summary of the current git repository, the current branch, and the hash for the current head.Installationpipinstallgitsummaryorconda-cconda-forgeinstallgitsummaryUsage>>>importgitsummary>>>gitsummary.print_cwd_git_version()'some_git_repository:On branch main at rev cd813e5'returns a string containing the current git repository, the current branch, and the hash of the branch head.  This information is useful in scientific codes to quickly determine the origin of a plot or dataset.  The string can, for example, be written in ajupyter notebookor placed in the metadata of anetcdffile.some_git_repositoryis reported as final portion of the URL of the remote 'origin'.  If there is no remote named origin, it uses the full path on disk to the .git directory.LicenseThis project is licensed under the terms of the MIT license.CreditsAdapted byTimothy W. Hiltonfrom code originally written byTravis O'Brien.
Package: gitsummary-Timothy-W-Hilton
gitsummaryPure python utility to print a one-line summary of the current git repository, the current branch, and the hash for the current head.usageimportgitsummarygitsummary.print_cwd_git_version()returns a string containing the current git repository, the current branch, and the hash of the branch head.  This information is useful in scientific codes to quickly determine the origin of a plot or dataset.  The string can, for example, be written in ajupyter notebookor placed in the metadata of anetcdffile.LicenseThis project is licensed under the terms of the MIT license.
Package: git-svn-clone-externals
Usagegit-svn-clone-externalssvn-working-copydest-dirThe main difference between this and other alternative scripts is that
this one starts from an svn checkout to discover the externals, so it’s
faster.The package comes with some utility command to manage a nestedgit-svnclone:git-svn-dcommitandgit-svn-rebase: asgit svn <command>but with automaticstash saveandstash popgit-svn-outgoing: shows a diff of dcommit’able commitsAll scripts are offering a--recursiveoption.InstallationThe scritps depends ongit svn, in Ubuntu you can get the package
with:$ sudoapt-getinstallgit-svnand than install the script with:$ pip installgit-svn-clone-externalsLicenseThis script is released under theMIT
LicenseTODOgit-ignore externalstest on convoluted externals (relative paths)manage fixed revision externals
Package: git-sweep3k
A command-line tool that helps you clean up Git branches that have been merged
into master.This is a fork that adds Python 3 support (in addition to Python 2). The
original is athttps://github.com/arc90/git-sweep.The problemYourmasterbranch is typically where all your code lands. All features
branches are meant to be short-lived and merged intomasteronce they are
completed.As time marches on, you can build upa long list of branches that are no
longer needed. They’ve been merged intomaster, what do we do with them
now?The answerUsinggit-sweepyou cansafely remove remote branches that have been
merged into master.To install it run:$ pip install git-sweep3kTry it for yourself (safely)To see a list of branches that git-sweep detects are merged into your master
branch:The--dry-runoption doesn’t make any changes to your repository:$ git sweep --dry-run
Fetching from the remote
These branches have been merged into master:

  branch1
  branch2
  branch3
  branch4
  branch5

To delete them, run again without --dry-runIf you are happy with the list, you can run the command that deletes these
branches from the remote:$ git sweep
Fetching from the remote
These branches have been merged into master:

  branch1
  branch2
  branch3
  branch4
  branch5

Delete these branches? (y/n) y
  deleting branch1 (done)
  deleting branch2 (done)
  deleting branch3 (done)
  deleting branch4 (done)
  deleting branch5 (done)

All done!

Tell everyone to run `git fetch --prune` to sync with this remote.
(you don't have to, yours is synced)Note: this can take a little time, it’s talking over the tubes to the remote.You can also give it a different name for your remote and master branches:$ git sweep --dry-run --master=develop --origin=github
...Tell it to skip thegit fetchthat it does by default:$ git sweep --dry-run --no-fetch
These branches have been merged into master:

  branch1

To delete them, run again without --dry-runMake it skip certain branches:$ git sweep --dry-run --skip=develop
Fetching from the remote
These branches have been merged into master:

  important-upgrade
  upgrade-libs

To delete them, run again without --dry-runOnce git-sweep finds the branches, you’ll be asked to confirm that you wish to
delete them:Delete these branches? (y/n)You can use the--forceoption to bypass this and start deleting
immediately:$ git sweep --skip=develop --force
Fetching from the remote
These branches have been merged into master:

  important-upgrade
  upgrade-libs

  deleting important-upgrade (done)
  deleting upgrade-libs (done)

All done!

Tell everyone to run `git fetch --prune` to sync with this remote.
(you don't have to, yours is synced)RequirementsGit >= 1.7Python >= 2.6 or >= 3.2LicenseFriendly neighborhood MIT license.
Package: gitsy
Gitsy - Git made easy!NOTICE: gitsy is still very much under construction, I'll notify when a standard beta version is ready.Gitsy is a supplementary CLI to git for a better git flow and git experience.I started it to enhance my git productivity and answer 4 main use cases:Fast commits - a combination of git's add, commit and push.Undo changes - easily undo all changes made to a file, whether it was staged or unstaged.Easy branch hopping - move between branches, even if you have unstaged changes, without having to stage them.Simplify git ignore resetting - that annoying thing where you accidentally pushed something you wanted ignored.Other then that I've added some interactiveness to the git flow - selectors, checkboxes, prompts, etc.InstallationUse the package managerpipto install foobar.pipinstallgitsyUsagegitsy can be used in a globaly with no context (out-of-the-box) or in a branch context.No context:# git add .# git commit -m "commit message"# git push# IS NOW:gitsyup"commit message"# Notes:# - Commit message is optional (defaulted to 'fast commit').# - Auto handles the case of setting remote origin for new branches.# To undo changes in an unstaged changed file:gitsyundofile_1.py# To pick a file just drop the file's name:gitsyundo# for staged files use:gitsyregret# ...Branch context:TBDBuilt withgoogle-firegitpythoninquireremojiContributingPull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.Please make sure to update tests as appropriate.Local dev environmentTBDLicenseMIT
Package: git-sync
Thegit_syncmodule.Githubhttps://github.com/Erotemic/git_syncPypihttps://pypi.org/project/git_syncThis is a very simple git script to help with local development and remote
execution. It turns the process of commiting, logging into the remote machine,
and then pulling on the remote machine into a single command.Assuming that you have the same file structure on both your local and remote
machine,git-syncallows you to edit files locally, and when you want those
changes reflected on the remote machine, you executegit-sync other-machineNote, thatthis creates a commitwith the message “wip” and pushes it to
the default git-remote. The commit message and target git-remote can be
modified by command line args.InstallationInstalling the git_sync Python module also installs thegit-synccommand line utility.pip install git-syncDetailsExecutinggit-syncperforms the following actions:Executes a git commit to the local repo (the default commit message is “wip”,
but this can be changed using the -m flag).Executes agit push originwhich pushes the local copy of the repo to the
git server. (Note, git-sync defaults to the origin git remote, but you can
specify a different one using a second positional argument: e.g.git-syncother-machineremote2).Creates an SSH connection to “other-machine”, cd’s into the same directory
you are in on the local machine (which is why mirroring the directory
structure across development machines is important), and then executes agit pull origin, which will update the remote machine to the newly pushed
state.CaveatsNote that this script is very simple, it will fail if these conditions aren’t met.The location of the repo (relative to the home directory) must be the same on
the local and remote machine. Note, it is fairly easy to ensure this is the
case using symlinks.The repo on the local machine and remote machine must be on the same branch.The repo on the remote machine must be in a clean state.On SSH ConfigsAlso, to make life easier, it is best that you have a $HOME/.ssh/config file
setup with the remote machines you to access and appropriate identify files so
you don’t need to enter your password each time yougit-sync.An example ssh config entry is:Host {myremote} {myremote.com}
    HostName {myremote.com}
    Port 22
    User {username}
    identityfile ~/.ssh/{my_id_ed25519}Replacing any entry in{curly braces}with an appropriate value.If you don’t have an ssh identify file, create one using:mkdir -p $HOME/.ssh
cd $HOME/.ssh

FPATH="$HOME/.ssh/my_id_ed25519"
ssh-keygen -t ed25519 -b 256 -C "${EMAIL}" -f $FPATH -N ""

chmod 700 ~/.ssh
chmod 400 ~/.ssh/id_*
chmod 644 ~/.ssh/id_*.pubAnd ensure the public key is registered with the remote machine:REMOTE={myremote.com}
REMOTE_USER={myusername}
ssh-copy-id $REMOTE_USER@$REMOTESimilar SoftwareCFarmis a tool for keeping remotes in sync and testing code on the remote machines.Visual Studio Codehas great remote ssh and developing support.
Package: git-sync-upstream
git-sync-upstream is a CLI to sync gitupstreamremote branches and tags with
the local clone andoriginremote.Installationgit-sync-upstream is distributed onPyPI. It requires Python 3.7+. To
install:$python-mpipinstallgit-sync-upstreamUsageChange directory to the git project to sync. The project must have a remote
namedupstreamandorigin. The remoteupstreamwill be used to sync
_from_. Its branches and tags will be synced locally and _to_origin.$cdmyproject#Tosyncthecurrentbranch$git-sync-upstream#Tosyncallbranches$git-sync-upstream--allIt is convenient to add a git alias to the command:$gitconfig--globalalias.sync"!git-sync-upstream"Then:$cdmyproject#Tosyncthecurrentbranch$gitsync#Tosyncallbranches$gitsync--all
Package: git-tagup
git-tagupFind and tag Git commits based on version numbers in commit messages.If you're like me, you often add the version number for a commit into the commit message itself, something like:$gitcommit-m"Bump version to 2.1.5"If you're still like me you probably forget to create a tag for the new version and push
it to the remote repository. I end up having projects that have many un-tagged commits
from months or years ago that never get real tags.I createdgit-tagupto conveniently search through the active branch in a Git repository
and find un-tagged commits containing version numbers in the commit message. For each one
it finds, the tool asks the user whether they want to create a tag for it.Currently onlySemVerversioning format is supported, but I'm happy
to take requests for other formats.Happy tagging!RequirementsPython 3.6 or greaterPip (Package manager for Python)QuickstartInstallgit-tagup:$pipinstallgit-tagupBrowse to the Git repository you want to add tags to - this is usually your project root directory containing the.gitdirectory:$cdpath/to/project/rootRun the program:$git-tagupIf version numbers are found in the commit messages, answer the prompts with ayto create the tag ornto skip it.Don't forget to push the new tags to your remote when done!$gitpush--followtagsExample$cdpath/to/project/root$git-tagupCreate the tag 'v0.1.1' for commit message 'Bump version to 0.1.1'? (y/n/q): nCreate the tag 'v0.1.2' for commit message 'Bump version to 0.1.2'? (y/n/q): yCreate the tag 'v0.1.3' for commit message 'Bump version to 0.1.3'? (y/n/q): qInstallation$pipinstallgit-tagupLearn MoreLearn more about this project on thegit-tagup project page.AuthorsJacob Stopak- on behalf ofInitial Commit
Package: gittalk
gittalk=======Imagine you are working on a hack, and you just pushed some code.Instead of yelling to your teammates and letting them aware of thechanges, wouldn't it be cool to have the computer say it out loudfor you?## Installation`pip install gittalk``python setup.py install` should also be just fine, in case you don'thave Pip installed.## Dependencies* `pyttsx`: https://pypi.python.org/pypi/pyttsxThe file `requirements.txt` contains all other dependencies I've usedwhile working on `gittalk`, though most of them are not needed inrunning this program.Pyttsx will also install its own dependencies.## Doesn't work?Most likely, the installation for pyttsx failed. Check outhttps://github.com/parente/pyttsx and see if any previously raisedissues there are helpful. Unfortunately, I've only tested this onUbuntu 12.10 32-bit, so it might not work as expected on Windows/OSX...## Features and Usage* Make a git commit as usual. Then type `gittalk` on the terminal. Thelast commit message should be said out loud. :D* ... More to come! (see `say_last_push` in `gittalk/core.py` for example)## NotesThis is still pretty basic, and is mostly my attempt at playing withdifferent TTS (text-to-speech) packages in Python, as well as learninghow to structure a proper Python package and share it via Pip.That said, I do plan to extend it further and make this even more funand useful. Please send me a pull request if you would like tocontribute. Suggestions/criticism/advice are all welcome!
Package: git-tessera
# tesseraThe most simple git based ticketing system.We believe that:Issues belong to the code. Point.A powerful system can be build with minimum effortSimplicity is the solution to our complex environment.If you want toget rid of loosing your tickets because of changing the issue management systemlet your issues flow with your branches and patcheshave documented your issues with your codehave a real unique and persistent issue ida shaXX save documented issue system… take a look at tessera.License:GPLVersion:0.00.01## Installation`bash git clonehttps://github.com/neolynx/git-tessera.gittessera cd tessera python setup.py install `## Usage`bash cd my_favorite_git_project git tessera init git tessera create my first ticket git tessera ls git tessera edit<tessera-id>`## DevelopmentWe recommend you to develop git-tessera inside a virtualenv, since the dependencies can be managed much easier and no unwanted packages installed somewhere on the system are involved.` virtualenvtessera-env--no-site-packages`Note: the `–no-site-packages` option is only used for older versions of virtualenv. In newer versions it’s default anyway but it is not a problem to use this option at all!Activate the virtualenv with:` .tessera-env/bin/activate`and deactivate it with:` deactivate `Now you can install all dependencies with therequirements.txtfile:` pip install-rrequirements.txt `After this command you can see the control with thepip freezecommand` $ pip freezeargparse==1.2.1colorful==0.01.02dulwich==0.9.4funky==0.0.2git-tessera==0.00.01gittle==0.2.2mimer==0.0.1paramiko==1.10.0pycrypto==2.6web.py==0.37wsgiref==0.1.2`Installgit-tesserawith the setup.py script inside the virtualenv:` python setup.py install `If you installgit-tesserawithout installing the dependencies from therequirements.txtfile the needed packages will be installed with the setup.py script!