Saravanan666/pypi-org huggingface dataset:
Package: git-remote-rclone-reds
Git remote helper for rclone-supported servicesThis is aGit remote helperfor
backends supported byrclone. In other words, this
helper makes it possible to push and pull to a large number of storage services
with no native Git support.UsageVisit therclone websiteand follow the instructions for
installation ofrclone, and configuration of access to the desired
service(s). Install this package via pip (pip install git-remote-rclone), or
place thegit-remote-rcloneexecutable provided here into the system path,
such that Git can find it. Now it is possible to use URLs likerclone://<remote>/<path-on-remote>as push and pull URLs for Git.For example, if access to a DropBox account has been configured as an rclone-remote
namedmydropbox, the URLrclone://mydropbox/myrepositoryidentifies a remote
in a directorymyrepository/under this DropBox account.Technical detailsAt the remote end,git-remote-rclonemaintains a directory with two files:refs: a small text file listing the refs provided by the remoterepo-<SHA>.tar.gz: an archive of a bare Git repositoryWhen interacting with a remote,git-remote-rcloneobtains and extracts a copy
of the remote repository archive (placed at.git/rclone/<remote-name>in the
local Git repository). All Git operations are performed locally. Whenever the
state of the mirror repository has changed, it is compacted to minimize transfer
size and uploaded to the remote storage service. Likewise, the remote storage
service is checked for updates before the local mirror repository is updated.git-remote-rcloneaims to minimize API usage of remote storage services. Per
invocation, it only queries for the state of a remote repository archive
(checksum), downloads two files (if needed), and uploads two files (if needed,
and on push only).Tested withrclone1.63.1Google DriveOnedriveDropBoxAcknowledgementsThis work is based ondatalad/git-remote-rclone. This work changes the
design for compatibility with rclone backends like crypt that do not support file
hashes.
Package: git-remote-run
This package defines agit-remote-runcommand, which allows running
custom commands on a git remote.This can be used, for example, to set up the actual remote repository,
as in:$gitremoteaddremote-repouser@server:path/to/repo$gitremote-runremote-repo-c'
    mkdir -p $REPO_DIR
    git init --bare $REPO_DIR
    echo echo it works! > $REPO_DIR/hooks/update
    chmod +x $REPO_DIR/hooks/update'InitializedemptyGitrepositoryin/home/user/path/to/repo/$gitpushremote-repomaster...remote:itworks!Seegit remote-run -hfor more options.How does it work?git-remote-rundoesn’t attempt any parsing of the git remote URL
on its own, nor does it make assumptions about the transport used.
Instead, it relies on git’s built-in ability to run commands on the
remote side.Git uses this ability in itsgit archive –remote=…command, to
create an archive of a remote repository. We abuse this ability
a little bit by sending a custom script to run as the–execparameter.AuthorRadek CzajkaLicenseThis project is licensed under the MIT License – see the LICENSE file for details.
Package: git-repo-cli
Git Repo CLIUtils to easily create/delete/rename repository.InstallationTo install git-repo-cli util type in your terminal:pipinstallgit-repo-cliTo use all the git-repo-cli functionality you should configure GitHub access token.git-repoconfig--token<github-token>Now you can use it.UsageTo make usage of the cli easiergit-repois used, instead ofgit-repo-cli.
To get help on usage you can always add --help flag to the command:git-repo--helpInitialize repositoryTo initialize repository type the following in the terminal:git-repoinit<repository-path>It will create folder with name of<repository-path>folder and initialize it
locally and remotely.If you use other name on remote you should use the following pattern:git-repoinit<repository-name>-f<repository-local-path>It will create repository with name<repository-name>on remote and with path<repository-local-path>locally.Delete repositoryTo delete a repository use the following command:git-repodelete<repository-path>Rename repositoryTo rename a repository use the following command:git-reporename<repository-path><repository-new-name>ContributingSeeCONTRIBUTING.mdLicenseMIT
Package: git-repo-info
Provides access to a local git repository’s configuration.Free software: MIT licenseInstallationpip install git-repo-infoDocumentationhttps://python-git-repo-info.readthedocs.io/DevelopmentTo run the all tests run:toxNote, to combine the coverage data from all the tox environments run:Windowsset PYTEST_ADDOPTS=--cov-append
toxOtherPYTEST_ADDOPTS=--cov-append toxChangelog0.1.0 (2017-06-29)First release on PyPI.
Package: git-repo-master
git-repo-masterSimple application to manage your Azure DevOps git repositoryInstallationgitclonehttps://github.com/mustafmst/git-repo-master.git
pythongit-repo-master/setup.pyinstallUsage$grm-h

