Saravanan666/pypi-org huggingface dataset:
Package: git-pep8-commit-hook
git_pep8_commit_hookGit pre-commit hook for checking coding style of Python code. The hook
requires pep8. It will check files with the.pyextension and files
that contain#!(shebang) andpythonin the first line. Heavily
inspired by and partly based ongit-pylint-commit-hookby Sebastian
Dahlgren.Sincepep8itself, by default, looks for asetup.cfgfile in the
repository root directory, so does this script. The script works without
thesetup.cfgfile. The options for the script can either be placed
in the[pep8_pre_commit_hook]section of the configuration file or
be passed as command line parameters. If the same option is specified in
both the configuration file and the parameters, the configuration file
takes precedence.InstallationInstall via PyPIpip install git_pep8_commit_hookUsageHaving installed the script, if you add it to yourpre-commitfile
which should be placed in thehookssubfolder for the Git folder
(usually.git/hooks), it will be called automatically when you rungit commit. If you want to skip the checks for a certain commit, you
can add the-nflag and rungit commit-n.ConfigurationBy default, the script looks for asetup.cfgin the root directory
of your repository. If the script does not find a configuration file, it
uses default settings. The file might look like this:[pep8]
ignore = E226,E302,E41
max-line-length = 79

[pep8_pre_commit_hook]
max-violations-per-file = 5The[pep8]section is used by pep8. The[pep8_pre_commit_hook]section is used by the commit hook script. You may specify the following
options:pep8-commandis for the actual command, for instance if pep8 is
not installed globally, but is in a virtualenv inside the project
itself.pep8-paramslets you pass custom parameters to pep8max-violations-per-filelets you specify how many violations of
the PEP 0008 standard you are willing to accept for any file. If at
least one file has more than the specified number of violations, the
commit will be blocked. The default value is 0.Alternatively you can pass the above directly to the commit hook script
as arguments. In addition to the above, you can also pass the following
arguments to the script:configlets you specify an alternative config file for both pep8
itself and the commit hook script.versiondisplays the current version of the commit hook script.helpdisplays a help message explaining the arguments.Running testsThe tests are written usingpytest. You can run the tests without
installing pytest and without installing the script by typingpython runtests.py. Alternatively, you can install pytest by runningpip install pytest. The script itself can be installed in
development mode by runningpip install-e.from the root directory
of the repository. Then the tests can be run by executingpy.test.RequirementsThis commit hook is written in Python and has the following
requirements:pep8(sudo pip install pep8)Python >= 2.7Release notes0.1.0 (2015-09-11)Initial release.
Package: git-phoenix
Git PhoenixA dynamic Git Branching ToolGit Phoenix is a Dynamic Branching Tool. We noticed that not all projects can be managed, using the branching models that are largely used by several companies. Many of them, have to adapt the way that they work with Git, just to fit with the branching model chosen.Git Phoenix is exactly the opposite.We made a system that adapts itself with the rules defined by the user or company, instead of the user or company adapt themselves to the system.You can define the branching rules for your Git Repository on a JSON template.
Package: git-pick-from
# About`pick-from` is a text user interface for the Git cherry pick command. Given abranch name on the command line$ pick-from <branch>it will show a list of commits differing between the `HEAD` and the givenbranch:Choose commits to cherry-pick and accept with `q'[ ] 13579ef: A commit message[X] fa45678: Another commit messageCommits can be picked with <kbd>Enter</kbd> and will be passed unconditionallyto `git cherry-pick` command.## InstallationInstall [urwid][] and put the script into your `$PATH`. That's it.[urwid]: http://excess.org/urwid/
Package: gitpkg
gitpkgA git powered package manager built on top of submodules.InstallThe recommended way to install git-pkg is viapipx:$pipxinstallgitpkgUsageThe first thing you need to do to make your project work with git pkg is add a
destination. A destination is a place where your packages will be installed into,
you can have multiple of these.Install a destination by using:$gitpkgdestaddaddonsThe directory does not have to exist, it will be automatically generated.Next we need to install packages lets do so by:$gitpkgaddhttps://github.com/coppolaemilio/dialogicBut wait! While we now have an addons/dialogic directory, the thing we actually
wanted there is now at addons/dialogic/addons/dialogicMany projects, in this case Godot projects have the thing that is important to us
in a subdirectory, to have this subdirectory in the desired location we have
to define it as the package root by:# You can just re-run this it will reconfigurate the package$gitpkgaddhttps://github.com/coppolaemilio/dialogic--package-rootaddons/dialogic# OR: short hand$gitpkgaddhttps://github.com/coppolaemilio/dialogic-raddons/dialogicNice! But what do I do if the repository name and the directory I want is different?Lets look at the next example:$gitpkgaddhttps://github.com/viniciusgerevini/godot-aseprite-wizard.git-raddons/AsepriteWizardWhile this again will add addons/godot-aseprite-wizard we want the directory name to be
AsepriteWizard we can do this by:$gitpkgaddhttps://github.com/viniciusgerevini/godot-aseprite-wizard.git-raddons/AsepriteWizard--nameAsepriteWizard# OR:$gitpkgaddhttps://github.com/viniciusgerevini/godot-aseprite-wizard.git--package-root-with-nameaddons/AsepriteWizard# OR: actual shorthand$gitpkgaddhttps://github.com/viniciusgerevini/godot-aseprite-wizard.git-rnaddons/AsepriteWizardOh no! Now we have addons/godot-aseprite-wizard and addons/AsepriteWizard... why?
Names are essential for identifying projects so this can not be updated, we just have to remove
the unwanted package now:$gitpkgremovegodot-aseprite-wizardNice! Now we can finally get back to work!A few days later...It looks like the packages received some updates! To update all installed packages simply run:$gitpkgupdate# You can also update singular packages by providing their names$gitpkgupdatedialogicAsepriteWizardSince this is powered by git submodules, you have to commit the update.MotivationManaging other git repositories as dependencies is essentially a very good idea
but git submodules are a pain to work with so there came the idea of having a
simpler approach that feels more like using something like npm, composer etc.I mostly wrote this to use this in Godot projects to manage the addons I install
but quickly realized this can be used for a lot of programming languages where
package managers are not an option.This is essentially just an opinionated wrapper around git and git submodules.LicenseGNU General Public License v3
Package: git-play
Git-play is a custom git command for deploying an application server very easily from a remote git repository. It checks the remote git repository every minute and if something has changed, it will restart the application server automatically.InstallationYou can simply install git-play from PyPI by usingpiporeasy_install:$pipinstallgit-playGetting startedGit-play is made for people who hate complicated configurations, thus basically it doesn’t require you to do much except for.git-play.yml.Configuring your git-play deployment with.git-play.ymlGit-play uses the.git-play.ymlfile in the root of your repository to configure how you want your application to be executed..git-play.ymlfile has three parts:app,setup,teardown.For your convenience, there are several examples of.git-play.ymlfile.Djangoapp:workdir:./mysiterespawn:yesexec:python manage.py runserversetup:-pip install -r requirements.txt-cd mysite-python manage.py syncdbteardown:-echo "The server is going down for maintanance..."Expressapp:respawn:yesenv:PORT:80exec:node app.jssetup:-npm installteardown:-echo "The server is going down for maintanance..."Spray and pray!Lastly, all you have to do is simply type the following in your terminal:$gitplayhttp://github.com/foo/bar--remoteorigin--branchmasterSpawned!For an existing repository, type the following:$gitplaybar-rorigin-bmasterSpawned!$ls-Fbar/$cdbar$gitplaySpawned!ContributingJust fork and request pulls. Any help or feedback is appreciated.
Package: git-portfolio
FeaturesConfigure multiple working repositories.Batchgitcommands with subcommands:add,branch,checkout,commit,diff,fetch,init,merge,mv,pull,push,rebase,reset,rm,show,switch,statusandtag.Batch API calls onGitHub: create/close/reopenissues, create/close/reopen/mergepull requestsand deletebranchesby name.BatchPoetrycommands such as:add,version patch,installorupdate.RequirementsCreate an auth token for GitHub, with therepoprivileges enabled by clicking on Generate new token. You will be asked to select scopes for the token. Which scopes you choose will determine what information and actions you will be able to perform against the API. You should be careful with the ones prefixed with write:, delete: and admin: as these might be quite destructive. You can find description of each scope in docs here.Important: safeguard your token (once created you won’t be able to see it again).Installgit(optional) -  this is needed for allgitcommands. For colored outputs please use the configuration:$gitconfig--globalcolor.uialwaysInstallationYou can installGit PortfolioviapipfromPyPI:$pipinstallgit-portfolioBasic usageCreate initial configuration with:$gitpconfiginitExecute all the commands you want. Eg.:$gitpissuescreate# create same issue for all projects$gitpcheckout-bnew-branch# checks out new branch new-branch in all projects$gitppoetryversionminor# bumps minor version of all projects that have pyproject.toml versionNote: by convention GitHub commands are always the resource name and action: eg.branches delete,issues createandprs merge(for pull requests).
This avoid conflicts with batch git commands, as ingitp branch(executes git command) andgitp branches delete(execute operations using GitHub API).Complete instructions can be found atgit-portfolio.readthedocs.io.ContributingContributions are very welcome.
To learn more, see theContributor Guide.LicenseDistributed under the terms of theMITlicense,Git Portfoliois free and open source software.IssuesIf you encounter any problems,
pleasefile an issuealong with a detailed description.CreditsThis project was generated from@cjolowicz’sHypermodern Python Cookiecuttertemplate.
Package: git-pr
A git command for fetching GitHub’s pull requests to local copy.$[sudo]pipinstallgit-prUsagehttps://github.com/ikalnytskyi/git-pr/pull/42$gitpr42$gitprgithub42$gitpr42--branchpr/42$gitprhttps://github.com/ikalnytskyi/git-pr.git42LinksDocumentation:https://git-pr.readthedocs.org/Source:https://github.com/ikalnytskyi/git-prBugs:https://github.com/ikalnytskyi/git-pr/issues
Package: git-pr-branch
GIT PR branchgit-pr-branchis a command line tool designed to manage the relationship between branches and
pull-requests.At the moment it only supports Github and Pagure, but other backends are possible.You need to create a personal token inyour Github settings
pageif you plan to use Github (Pagure can work without a
token). When you start the program for the first time, it will ask you for it and store it in a
configuration file.Downloading pull requestsgit pr-branch pull 42will download pull request #42 in a local branch, creating a new branch each
time the command is run. Why, you ask? Because it is common for PR authors to amend their commits
after a review instead of adding more commits, and as a reviewer it's hard to see the differences
between the code you reviewed and the new code. By creating a new branch each time, you can just
diff with the previous branch.If you have not checked out this PR before, it will create a branch for every existing review in the
PR's history. This way it'll be easy to see what's changed between earlier reviews even if you did
not run the command at that time (this behavior is not supported on Pagure).When you're working on the PR branch, runninggit pr-branch updateorgit pr-branch upwill
download the latest version of the PR in a new branch and switch to it. It is a shortcut to running
the same command, so you don't have to remember and type in the PR number again.Displaying branches and pull requestsgit pr-branch showwill list all your local branches and show you whether they are associated with
a pull request, whether that PR is still open or not, and the URL for that PR.Purging branchesgit pr-branch purgewill delete the branches that are linked to a closed pull request (or multiple
pull requests that are all closed). This will let you keep your local repo tidy.OptionsIf the remote name for the repository you're forking from (here called "upstream") is not named
"origin", you can set which remote is your upstream with the-uor--upstreamoption. Here is an
example: if Bob wants to fork Alice's repository he may clone his own fork first and then add
Alice's repository as a remote:$ git clone git@github.com:/bob/repo
$ git remote add upstream git@github.com:/alice/repoThe original repository is therefore not in the defaultoriginremote but in theupstreamremote.
In this configuration,git-pr-branchmust be used with the-uoption as such:$ git pr-branch -u upstream showThe value will be set in the local repository's configuration and you won't need to use the option
in the future.If most of your local repositories don't use the remoteoriginas upstream, you can configure a
different default value in the configuration file. The first-time setup "wizard" will ask you.
Package: git-pre-push-hook
Pre push hook running linters.Free software: BSD licenseInstallationpip install git-pre-push-hookInstall hook to current Git-repository:install-git-pre-push-hookDefault pre-push hook:python -c "import pre_push_hook; sys.exit(pre_push_hook.hook.main())"ConfigurationYou can pass configuration parameters to script by setting proper environement variables in./.git/hooks/pre-pushCustom Pyflakes configuration fileLINTER_FLAKE_CONFIG="./setup.cfg" python ...Warnings only for changed linesCHANGED_LINES_ONLY=1 python ...TroubleshootingIn OSX not prompt question is displayed and after pressing any key EOFError is raised:Maybe you are not using system Python. E.g. MacPorts have problem with using stdin (
see:http://superuser.com/questions/965133/python2-7-from-macports-stdin-issue).
Try using system Python (System/Library/Frameworks/Python.framework/Versions/Current/bin/python)DevelopmentTo run the all tests run:toxChangelog0.1.0 (2016-01-06)First release on PyPI.
Package: git-pretty
An implementation of Justin Hileman’s handy chart fromhttp://justinhileman.info/article/git-pretty/Git Pretty ChartInstallpipinstallgit-prettyUseJust rungit-prettyThis opens an interactive session like this:Soyouhaveamessonyourhands.Whatsortofmess?1:Anuncommittedmess2:Iaccidentallycommittedsomething3:MyGithistoryisugly>
Package: git-processor
A git log processor for better stats.View the demogit processor demo.SetupInstall the library with:# From pypipython3-mpipinstallgit_processorTo use it, run thegenerate_git_logs.shin where you have all your repository.
It will create astats.txtfile.importosfromgit_processor.dataimportProjectsp=Projects(os.path.abspath("stats.txt"))# Process the git log statsp.clean_up_names()# Get all similar names as onep.df# Get the created dataframep.total()# Total commits per userLet’s use jupyter to display the information.pyhton3-mpipinstalljupytercdjupyter/jupyternotebookOnce you are in the jupyter notebook, you can display the data and plot the stats.
Check in thejupyter/folder, you can reuse the demo and get your stats in one go.
Just click onRun All Cell, or go along with <kbd>shift</kbd> + <kbd>enter</kbd> to run them individually.TestingTo find out more info about the testing configuration, check out thetox.inifile.# Run the test suitetox# Run the linter:tox-elintLocal InstallationUsing a virtual environment:# From pypipython3-mpipinstallvirtualenvThen set it up and install the package locally# Create the virtual environmentpython3-mvenv`pwd`/env# Activate itsourceenv/bin/activate# Install from local(env)python3-mpipinstall.
Package: gitprof
GitProfIntroductionGitProf ("Git Profiles") is a tool which simplifies working with multiple Git accounts/services.GitProf helps you with:Using different Git services (e.g. GitHub and GitLab).Using multiple accounts on GitHub (e.g. personal and work accounts).It solves the problems which you may experience when using multiple accounts/services:You can't clone a repository easily because your default SSH key is for a different account.Once you clone the repository, local Git config values such asuser.emailneed to be set correctly.GitProf doesn't change your Git workflow; after usinggitprof cloneorgitprof profile applyon a repository, you don't need to interact withgitprofagain for that repository.InstallationRequirements:Python 3.7 or higher, with thepippackage manager (which is usually installed by default).Windows, Linux or macOS.When installed withpip, thegitprofexecutable is automatically added to thePATHand behaves as a standalone program.To install GitProf withpip, run the command:pipinstallgitprofNow you can rungitprof versionto check that it is installed and available on thePATH.Quick StartGitProf storesprofileswhich contain the information required to configure repositories for different accounts. When you run a command which uses a profile, you will be prompted to choose an existing profile or create a new one.Cloning a new repositoryTo clone a repository, just usegitprof cloneinstead ofgit clone. For example:>>gitprofclonegit@gitlab.com/some-profile/some-repo.git### Choose a profile to clone with ###[0]github(GitHub)[2]gitlab(GitLab)[3]<CREATENEWPROFILE>
Enteranumberfromthelisttochooseanoption[default=0]:1Cloning'git@gitlab.com/some-profile/some-repo.git'withprofile:gitlab

SettinglocalGitconfigvaluesfor'some-repo'...
SettingyourGitnameto'MyUsername'...
SettingyourGitemailto'MyGitEmail'...
SettingyourGitSSHcommandto'ssh -i ~/.ssh/my_ssh_key'...
FinishedsettingupyourGitrepository.Applying a profile to an existing repositoryIf you have an existing repository whose config values you wish to change, you cancdinto the repository and usegitprof profile apply. For example:>>cdsome-repo
>>gitprofprofileapply### Choose a profile to apply ###[0]github(GitHub)[2]gitlab(GitLab)[3]<CREATENEWPROFILE>
Enteranumberfromthelisttochooseanoption[default=0]:1SettinglocalGitconfigvaluesfor'some-repo'...
SettingyourGitnameto'MyUsername'...
SettingyourGitemailto'MyGitEmail'...
SettingyourGitSSHcommandto'ssh -i ~/.ssh/my_ssh_key'...Tip: GitProf includes help info, even for subcommands. For example, you can usegitprof profile --helpto see parameters for theprofilesubcommand.Developer NotesPackaging the projectrm-rdist/
python-mpipinstall-rrequirements-dev.txt-rrequirements.txt
pythonsetup.pysdist
pythonsetup.pybdist_wheel
twineuploaddist/*
Package: gitprofile
GitHub:github.com/euanacampbell/gitprofilePyPi:pypi.org/project/gitprofileInstallationpipinstallgitprofileImportfromgitprofile.githubimportprofileSetupfromgitprofile.githubimportprofilegithub_user_name='euanacampbell'user_profile=profile(github_user_name)Repositoriesfromgitprofile.githubimportprofilegithub_user_name='euanacampbell'user_profile=profile(github_user_name)forrepoinuser_profile:print(repo.title)# github-public# octopus_energy_api# boggle_solver# System-Monitoring# Pathfinding-Algorithm# pegasus# euanacampbell.github.io# sqlite-editor# reddit-clientAccessible detailsfromgitprofile.githubimportprofilegithub_user_name='euanacampbell'user_profile=profile(github_user_name)first_repo=user_profile.repositories[0]# titlefirst_repo.title#gitprofile# urlfirst_repo.url#https://github.com/euanacampbell/gitprofile# descriptionfirst_repo.description#Extract public repository data.
Package: git-profile
git-profileThis command-line tool allows you to define a set of configuration profiles that can be applied on
a per-repository basis. The main use case is to swap the user details and signing key, but it's
not limited to just that.InstallationWe recommend installing the tool with Pipx.$ pipx install git-profileConfigurationIn~/.gitconfig, prefixing section names with<Profile>.assigns them to the specified profile.
Git-profile can use that information to determine which profiles there are and what configuration
is associated with it.Example:[Work.user]email="me@work.com"signingkey=DEADBEEFDEADBEEFUsageRungit profileto list available profiles. The current profile will be marked with a star. Note
that thedefaultprofile is always present and represents your normal Git configuration without
profile overrides.$ git profile
* default
  WorkWithgit profile <Profile>you can switch to the specified profile.$ git profile Work
Switched to profile "Work".The changes will be applied to.git/configof the current repository.You can add the--diffoption to print a diff of the applied config changes.FAQHow do I avoid accidentally forgetting to switch my profile after checking out a repository?You can leave the[user]section of your default configuration empty. That way Git will prompt
you to configure it when trying to commit. Simply rungit profile <Profile>after that and
commit again.Vendored Librariesgitconfigparser.pyby looking-for-a-job @ GitHubCopyright © 2012 Niklas Rosenstein
Package: git-profile-manager
Git Profile ManagerA git extension to allow you manage multiple git profiles on your workstation. User profiles can have independent configurations. They can also share configurations.Installationusing PipGit-profile-manager can be installed using the pythonpiptool.pip3installgit-profile-manager# pip install git-profile-manager## Upgradepip3installgit-profile-manager--upgradeNOTE: After installation, your current git config will be used as a shared configuration. All users inherit from the configurationUsageCreate ProfileTo create a profilegitcreate-profilegitcreate-profile-efoo@bar.com-n"Foo Bar"To Configure profile:# Sets up ssh for that usergitconfig--globalcore.sshCommand"ssh -i /full/path/to/id_a/id_rsa"NOTE: Git Profile Manager stores the user config as global config. Hence all configurations must carry the--globalflag. That means running config without the--globalflag creates a local config that overrides values set on user config# Sets up ssh for that user# Set config for present repository# This Config overrides the user profile created config value for core.sshCommandgitconfigcore.sshCommand"ssh -i /full/path/to/id_a/id_rsa"All initial global configurations are added to the user config. For conflicts, the user's config override the global config.Global ConfigurationTo add configurations that would be shared by all users:gitglobal-configcore.sshCommand"ssh -i /full/path/to/id_rsa"User's configuration always override global configurationApply profileApplies a profile to a particular directory. Once applied, any repository within the directory uses the config.# Applies current user profilegitapply-profile/home/user/company# Applies specified user profilegitapply-profile/home/user/personal-upersonalimplemented usinghttps://git-scm.com/docs/git-config#_conditional_includesSwitch between ProfilesTo Switch Profile:gituse-profilefoo@bar.comRemove Existing ProfileTo Remove an existing Profile:gitremove-profilefoo@bar.comCurrent ProfileTo get the Current Profile:gitcurrent-profileList ProfilesTo list the Current Profile:gitlist-profilesTODOAdd bash completionsCheck and add windows compatibilityTests