Saravanan666/pypi-org huggingface dataset:
Package: git-upstream
What is git-upstream?git-upstream is an open source Python application that can be used to keep in
sync with upstream open source projects, mainly OpenStack.The main usecase for this tool is for people who are doing active contributions
to repositories that are mirrors of OpenStack repositories, with the intention
that most of those contributions will be submitted to review.openstack.org at
some point.
If you are running a public cloud based on OpenStack, having local changes
needed to use it in your environment, you can use git-upstream to stay up to
date with the upstream master in a easier way (with respect to using raw git
commands).git-upstream provides new git subcommands to support rebasing of local-carried
patches on top of upstream repositories. It provides commands to ease the use
of git for who needs to integrate big upstream projects in their environment.
The operations are performed using Git commands.See also README.md, and USAGE.md files.What git-upstream is notThe name of this tool includes the “git-” prefix because of the Git naming
convention that a Git subcommand must have. So, as git-review (usually invoked
with “git review […]”), this tool can be invoked using “git upstream […]”.
That said, and even if git-upstream currently uses Change-Ids, it is not
strictly related to git-review.
In other words, git-review can (and most of the time will) be used without even
knowing about git-upstream existence.How can I contribute to git-upstream?Git-upstream is in OpenStack:https://git.openstack.org/openstack/git-upstreamAs for any other OpenStack project, contributions are submitted thru the Gerrit
review system.To summarise:create a Gerrit account (that is, a launchpad identity)click on the “Sign in” link in the upper right corner here:https://review.openstack.orginstall git-reviewpip install git-reviewclone the repogit clonehttps://git.openstack.org/openstack/git-upstreamsetup to work with Gerritcd git-upstream
git review -sgit-review will ask the username to use to submit changes to
review.openstack.org, just enter the name you have registered in 1)add cool features or fix nasty bugscreate your commit as usualgit add/rm <…>
git commitsubmit the change for reviewgit reviewThat’s it. You can see your change signing in to your review.openstack.org
account.Hold on tight, someone will come in shortly and will review your change!
Meanwhile, you can join the OpenStack community on IRC. There is also a
specific channel for git-upstream:#git-upstreamIf you need help, please join us on IRC!Before writing new code, it is always a good idea to check if the required
change is already in Gerrit:https://review.openstack.org/#/q/project:openstack/git-upstream,n,zMore info about OpenStack and the Gerrit review process.https://wiki.openstack.org/wiki/IRChttp://www.mediawiki.org/wiki/Gerrit/git-reviewhttp://docs.openstack.org/infra/manual/developers.htmlhttp://docs.openstack.org/infra/manual/developers.html#development-workflowhttps://review.openstack.org/#/q/status:open,n,z
Package: gituptools
Welcome to GituptoolsGituptools is a helper for packing Python on Gitlab CICD runners.  It basically gets as much from the runtime environment as it can to fill in all the packaging metadata that a typicalsetup.pyfile needs.Gituptools is100% standard library.  No 3rd party dependencies.See theDocumentationfor more help.InstallationFromPyPIdirectly:pip install gituptoolsExamplesThis is all you need in asetup.pyfile if you are building on Gitlab CICD.importgituptoolsif__name__=='__main__':gituptools.setup()This is the optionalpyproject.tomlyou can use.[build-system]requires=["gituptools"]This is a basic example of a.gitlab-ci.ymlfile to build and publish your package.image:python:lateststages:-Build-PublishPyPackage:stage:Buildartifacts:paths:[dist/*]script:# option 1: with a pyproject.toml-python -m install -U build-python -m build# option 2: just do it the old way-python setup.py sdist bdist_wheelPyPi:stage:Publishneeds:-job:PyPackageartifacts:truescript:-python -m install twine->twine upload--username $YOUR_USERNAME--password $YOUR_PASSWORD--verbose--non-interactivedist/*
Package: giturlparse
Parse & rewrite git urls (supports GitHub, Bitbucket, FriendCode, Assembla, Gitlab …)This is a fork of giturlparse.py with updated parsers.Original project can be found athttps://github.com/FriendCode/giturlparse.pyInstallingpip install giturlparseExamplesExposed attributesplatform: platform codenamehost: server hostnameresource: same ashostport: URL port (only if explicitly defined in URL)protocol: URL protocol (git, ssh, http/https)protocols: list of protocols explicitly defined in URLuser: repository userowner: repository owner (user or organization)repo: repository namename: same asrepogroups: list of groups - gitlab onlypath: path to file or directory (includes the branch name) - gitlab / github onlypath_raw: raw path starting from the repo name (might include platform keyword) - gitlab / github onlybranch: branch name (when parseable) - gitlab / github onlyusername: username from<username>:<access_token>@<url>gitlab / github urlsaccess_token: access token from<username>:<access_token>@<url>gitlab / github urlsParsefrom giturlparse import parse

p = parse('git@bitbucket.org:AaronO/some-repo.git')

p.host, p.owner, p.repo

# => ('bitbucket.org', 'AaronO', 'some-repo')Rewritefrom giturlparse import parse

url = 'git@github.com:Org/Private-repo.git'

p = parse(url)

p.url2ssh, p.url2https, p.url2git, p.url2http
# => ('git@github.com:Org/Private-repo.git', 'https://github.com/Org/Private-repo.git', 'git://github.com/Org/Private-repo.git', None)URLSAlternative URLs for same repo:from giturlparse import parse

url = 'git@github.com:Org/Private-repo.git'

parse(url).urls
# => {
#     'ssh': 'git@github.com:Org/Private-repo.git',
#     'https': 'https://github.com/Org/Private-repo.git',
#     'git': 'git://github.com/Org/Private-repo.git'
# }Validatefrom giturlparse import parse, validate

url = 'git@github.com:Org/Private-repo.git'

parse(url).valid
# => True

# Or

validate(url)
# => TrueTestspython -munittestLicenseApache v2 (Check out LICENSE file)History0.12.0 (2023-09-24)FeaturesAdd github/gitlab username:access_token parse support (#21)Migrate to bump-my-version (#79)BugfixesFix Gitlab URLs with branch (#42)Align tox.ini with github actions (#71)0.11.1 (2023-08-04)BugfixesRemove debug print statements (#66)0.11.0 (2023-08-03)FeaturesAdd parsing variable for user to gitlab parser (#47)Add support for Python 3.8+ (#48)BugfixesUpdate tests invocation method to avoid future breakages (#29)Update linting tools and fix code style (#34)Add more github use cases (#43)Fix parsing generic git url (#46)0.10.0 (2020-12-05)FeaturesGeneral matching improvements (#18)Update tooling, drop python2 (#10213)0.9.2 (2018-10-27)Removed “s” from the base platform regexFix license classifier in setup.pyUpdate meta files0.9.1 (2018-01-20)First fork release
Package: giturlparse2
Parse & rewrite git urls (supports GitHub, Bitbucket, FriendCode, Assembla, Gitlab …)This is again a fork, now fork ofhttps://github.com/nephila/giturlparse.
Original project can be found athttps://github.com/FriendCode/giturlparse.pyInstallingpip install giturlparseExamplesExposed attributesplatform: platform codenamehost: server hostnameresource: same ashostport: URL port (only if explicitly defined in URL)protocol: URL protocol (git, ssh, http/https)protocols: list of protocols explicitly defined in URLuser: repository userowner: repository owner (user or organization)repo: repository namename: same asrepogroups: list of groups - gitlab onlypath: path to file or directory (includes the branch name) - gitlab / github onlypath_raw: raw path starting from the repo name (might include platform keyword) - gitlab / github onlybranch: branch name (when parseable) - gitlab / github onlyParsefrom giturlparse import parse

p = parse('git@bitbucket.org:AaronO/some-repo.git')

p.host, p.owner, p.repo

# => ('bitbucket.org', 'AaronO', 'some-repo')Rewritefrom giturlparse import parse

url = 'git@github.com:Org/Private-repo.git'

p = parse(url)

p.url2ssh, p.url2https, p.url2git, p.url2http
# => ('git@github.com:Org/Private-repo.git', 'https://github.com/Org/Private-repo.git', 'git://github.com/Org/Private-repo.git', None)URLSAlternative URLs for same repo:from giturlparse import parse

url = 'git@github.com:Org/Private-repo.git'

parse(url).urls
# => {
#     'ssh': 'git@github.com:Org/Private-repo.git',
#     'https': 'https://github.com/Org/Private-repo.git',
#     'git': 'git://github.com/Org/Private-repo.git'
# }Validatefrom giturlparse import parse, validate

url = 'git@github.com:Org/Private-repo.git'

parse(url).valid
# => True

# Or

validate(url)
# => TrueTestspython -munittestLicenseApache v2 (Check out LICENSE file)History1.0.0 (2023-07-22)FeaturesAdd parsing variable for user to gitlab parser (#47)Add support for Python 3.8+ (#48)BugfixesUpdate tests invocation method to avoid future breakages (#29)Update linting tools and fix code style (#34)Add more github use cases (#43)Fix parsing generic git url (#46)0.10.0 (2020-12-05)FeaturesGeneral matching improvements (#18)Update tooling, drop python2 (#10213)0.9.2 (2018-10-27)Removed “s” from the base platform regexFix license classifier in setup.pyUpdate meta files0.9.1 (2018-01-20)First fork release
Package: git-user23
git-userPurpose of the PackageA Python library for GitHub API integration. Retrieve user info, repositories, and more. Simplify GitHub-related tasks effortlessly.Features------List of functions------format_username(username)confirm_username(username)get_response(username)full_name(username)twitter(username)repos(username)bio(username)location(username)repo_count(username)followers_count(username)following_count(username)joined_date(username)confirm_token(username, token)create_repo(username, token, repo_name)DependenciesPython >3
Requestpip install requestsGetting StartedThe package can be found on pypi hence you can install it using pipInstallationpipinstallgit_user23How to useList of functionsformat_username(username)
This function removes leading and trailing spaces from the given username.>>>fromgit_user23import*>>>format_username("           samuelogboye")'samuelogboye'>>>format_username("     samuelogboye        ")'samuelogboye'confirm_username(username)
Checks if a given username is valid on GitHub.>>>fromgit_user23import*>>>confirm_username("samuelogboye")True>>>confirm_username("samuelogboy")Falseget_response(username)
Retrieves all user information from GitHub API and returns it as a dictionary.>>>fromgit_user23import*>>>get_response("samuelogboye")infofull_name(username)
Retrieves the full name of the user>>>fromgit_user23import*>>>full_name("samuelogboye")'Samuel Ogboye'twitter(username)
Retrieves the twitter username of a user>>>fromgit_user23import*>>>twitter("samuelogboye")'samuel_ogboye'repos(username)
Retrieves a list of all repositories owned by the user.>>>fromgit_user23import*>>>repos("samuelogboye")listofrepobio(username)
Retrieves the bio of the user>>>fromgit_user23import*>>>bio("samuelogboye")'Software Engineer || Open Source || Technical Writer || C || Python'location(username)
Retrieves the location of the user.>>>fromgit_user23import*>>>location("samuelogboye")'Nigeria'repo_count(username)
Retrives the count of public repositories owned by the user.>>>fromgit_user23import*>>>repo_count("samuelogboye")30followers_count(username)
Retrieves the count of followers of the user.>>>fromgit_user23import*>>>followers_count("samuelogboye")75following_count(username)
Retrieves the count of users that the user is following.>>>fromgit_user23import*>>>following_count("samuelogboye")64joined_date(username)
Retrieves the date when the user joined GitHub.>>>fromgit_user23import*>>>joined_date("samuelogboye")'2023-02-16'confirm_token(username, token)
Confirms if both username and token are valid. Returns True or False>>>fromgit_user23import*>>>confirm_token("samuelogboye",*********)Falsecreate_repo(username, token, repo_name)
Creates a public GitHub repository instantly with a README file and returns True if successful.>>>fromgit_user23import*>>>create_repo("samuelogboye","******","testing")TrueContributionContributions are welcome
Notice a bug, let us know. ThanksAuthorMain Maintainer: Samuel OgboyeJesus Saves
Package: gitutils
GitMC -- concurrent asynchronous Git Utilities for operations on massive numbers of Git reposPlatform-independent (Linux/Mac/Windows) Git utilities, useful for managing large (100+) numbers of Git repos.
Speed is an emphasis throughout, with concurrency via Python stdlibasyncioviaasyncio.create_subprocess_execand pipelining makes operations in effect 100x faster overall as the coroutines simultaneously wait for Git operations (particularly remote operations like "fetch" and "pull").
We have implemented individual concurrent subprocess timeout usingasyncio.wait_forso that one Git operation hanging doesn't cause other Git operations to fail--this is good for when a Git login popup may go unnoticed by the human.GitMC uses command-line Git because PyGit also requires command-line Git installed, and we don't need the advanced functionality.Also seePyGit-bulkfor managing large (100+) numbers of users / teams.This repo contains aGit pre-commit scriptwithexplanation.InstallInstall Git in a way accessible from the command line lineMac:brew install gitLinux:apt install gitWindows: command lineGit.python-mpipinstall-e.Usagegitbranch: Tells of any non-master branches under directory ~/codepython -m gitutils.email: list all contributor email addresses. To fix unwanted emails useGit-filter-repofind_missing_file: find directories missing exact fullpath to filefind_matching_file: find directories matching exact fullpath to fileSync large number of git reposThese assume numerous subdirectories under~/code.
They work very quickly for large numbers (100+) of repos.gitstatcheck if any local repos have pending changesgitpullGit pulls all repos (suggestgitfetchinstead)gitfetchGit fetches all repos, printing a summary of files changed on remotePlace an empty file.nogitin a subdirectory to skip it.[optional] speedup with https pullFor public repos, to make the Git remote checking go at least twice as fast, and significantly reduce the computational burden when SSH is used forgit push(as is recommended), consider the "pushInsteadOf" global Git config.
To do this, when cloning a public repo (including ones you're a collaborator on), usegit clone https://.
This global SSH push config one-time does SSH push for HTTPS-cloned repos:gitconfig--globalurl."ssh://github.com/".pushInsteadOfhttps://github.com/The pattern matching can be made for all sites by omittinggithub.comfrom the command above, or you can refine it for each site, or even for specific usernames by editing the command above.
For private repos, simply clone with SSH as usualPreview all changed Jekyll filesThis is for a website made usingJekyllorHugo:ActOnChanged.-pIt shows web page previews of all pages changed locally--start the Jekyll or Hugo debug server first e.g.hugo serve
Package: git-utils-py
git-utils-pyis a Python package providing utils task to the Git.InstallationAs of 0.0.5,git-utils-pyis compatible with Python 3.7+.Usepipto install the latest stable version ofgit-utils-py:$pipinstall--upgradegit-utils-pyCommanddownload_file(host, token, project_name, project_id, file_search_path, file_search_name, file_search_extension,
file_output_path, file_output_name=None, branch_name=’master’)
Package: gitutor
GitutorWelcome to Gitutor. This tool is meant to get you up and running using gitmin the shortest time possible while learning on the go.Gitutor is a command line application that wraps git and provides beginner friendly versions of git's commands. It's Git the easy way.You can check out the tutorial and a further explanation of the commands in thedocs. And don't worry if you forget how to use a command you can always run$ gt <command> --helpIf you have any problems please send us an email atsupport@gitutor.ioor open an issue in ourrepo, we usually answer in less than a day.Available commandsgt init - Initialize your local and remote repository.gt save - Save you changes in the local and remote repository.gt goback - Return to a previous commit.gt compare - Compare the current state with a previous commit.gt ignore - Make git ignore selected files.gt lesson - See gitutor lessons and documentation.Installation guideNOTE: pipx and gitutor work with Python3.6+In order to use gitutor without any dependencies version conflicts we recommend installing it using pipx. Pipx creates a virtual environment for your package and exposes its entry point so you can run gitutor from anywhere.To install pipx and configure the $PATH run the following commandsFor Windows:$ python -m pip install pipx
$ python -m pipx ensurepathFor MacOS use:$ brew install pipxFor Linux use:$ python3 -m pip install pipx
$ python3 -m pipx ensurepathNOTE: You may need to restart your terminal for the path updates to take effect.Once pipx is installed, run the following to install gitutor:$ pipx install gitutorAnd to upgrade gitutor to its latest version you only need to run:$ pipx upgrade gitutorTo install gitutor without using pipx just run:$ pip install gitutorAdditional notesBefore using gitutor you need to have Git available in your computer. You can check the installation guidehere.It's also recommended to store your GitHub credentials so you won't have to authenticate everytime you realize a push or pull. You can do this by running$ git config --global credential.helper storeThis will store your credentials in a plain-text file (.git-gredentials) under your project directory. If you don't like this you can use any of the following approaches:On Mac OS X you can use its native keystore with$ git config --global credential.helper oskeychainFor Windows you can install a helper calledGit Credential Manager for Windowsand then run$ git config --global credential.helper managerIf you like what we're doing you can buy as acoffee
Package: git-vendor
# Git VendorThis is a utility to aid in vendoring software projects from Git to => [VCS|Directory]## Why this existsI like to track my upstream development in github, and I have a hard dependency on some projects that live in bzr/Launchpad. BZR and Launchpad are both great systems, I just have a long running preference for git/github. This python module allows me to track and maintain my history in git, while running exports for tag releases to a directory that is independently tracked by BZR.I’m not so much concerned with the commit history as I am with ensuring my tags are what make the porting phase, and they are high quality without requiring a joint VCS tree and other plugin wizardry.## How it worksThe plugin only works with git tags, and will not operate on a dirty branch. This allows me to adopt the workflow of cycle until features/bugs are complete in a given milestone. Export that code to the bzr repository and run a checkin of everything that happened from A -> Z along with a Changelog to track what happened independently of the BZR VCS.  This is a fairly simple process that can be done manually without much fuss - but like anything I do repeatedly: it’s even nicer to have a tool do the drone work for me.## Getting StartedClone the repositorygit clonehttp://github.com/chuckbutler/git-vendor.gitcd git-vendorCreate a virtualenv to isolate dependencies from your systemvirtualenv .venv/
source .venv/bin/activate
python setup.py installWhile the virtual env is active, you can call git-vendor like you would any other executable.git-vendor -h#### Basic Usagegit-vendor works with a single initialized configuration file.git-vendor initThis will create a .vendor-rc file which you can edit and place ignored files. It’s pre-populated
with some common patterns for you.git tag mytagWhen you are ready to vendor a git repository to bzr:git-vendor sync -d /path/to/bzr/repositoryyou will be presented with a list of tags from your git repo to pick and export. Now you can head
over to your bzr repository, commit and push as you see fit. Enjoy!
Package: gitvenv
gitvenvTool to manage multiple Git environments.Strongly based on python's venv module.gitvenv defines four environment variables to make the environment work:GIT_VIRTUAL_ENV– a convenience variable pointing to the environment directory.GIT_CONFIG_GLOBAL– tells Git to use config from the environment.GIT_VIRTUAL_ENV_SSH_CONFIG– a convenience variable pointing to SSH config.GIT_SSH_COMMAND– tells Git to use SSH command with config from the environment:$GIT_SSH -F /path/to/env/ssh_config. IfGIT_SSHis undefined,sshwill be used instead.InstallationUsing pippipinstallgitvenvUsing AURgitclonehttps://aur.archlinux.org/python-gitvenv.gitcdpython-gitvenv/
makepkg-siUsing Gitgitclonehttps://gitlab.com/yataro/gitvenv.gitcdgitvenv/
pipinstall.Usageusage: gitvenv [-h] [--clear] [--copy] ENV_DIR

Creates a virtual Git environment in the target directory.

positional arguments:
  ENV_DIR     A directory to create the environment in.

options:
  -h, --help  show this help message and exit
  --clear     Delete the contents of the environment directory if it already exists, before environment creation.
  --copy      Copy the current config files to the new environment.

Once an environment has been created, you may wish to activate it, e.g. by sourcing an activate script in its bin directory.bash and PowerShell are currently supported:bashgitvenvmy_env/sourcemy_env/bin/activate# Use environmentgitconfig--globaluser.name'John Doe'gitconfig--globaluser.email'john@example.com'# Deactivate environmentgitvenv_deactivatePowerShellgitvenvmy_env/.\my_env\bin\Activate.ps1# Use environmentgitconfig--globaluser.name'John Doe'gitconfig--globaluser.email'john@example.com'# Deactivate environmentgitvenv_deactivate
Package: gitverse
GitVerseGet GitHub's release notes or commit history and format it intoreStructuredText/Markdowndocuments.InstallationpipinstallgitverseUsageRelease Notes (Tags)Generate release notes from releases tagged in GitHubgitverse-releaseTries to get release notes, using GitHub APIIf failed, uses the commit message as notes for the associated releaseThis feature optionally takesGIT_TOKENas an environment variable if it is generated for a personal repoKnown issue related to the order of release notesThere is a known issue with GitHub where thegit tagcommand returns incorrect timestamp(when tags are created in different timezones)If the release notes are not generated in the expected order, please run the following command to verifygitfor-each-ref--sort='-creatordate'--format'%(refname:short) %(creatordate:iso8601)'refs/tagsIf the output is in expected order, please raise anissueCommit HistoryGenerate commit history from git loggitverse-commitOptionsdebug- Enable debug mode for logging.reverse- Generate commit history/release notes in reverse order.Flags-bGather commit notes specific to a branch. UsesDefault branchif not passed. (Only forgitverse-commit)-fWrite the commit notes to a custom filename.-tTitle or index line for the file generated.Samplerelease_notes.rstchangelog.rstLintingPreCommitwill ensure linting, and the doc creation are run on every commit.Requirementpipinstallsphinx==5.1.1pre-commit==2.20.0recommonmark==0.7.1Usagepre-commitrun--all-filesPypi Packagehttps://pypi.org/project/gitverse/Runbookhttps://thevickypedia.github.io/gitverse/License & copyright© Vignesh Rao, GitVerseLicensed under theMIT License