Saravanan666/pypi-org huggingface dataset:
Package: gitrecipe
Welcome to gitrecipe doc pageUsageRecipe clones git repository and checkouts to revision, if it is provided
in configuration. You can use recipe like this:[buildout]
parts = data

[data]
recipe = gitrecipe
repository = git://example.com/my-git-repo.git
rev = origin/redevlop-branchOptionsrepository- repository urlrefofrev- gitreferencewich you want to checkoutNotesrevoption leaved for compatibility withzerokspot.recipe.git.
It is better to userefparameter, because it corresponds Git terminologySince 0.0.2 recipe does check existing repository while install and update.
Repository origin url must be the same as given inrevoption.
Otherwise repository will be deleted and cloned again.AboutI’ve used recipezerokspot.recipe.git, but as for me, it too complex and has some disadvantages:it does not allow commit from the source folder, default remote is local copy in downloadsit does not allow to specify the tag or branch of the repository, only revision hashSo I wrote my own git recipe with compatible options. You can choose this or that.
Package: git-recipe
Welcome to git-recipe doc pageUsageRecipe clones git repository and checkouts to revision, if it is provided
in configuration. You can use recipe like this:For python[buildout]
parts = data

[data]
recipe = git-recipe
repository = git://example.com/my-git-repo.git
ref = origin/redevlop-branch
as_egg = True
newest = TrueFor static resouces[jquery]
recipe = git-recipe
repository = git://github.com/jquery/jquery.git
ref = origin/master
download-directory = ${buildout:directory}/static/js/For django plugins with bad repository name[paypal]
recipe = git-recipe
repository = git://github.com/johnboxall/django-paypal.git
ref = origin/master
repo_name = paypal
as_egg = TrueOptionsrepository- repository urlref- gitreferencewich you want to checkout.For example, it can be abranch name or a tag name like “origin/master”、or “v1.0”.download-directory- If filled it will make the clone in this folder.repo_name- If filled it will change the repository name.as_egg- Set to True if you want the checkout to be registered as adevelopment egg in your buildout.newest- always download newest repository, default is true.And you can use buildout’s globalofflineconfigure.AboutThis is a fork ofgitrecipe, which doesn’t support
the as_egg feature ofzerokspot.recipe.git.CHANGES0.2    add custom repository name for django plugins.0.1    add custom directory support for static resources.0.0.4  determine repository  now support ‘.’ and ‘_’ in its name.0.0.3  add offline/newest configuration.
Package: git-redmine
Redmine integration to git.ConfigurationAdd the following snippet to your .config/git/config file.:[redmine]
url = https://redmine.mycompany.org/
key = apikey

   OR