usage:__main__.py[-h][-organizationORGANIZATION][-projectPROJECT][-repositoryREPOSITORY[REPOSITORY...]][-tokenTOKEN][-action{lock-branch,unlock-branch,create-pull-request}][-branchBRANCH][-sourceSOURCE][-targetTARGET][-titleTITLE][-descriptionDESCRIPTION]optionalarguments:-h,--helpshowthishelpmessageandexitAllarguments:-organizationORGANIZATIONAzureDevOpsorganization-projectPROJECTAzureDevOpsprojectingivenorganization-repositoryREPOSITORY[REPOSITORY...]Repoforaction-tokenTOKENPersonalaccesstokenforAzureDevOps-action{lock-branch,unlock-branch,create-pull-request}Actiontoperform

Branchlockandunlockactionsarguments:-branchBRANCHBranchtoperformactionon

Createpullrequestactionarguments:-sourceSOURCEBranchnamefromwhichactionhastobedone-targetTARGETBranchnametowhichactionhastobedone-titleTITLEPullrequesttitle-descriptionDESCRIPTIONPullrequestdescription
Package: git-repo-move
git-repo-moveMove files from one git repo to another, preserving history!
Under the hood, this utility usesgit filter-branch, but the API is much more user friendly.How-ToInstallpipinstallgit-repo-moveBuild LocallypoetrybuildRun ItIf you've already installed in viapip, it's really easy to use.
The program is calledgit-repo-move.
You can also checkout the source and build locally by running:poetryinstall--no-devSelect Files and DirectoriesSelect what files you want to keep by specifying:--filepath/to/file.txt--filepath/to/another_file.txtand what directories you want to keep by specifying:--directorypath/to/subfolder--directorypath/to_anothersubfolderSelect the Final Directory for the FilesOptionally, specify the final directory for the files--final_directorynewpath/to/thefilesSelect Directory StructureYou can either flatten all files or keep the original directory structure--directory-structure<FLAT|ORIGINAL>For example:--filepath/to/file.txt--final-directorynewpath/to/thefiles--directory-structureFLATfile.txtwill end up atnewpath/to/thefiles/flat.txt--filepath/to/file.txt--final-directorynewpath/to/thefiles--directory-structureORIGINALfile.txtwill end up atnewpath/to/thefiles/path/to/file.txtSpecify the Git Remote URL of the Destination RepoYou can rungit remote -vto get a list of remote URLs.--git-remote-urlgit@github.com:AlanRosenthal/git-repo-move.gitSpecify the Git Branch NameRemember this branch will used on both repos.--git-branchmove_filesSave Shell ScriptThis utility generates a shell script.
By default, the script will be saved in the root of the repo with the namegit-repo-move.sh.You can change the default name by specifying--shell-script-namebest-script-ever.shIt is recommended to include the generated shell script on your PR.Optionally, don't save a shell script by specifying the--dont-save-shell-scriptflag.Try It OutThis utility usesgit-filter-branchwhich is relatively slow, especially for large repos.
It usually takes a few attempts to specify the correct files and directories.By specifying the--try-keepflag,git-repo-movewill move the specified files into a folder.
Inspect that folder to ensure everything is correct.ExecuteBy specifying the--executeflag, the generated script will be executed.ExampleWe're usingclickfor the example.We want to savesrc/click/formatting.pyandsrc/click/parser.pyand have them end up in the folderalan/click.Running the command:git-repo-move--fileclick/formatting.py--filesrc/click/formatting.py--fileclick/parser.py--filesrc/click/parser.py--final_directoryalan/click--directory-structureflat--git-remote-urlgit@github.com:AlanRosenthal/git-repo-move.git--git-branchmove_files_example--executeNote: We're includingclick/formatting.py&src/click/formatting.pyandclick/parser.py&src/click/parser.py.
Files were moved fromclicktosrc/click.git-blameknows how to capture files history across moves, butgit-filter-branchdoes not.As you can see, themove_files_examplebranchhas contains two files,formatting.pyandparser.py.
Both files contain the history from their original repo.
Package: gitreport
Git ReportInstallation# recommend to avoid cachedpipinstallgit+https://github.com/peelz/git-report# or install from repositorypipinstallgitreportParametersusage:cli.py[-h]--projectsPROJECTS[PROJECTS...]--authorsAUTHORS--monthMONTH--output-fileOUTPUT_FILE

optionalarguments:-h,--helpshowthishelpmessageandexit--projectsPROJECTS[PROJECTS...],-pPROJECTS[PROJECTS...]projectdircanbelist--authorsAUTHORSauthorpatternnameuseforfilter--monthMONTH,-mMONTHnumbermonthofyear--output-fileOUTPUT_FILE,-oOUTPUT_FILEenddateformatdd/mm/yyyyExample# Unixgireport-p~/path/to/project-m5-apeelz-o./output.xlsx# Windowgireport-pC:\path\to\project-m5-apeelz-ooutput.xlsx
Package: git-repos
Git reposManages git repos inside a directory.Installpip install git-reposUsageInside a directory with several git repos run:reposTo check all available commands:$ repos help
NAME
    repos —  Manages your git repos

USAGE
    repos                       # Lists all repos in text format
    repos export --json         # Exports all repos as json
    repos export --yaml         # Exports all repos as yaml
    repos show REPO             # Saves configured repos
    repos save                  # Saves configured repos
    repos push                  # Pushes to upstream
    repos pull                  # Pulls from upstream
    repos sync                  # Pull from upstream and save
    repos help                  # Shows this help
    repos version               # Prints the current version
Package: gitrepoxmlparser
GitRepoXMLParserCapable of processing the AOSP repo's manifest file differentiating from the supplierGitRepoXMLParser helps you visualize your AOSP manifest files that is fed forrepotoolRich-powered visualization.Manifest file example<manifest><remotefetch="url"name="pj-gerrit"review=""/><includename="supplier.xml"/><includename="pj_apps.xml"/><remove-projectname="pathto/projec"/><projectname="supplier/pathto/projectrepo"path="company/pathto/projectrepo"remote="pj-gerrit"revision="branch_name"/><projectname="PJ/pathto/projectrepo1"path="vendor/pathto/projectrepo1"remote="pj-gerrit"revision="branch_name"/><projectname="PJ/pathto/projectrepo2"path="vendor/pathto/projectrepo2"remote="pj-gerrit"revision="branch_name"/>
</manifest>FeaturesVisualize your manifest.xml files visuallyThe table size depends on the screensize of the command line utility that you are running the scriptInstallationgitrepoxmlparser requiresRich12.5.1+.pipinstallgitrepoxmlparserUsagecmd>gitrepoxmlparser-h
usage:-m[-h]-fF-cC-sS[-x]options:-h,--helpshowthishelpmessageandexit-fFmanifestxmlfile-cCYourcompanyname(Shouldmatchwithcompaniesfoldernameinthestack)-sSSupplier'sCompanyname(justcontrastswithonlyonevendor)-x,--htmlForhtmlreportBuilding the sourceTo activate the virtual envpoetryshellInstalling dependencies onlypoetryinstall--no-rootTo install the dependencies and install the package (reads the poetry.lock or pyproject.toml file )poetryinstallLicenseMITFree Software, Hell Yeah!
Package: git-restack
A git command for editing a series of commits without rebasing.git-restack is a tool that performs an interactive git rebase of a
branch without changing the commit upon which the branch is based.Free software: Apache licenseDocumentation:http://docs.openstack.org/infra/git-restack/Source:https://git.openstack.org/cgit/openstack-infra/git-restackBugs:https://storyboard.openstack.org/#!/project/838
Package: git-review
A git command for submitting branches to Gerritgit-review is a tool that helps submitting Git branches to Gerrit for
review.Free software: Apache licenseDocumentation:http://docs.opendev.org/opendev/git-reviewSource:https://opendev.org/opendev/git-reviewBugs:https://storyboard.openstack.org/#!/project/opendev/git-review
Package: git-reviewers
git-reviewersIntelligently find code reviewers.
See also,git-browse.InstallationHomebrew (preferred for MacOS)If you use Homebrew, you can install git-reviewers through thehomebrew-albertyw tap:brewinstallalbertyw/albertyw/git-reviewersManualIf you don't use Homebrew, first clone this repository to somewhere on your system
(perhaps in yourdotfilesrepository), then run<REPOSITORY_LOCATION>/install.sh.After installation, you can modify any default flags for git-reviewers
in~/.gitconfigUsageusage: reviewers.py [-h] [-v] [--verbose] [-i IGNORE] [-j JSON] [-c]

Suggest reviewers for your diff. https://github.com/albertyw/git-reviewers

optional arguments:
  -h, --help            show this help message and exit
  -v, --version         show program's version number and exit
  --verbose             verbose mode
  -i IGNORE, --ignore IGNORE
                        ignore a list of reviewers (comma separated)
  -j JSON, --json JSON  json file to read configs from, overridden by CLI
                        flags
  -c, --copy            Copy the list of reviewers to clipboard, if available
  -b BASE_BRANCH, --base-branch BASE_BRANCH
                        Compare against a base branch (default: master)Findersgit-reviewersis componsed of a set of strategies for generating lists of