username = username
password = passwordUsageprojectShow the current default project.project setSet the current default project for this repository, useful for creating new
issues.:git redmine project set myproject-idrebaseCheckout master, pull origin/master on master then rebase current feature
branch on master, if it fails it reset the branch. Checkout the original branch
after all this.git redmine rebaseissue newGiven a default project, create a new issue, an editor is launched to define
subject and description of the issue.:git redmine issue newissue takeHandle the given issue by creating or switching to a branch namedwip/<issue-number>-<slugified-issue-subject>forking frommaster.:git redmine issue take 123It will propose applying patches attached to the issue.issue showShow information about the current issue.:git redmine issue showShow informations about issue 9999.:git redmine issue show --issue 9999issue submitIt first does agit redmine rebasethen usegit format-patchto create the
patch serie frommasterand attach it to the current issue. An editor is
launched to add a commment.:git redmine issue submitTo submit only the last commit:git redmine issue submit 1To submit the last commit to issue 9999:git redmine issue submit --issue 9999 1issue applyApply patches attached to the current issue.:git redmine issue applyApply patched atteched to issue 9999.:git redmine issue apply --issue 9999linkgit redmine link 9999Link current branch issue to issue 9999.merge-and-pushMerge current feature branch in a target branch (default is master), push
target branch to origin, delete feature branch locally and on origin; if before
that those operations pass: pull-rebase the target branch, rebase feature
branch on target.git rebase merge-and-pushcleanRemove local and remote branch for issues closed more than 21 days ago. Use
–no-local to only clean local branches.git redmine clean [–local/–no-local]
Package: git-refs
# git refslist git references(branches, tags) on local and remote repositories.## Installpip3 install -U git-refs## Example`bash $git-refslocal branch master 5a4344acd93627b7e20d5c86aa18a587c90a17d9->origin/master remote reference master 5a4344acd93627b7e20d5c86aa18a587c90a17d9 origin `### CSV output format`bash $ CSV=1git-refswhere,type,name,sha,remote local,branch,master,5a4344acd93627b7e20d5c86aa18a587c90a17d9,origin/master remote,reference,master,5a4344acd93627b7e20d5c86aa18a587c90a17d9,origin `You can use [printable](https://github.com/weaming/printable) to view csv in terminal:CSV=1 git-refs | printable -t csv -f /dev/stdin
Package: git-regex-search
GitHub Search Using RegexSaikat Karmakar | 28 Jan:2023This program allows you to search for a specific pattern within the files of a GitHub repository(Using PyGithub). The program utilizes regular expressions and multithreading to quickly search through the repository's contents and return all files that contain the specified pattern.FeaturesSearch for a specific pattern in the files of a GitHub repositorySupports single repository or file containing multiple repository URLsUses multithreading to improve search performanceInstallation# using pippipinstallgit-regex-searchTo use this program, you will need to have Python 3 and the PyGithub library installed. You can install PyGithub using pip:pip3install-rrequirements.txtYou will also need to have a GitHub personal access token. You can create one by going to theGitHub Developer Settings.UsageTo use the program, you will need to provide a GitHub access token. The token can be passed as an environment variable or in a config.toml file. The program will look for the token in the following order:GITHUB_TOKENenvironment variableconfig.tomlfilepython3git_regex_search.py-husage:git_regex_search.py[-h][-uURL][-rREGEX]options:-h,--helpshowthishelpmessageandexit-uURL,--urlURLURLoftherepository(singleorfilecontainingURLs)-rREGEX,--regexREGEXRegexpatterntosearchforFor example, to search for the patternbrowniein the repositoryAviksaikat/RoadClosed-quillctf-brownie, you would run the following command:python3git_regex_search.py-uhttps://github.com/Aviksaikat/RoadClosed-quillctf-brownie-r"brownie"The program will then return a list of all files that contain the specified pattern, along with the line number where the pattern was found.MultithreadingThe program utilizes multithreading to search through the repository's contents more quickly. Two threads are created and run simultaneously, each searching through the repository's contents. This allows the program to search through the repository's contents much faster than if it were only using a single thread.Regular ExpressionsThe program utilizes regular expressions to search for the specified pattern within the files of the repository. This allows for more powerful and flexible searches, as opposed to simple string matching.DockerYou can build the image by running the following command in the same directory where the Dockerfile is located:dockerbuild-t<image-name>.You can then run the container using the following command:dockerrun-eGITHUB_TOKEN=<access_token><image-name>LimitationsThis program only searches the contents of the files and not the name of the files. For my use I don't need it to search the names.Additional FeaturesThe program also prints the whole file path where the pattern was found, which is helpful in identifying the location of the pattern.ConclusionThis program is a powerful tool for quickly searching through the contents of a GitHub repository and finding specific patterns. With the use of regular expressions and multithreading, it is able to search through large repositories quickly and efficiently.Version 0.3Published as pip packagehttps://pypi.org/project/git-regex-search/0.3/
Package: git-release
git-releaseEasily generate tag-based releases. Uses the powerfulgit-cliffto generate changelogs. These can then be leveraged viagithub actionsInstallation# Install dependenciescargoinstallgit-cliff# Install git-releasepipinstallgit-releaseUsageusage: git-release [-h] [--comment COMMENT] [--remote REMOTE] [-v] [--semver SEMVER] [--major | --minor | --patch | --no-inc]

optional arguments:
  -h, --help            show this help message and exit
  --comment COMMENT, -c COMMENT
                        A comment to describe the release. Synonymous to a tag message. Defaults to the generated changelog.
  --remote REMOTE, -r REMOTE
                        The repository remote (defaults to 'origin')
  -v, --verbose         NOT IMPLEMENTED YET