reviewers, or Finders.  They return a weighted set of reviewers which is then
sorted and recommended to you.  They include:FindLogReviewers- Generate a list of reviewers based on committers to
your committed (but not merged with master) filesFindHistoricalReviewers- Generate reviewers based on the repository
committers as a wholeFindArcCommitReviewers- Generate reviewers based on arc commit messages
for files which you have modified on your branchConfigurationgit-reviewerssupports reading configuration from a configuration file
with the--jsonflag.  The configuration file accepts json with the
following fields (all fields optional):{"verbose":false,"copy":false,"ignore":["a","b","c"],"base_branch":"master"}git-reviewerswill also by default search for and load a json
configuration file at~/.git/reviewers.Developmentpythonsetup.pydevelop
pipinstall-rrequirements-test.txt
ruffcheck.
mypy.
coveragerun-munittest
coveragereport-mPublishingpipinstalltwine
pythonsetup.pysdistbdist_wheel
twineuploaddist/*Need to also updatealbertyw/homebrew-albertyw.
Package: gitreview-gpt
Let your code changes get reviewed by AI with codereview-agiGet review suggestions to changes in your git working directory or to any committed changes in your current branch against a target branch and let these suggestions get applied to your code
with an informative commit message.✨ FeaturesGet feedback and suggestions with the corresponding line numbers to your git changes in your terminalLet your current working directory get reviewed (staged and unstaged changes)Let all commits of your current branch get reviewed against any specific target branchLet AI-generated review suggestions get applied to your codeLet a commit message get generated for your current changes[!NOTE]
Review suggestions will only be applied to files without unstaged changes, so that nothing is overridden.🚀 Usagergpt review: Reviews all changes in your working directory and applies review suggestions to related files autonomously.rgpt review --readonly: Reviews all changes without applying the suggestions to the code.rgpt review --guided: User needs to confirm review process for each file. Useful if not all files should get reviewed.rgpt review --target $BRANCH: Reviews all committed changes in your current branch compared to$BRANCH.rgpt review --gpt4: Use GPT-4 model (default is GPT-3.5).rgpt commit: Generates a commit message for your staged changes.📋 RequirementsPython >= 3.8🔧 InstallationCreate your personal OpenAI Api key and add it as$OPENAI_API_KEYto your environment with:export OPENAI_API_KEY=<YOUR_API_KEY>Install withpipx:pipx install gitreview-gpt[!NOTE]
It is recommended to usepipxfor installation, nonetheless it is also possible to usepip.
Package: git-revise
git revisegit reviseis agitsubcommand to efficiently update, split, and rearrange
commits. It is heavily inspired bygit rebase, however it tries to be more
efficient and ergonomic for patch-stack oriented workflows.By default,git revisewill apply staged changes to a target commit, then
updateHEADto point at the revised history. It also supports splitting
commits and rewording commit messages.Unlikegit rebase,git reviseavoids modifying the working directory or
the index state, performing all merges in-memory and only writing them when
necessary. This allows it to be significantly faster on large codebases and
avoids unnecessarily invalidating builds.Install$pipinstall--usergit-reviseVarious people have also packagedgit revisefor platform-specific package
managers (Thanks!)macOS Homebrew$brewinstallgit-reviseFedora$dnfinstallgit-reviseDocumentationDocumentation, including usage and examples, is hosted onRead the Docs.
Package: git-ripper
Git Ripper ⚰️Downloads git repos from the web.From Russia with hate, szuki! Developed by secret KGB konstruktor buyro by red soviet communits hackers. Enjoy before you die in nuclear war...Downloading git repo from ukrainian neonazi site.Features:Asynchronous and fast.Mass git downloading.Unix-friendly for geeks.Colored output for gay people and transformers.Powered by Putin's 🇷🇺 dark energy.Use Python programming language instead peaces of shit like Go or Rust. You can easily customize it!# install$pipxinstallgit-ripper

$git-ripperhttps://<target># so...$git-ripper<urls.txt
$command|git-ripper# see help$git-ripper-hHow To Find Sensitive data# extract text from git objectsforiinoutput/target/.git/objects/*/*;dozlib-flate-uncompress<$i|strings>>/tmp/decoded# find passwords$grep-A2-B2-n-ipassword/tmp/decodedFIXMETo stop the execution, you need to press^Cseveral times.NotesGit directory structure:Git Object FormatСборка происходит автоматически при добавлении тега.
Package: gitrisk
git-risk is a command that will determine which tickets are at risk of
regressions from a range of commits. It is most useful when used after a merge
to determine which tickets were affected by the merge by searching through the
range [<merge-commit>..<least common ancestor(merge-commit)>]. In this mode, it
determines the least common ancestor of the commits included in the given merge
and reports all tickets identified in the commit messages for all commits in
between each of the merged commits and their least common ancestor.The theory is that, for a given merge commit, regressions will typically be
seen in tickets that weren’t previously merged into the main development trunk.
Tickets that have already been merged into the main development trunk, and are
tested prior to the merge in question, are at a lower risk for regressions. As
such, git-risk provides a list of all tickets that haven’t yet been tested after
the merge in question, so they can be tested to ensure lower probability of
regressions in the happy-path of the code.git-risk can also be used to report which tickets were involved (or, at least
mentioned) within any range of commits.For any of these to work, you must have a standard commit message format that
includes the issue to which a given commit relates. Extraction of the ticket
from a commit message is performed using a regular expression, so a great deal
of flexibility is available.
Package: git-rsrc
=============================git-r=============================.. contents:: **Table of Contents**What is git-r?===============git-r is a python module to manage git repositories from a distant folder.We provide an executable ``git-r`` which is a wrapper around the traditional ``git`` commandand can be called from any location to make change to a particular git repository on the machine.Requirements===============No special dependencies. Work for both python2.7 and python 3.X.Installation===============The best is to use pip::pip install git-rMake sure that the executable is in your path.Quick examples===============The general usage is very simple::git-r <command> [<options>] <repo_name>Note that ``command`` can be any git commands.Say now I have a repo at ``/some/path/repo``. First, you need to create the .git-rrc file inyour ``$HOME`` and register ``repo`` (see the example provided). git-r allows you to thatfrom the command line:::julien:workspace$ git-r add_repo /some/path/repo.git-rrc does not exist. Now created at /Users/julien/.git-rrc.This message will appear only once when the file is created.Then you can as many repo as you want. You can also overwrite location ofold repo:::julien:workspace$ git-r add_repo /some/new/path/repo+---------------------------+Repo already in the .git-rrc file!Path used is /Users/julien/Documents/Workspace_postdoc/github/s4cmbDo you want to overwrite it? [Y/n]**Example 1: Pull**Imagine I am working from a folder distant ``/some/other/path/workspace`` (but still the same machine!)and I want to pull the latest change from ``repo``:::julien:workspace$ git-r pull repoRepo: /some/path/repo<can ask password>Already up-to-date.julien:workspace$**Example 2: Changing branch**Imagine I am working from a folder distant ``/some/other/path/workspace`` (but still the same machine!)and I want to switch from the ``master`` branch to ``mybranch`` branch in ``repo``:::julien:workspace$ git-r checkout mybranch repoRepo: /some/path/repoSwitched to branch 'mybranch'Your branch is up-to-date with 'origin/mybranch'.julien:workspace$Support===============.. raw:: html<img src="https://github.com/JulienPeloton/git-r/blob/master/pics/erc.jpg" height="200px">
Package: git-runstats
git-runstatsDisplay git contribution statistics (insertions + deletions)UsageUsage: git-runstats [OPTIONS] [GITARGS]...

  Most arguments of `git log` will work as GITARGS, but do not change the
  output-format. Use -- to separate GITARGS.

Options:
  -l, --limit INTEGER  Number of commits to read
  --tty / --no-tty     Enable ttyLive-statsgitrunstatsStats forREADME.mdgitrunstatsREADME.mdDisplay helpgit-runstats--helpNon-live stats with limitgitrunstats-l1000|lessNon-live stats reversedgitrunstats-l1000|head-n-1|sort-nShow stats in branchgitrunstatsmaster..my_branchShow stats in current branchgitrunstatsmaster..Show stats from 2019gitrunstats----since=2019-01-01--until=2019-12-31Who knows most about the rust Alpine Linux packagecdaports
gitrunstatscommunity/rustInstallpipinstallgit-runstatsWhyIn comparison to shortlogrunstatsgives immediate feedback and counts changes
instead of commits. Press Ctrl-C once you have enough information. Shortlog can
also be very wrong:$>cdlinux
$>gitshortlog-s-nnet/802/|head-n1011StephenHemminger10ArnaldoCarvalhodeMelo9EricDumazet6EricW.Biederman5AlexeyDobriyan5DavidS.Miller4PaulGortmaker4DavidWard3LinusTorvalds3AdrianBunkversus$>cdlinux
$>gitrunstatsnet/802/|head-n101556LinusTorvalds931DavidWard749PatrickMcHardy104StephenHemminger98EricDumazet65PavelEmelyanov51ThomasGleixner47JohannesBerg40AlexeyDobriyan30JoePerches