Semantic Version:
  Options to manipulate the version. If --semver is not passed, git-release uses the most recent tag.

  --semver SEMVER       Custom semantic version. Use --no-inc to use as is.
  --major, -M           Increment the major version by 1 (resets minor and patch)
  --minor, -m           Increment the minor version by 1 (resets patch)
  --patch, -P           Increment the patch version by 1 (default behaviour)
  --no-inc              Don't increment anythingContributingEnsure thatpre-commitis installed and working. Otherwise the pre-commit CI will most likely fail.# Install and setup pre-commitpipinstallpre-commit
pre-commitinstall--install-hooksRepos that have used git-releaseiwishiwasaneagle/jsim
Package: git-releaseit
Git-Releaseit==========`git-releaseit` adds a git command which will smartly auto-increment git release tags.  It currently only supports tags following the `major.minor` convension.Getting Started===============You can get started with `git-releaseit` by using PIP:```pip install git-releaseit```This can be done in a virtual environment or at the system level.From then on, you can tag your new releases with something like:```git release major```or```git release minor```where `major` indicates a major release and will increment the major version number and reset the minor, and `minor` indicates a minor release and will increment the minor version number and leave the major version number alone.The command also supports the `-s` option, which will attempt to sign the tag.The tags are annotated by default, so a `-a` option is not needed.
Package: git-release-tagger
Small CLI utility to enable the CI environment to communicate the deployment progress through the use of git tags.Installation$pipinstallgit-release-taggerUsage$tag-release[-h][-tTRIGGER][-v][-mMESSAGE]prefix{pending,deploying,failed,success}Prefix is self explanatory.If the release was triggered by a tag (like ‘release’) - use the–triggeroption to have the tagger remove it automatically.
This enables the user to retry a failed deployment just by tagging the same commit again.Use-mto add a message to the commit. For example - a link to the build status on Jenkins / TeamCity / other CI.Examples$tag-releaseproductionpendingwill remove tags:‘production_pending’,‘production_deploying’,‘production_failed’,‘production_success’will add tags:‘production_pending’$tag-releaseproductionsuccesswill remove tags:‘production_pending’,‘production_deploying’,‘production_failed’,‘production_success’will add tags:‘production_success’‘production_success_2015-11-02_16_34_26’$tag-release-tproductionproductionsuccesswill remove tags:‘production’‘production_pending’,‘production_deploying’,‘production_failed’,‘production_success’will add tags:‘production_success’‘production_success_2015-11-02_16_34_26’Release History0.0.2 (2016-03-09)‘git push’ is run with –no-verify to skip pre-push hooks.0.0.1 (2015-11-03)Initial release.
Package: git-relevant-history
git-relevant-historyExtract software component from git repo into a new repo, taking complete relevant history with it.BackgroundWhen software evolves, it is typical for a stable, established software component to be moved out of a git repository to facilitate more comprehensive reuse. One of the pain points of such a move would be losing git history, breaking the possibility of usinggit blameorgit logto understand what led to the current design.Historically git filter-branch was used for such extracting, andhttps://github.com/newren/git-filter-repois a much faster alternative recommended by git now. Both tools work on a static list of path patterns to preserve, so file renames in the past are usually "cut point."This tool also starts with "what is subcomponent in the current repo to extract?" but then analyzes the history of renames for any existing file. Such a list is used to create a list of patterns forgit filter-reposo that effectively the old repo/component becomes standalone repo with a full history of every file, as long as git --follow catches the rename.So from the extracted component perspective, the only history "lost" is one that would require manual analysis of commits to find file merging/splitting.HelpUsage documentation for the tool is available via cmdline:git-relevant-history --help :Extract enough git history to facilitate git blame and have each line correctly annotated

Wipe all history that has no connection to the current state of the repository.

The resulting repository is a drop-in replacement for the old directory and has all history needed for typical git history use.

Usage:
  git-relevant-history [options] --source=<source_repo> --subdir=<subdir> --target=<target_repo>

Where git repo at <source_repo> would be processed into <target_repo>, in a way that only files starting with
<subdir> would be preserved.


Options:
  --only-specs         Only print git filter-repo specs file as expected by git filter-repo --paths-from-file
  -h --help            show this help message and exit
  -f --force           remove <target_repo> if exists
  -v --verbose         print status messages
Package: git-remote
Installation$[sudo]pipinstallgit-remoteExamples>>>importgit_remote>>>git_remote.add("github","git@github.com:owner/repo.git")>>>git_remote.remotes()[['github','git@github.com:owner/repo.git']]>>>git_remote.names()['github']>>>git_remote.urls()['git@github.com:owner/repo.git']>>>git_remote.set_url("github","git@github.com:owner/repo2.git")>>>git_remote.rm("github")readme42.com
Package: git-remote-couch
Author:Filip NoetzelVersion:v0.1aWeb:http://github.com/peritus/git-remote-couch/Git:git clonegit://github.com/peritus/git-remote-couch.git(browse source)Download:Downloads page on GitHubAbstractgit-remote-couchis agit-remote-helperthat allows you to push source code into aCouchDB(you can then fetch a clone from it, of course).WarningThis software is very slow and a three headed monkey will eat your data!  It
should not be used to save valuable production source code!ALWAYSkeep
at least a second copy using other backup mechanisms.NoteThis is a fun project for me to learn some git and CouchDB internals. Also, I
want to writeCouchAppsthat handle
source code. Patches welcome.Installation and UsageFirst, installgit-remote-couchvia your favorite Python package installing mechanism, like so:easy_install -U git-remote-couchThen, you can start cloning a repository:git remote add couch http+couch://localhost:5984/testrepo/
git push origin masterYou can now browse your repository with CouchDB’s web interface athttp://localhost:5984/_utils/database.html?testrepoor clone that
repository:git clone http+couch://localhost:5984/testrepo/ a_copy
Package: git-remote-cvm
git-remote-cvmThis package provides a simple method for pushing and pulling fromAWS
CodeCommitusing the CVM. This package extendsgitto support repository URLs prefixed withcvm://.… you can clone repositories as simply as…% git clone cvm://role-name@account-name/repository-nameThegit-remote-cvmpackage works on Python versions:3.6.x and greater3.7.x and greaterPrerequisitesBefore you can usegit-remote-cvm, you must:Complete initial configuration for AWS CodeCommit, including:Install and configure the CVMCreate an AWS CodeCommit repository (or have one already) in your AWS account.Install Python and its package manager, pip, if they are not already installed. To download and install the latest version of Python,visit the Python website.Install Git on your Linux, macOS, Windows, or Unix computer.Install the latest version of the AWS CLI on your Linux, macOS, Windows, or Unix computer. You can find instructionshere.Note: Installation of the AWS CLI on some operating systems requires pip version 9.0.3 or later. To check your version of pip, open a terminal and type the following command:% pip --versionIf the version is not 9.0.3 or later, run the following commands to update your version of pip:% curl -O https://bootstrap.pypa.io/get-pip.py
% python3 get-pip.py --userSet UpStep 1: Install git-remote-cvmOn your Linux, macOS, Windows, or Unix computer, installgit-remote-cvmusing thepipcommand. For example:% pip3 install git-remote-cvmIf you already havegit-remote-cvminstalled you can upgrade to the latest version with the–upgradeparameter:% pip3 install --upgrade git-remote-cvmStep 4: Clone your repositoryAt the terminal, run thegit clone cvmcommand, using the details of your repository. For example:% git clone cvm://power-user-role@dev-account/web-project-1
Cloning into 'web-project-1'...
remote: Counting objects: 1753, done.
Receiving objects: 100% (1753/1753), 351.77 KiB | 1.91 MiB/s, done.
Resolving deltas: 100% (986/986), done.
Package: git-remote-get
git-remote-getDownload single files or directories from a git remote repository without cloning its entire contents.Installationpipinstallgit-remote-getUsageUsage:git-remote-get[OPTIONS]PATH[DESTINATION]GetafilefromaremotegitrepositoryArguments:PATH:ThepathontheremoterepositorytogetthefilefromDESTINATION:Thepathtosavethefileto.Defaultstothesameasthepath.

Options:--repoTEXTTherepotogetthefilefrom.YoucanalsosettheGGET_REPOenvironmentvariabletosetthisoption.--fromTEXTAliasfor--repo--ownerTEXTTheowneroftherepotogetthefilefrom.YoucanalsosettheGGET_OWNERenvironmentvariabletosetthisoption.[required]--provider[github]Theremoterepositoryprovidertogetthefilefrom.Defaultstogithub.Currently,onlygithubissupported.YoucansettheGGET_PROVIDERenvironmentvariabletosetthisoption.--refTEXTBranchorcommittogetthefilefrom.Defaultstomaster.YoucansettheGGET_REFenvironmentvariabletosetthisoption.--helpShowthismessageandexit.You can also use theggetalias forgit-remote-get.Examples# This will download the README file from the octocat/Hello-World repository# and save it to the current directory with same nameggetREADME--owner=octocat--repo=Hello-World# This will download the README file# and save it to docs/README.mdggetREADME--owner=octocat--repo=Hello-Worlddocs/README.md# This will download `examples/tutorial`# of flask repository and save it to the current directory.## If destination is not provided, the program# will create a directory with the same name as the PATH.## In other words, you will get `examples/tutorial` directory# and its contents inside that directory.ggetexamples/tutorial--owner=pallets--repo=flask--ref=main# This will download the `examples/tutorial`# of flask repository and save it to `tutorial` directory.## In this case, the destination is provided.# Contents under `examples/tutorial` will be saved to `tutorial-contents` directory.ggetexamples/tutorial--owner=pallets--repo=flask--ref=maintutorial-contents
Package: git-remote-hg3
Are you a git junkie but need to work on projects hosted in mercurial repos?
Are you too stubborn, lazy or maladjusted to learn another VCS tool?  I
know I am.  But fear not!  This script will let you interact with mercurial
repositories as if they were ordinary git remotes.Git allows pluggable remote repository protocols via helper scripts.  If you
have a script named “git-remote-XXX” then git will use it to interact with
remote repositories whose URLs are of the form XXX::some-url-here.  So you
can imagine what a script named git-remote-hg will do.Yes, this script provides a remote repository implementation that communicates
with mercurial.  Install it and you can do:$ git clone hg::https://hg.example.com/some-mercurial-repo
$ cd some-hg-repo
$ # hackety hackety hack
$ git commit -a
$ git pushTada!  Your commits from git will show up in the remote mercurial repo, and
none of your co-workers will be any the wiser.All the hard work of interoperating between git and mercurial is done by the
awesome hg-git module.  All the hard work of speaking the git-remote-helper
protocol is done by git’s own http-protocol handlers.  This script just hacks
them together to make it all work a little easier.For each remote mercurial repository, you actually gettwoadditional
repositories hidden inside your local git repo:.git/hgremotes/[URL]:           a local hg clone of the remote repo.git/hgremotes/[URL]/.hg/git:   a bare git repo managed by hg-gitWhen you “git push” from your local git repo into the remote mercurial repo,
here is what git-remote-hg will do for you:use git-remote-http to push into .git/hgremotes/[URL]/.hg/gitcall “hg gimport” to import changes into .git/hgremotes/[URL]call “hg push” to push them up to the remote repoLikewise, when you “git pull” from the remote mercurial repo into your local
git repo, here is what happens under the hood:call “hg pull” to pull changes from the remote repocall “hg gexport” to export them into .git/hgremotes/[URL]/.hg/gituse git-remote-http to pull them into your local repoUgly?  Sure.  Hacky?  You bet.  But it seems to work remarkably well.By the way, there is apparently a native implementation of a git-remote-hg
command in development:https://plus.google.com/115991361267198418069/posts/Jpzi24bYU91Since the git-remote-helper protocol is pretty simple, it should be possible
to switch back and forth between that implementation and this one without any
hassle.WARNINGS:Pushing multiple branches into the remote is currently broken.hg-git seems to map git branches onto mercurial bookmarks, but I’m not
sure of all the details.  I don’t need it so I haven’t tried to make it
work.  Don’t do it.
Package: git-remote-oracle
git-remote-oracleSource can be found onhttps://github.com/TheCrazyT/git-remote-oracle.Can be used in combination with git to view made changes in packages.It isNOTintended to be a full backup of the database structure.Requirementspython 3gitpip-packages:pexpectoracleUsageusage example can be found here:https://github.com/TheCrazyT/git-remote-oracle/blob/main/tests/google_colab_docker_oracle_xe.ipynbfor example you can do:git clone oracle://127.0.0.1:1521/XEPDB1/JOHNthis will ask for credentials and create a folder called JOHN.But it works only if that scheme exists and you have access to it!(There is currently no validation, so you won't get a proper error message).Environment variablesNameDescriptionGR_ORACLE_DEBUGDebug informationsGR_ORACLE_DEBUG_GITOutput of all internal output to git itself to the consoleGR_ORACLE_SYSDBASet flag that you run as sys user