Saravanan666/pypi-org huggingface dataset:
Package: gitbuilding
What is GitBuildingGitBuilding is a program for documenting hardware designs. It's primary focus is on high-quality, up-to-date assembly instructions. GitBuilding gives you the freedom to write instructions in the form and structure that you want using markdown. It uses extra metadata to track component usage, and generate bills of materials. Independent, clear, and consistent documentation can be generated for variations of the same design without specifying the same information multiple times.In GitBuilding you are able to:Write the instructions as you go along in markdownTag links in the code with meta-data to show if they are steps in the build or parts that are neededAutomatically generate bills of materialsCreate templates for instructions that render differently for different configurations of a design3D preview of manufacturing filesDefine reusable libraries of componentsExport to HTML, Markdown, or PDF (experimental)How to install GitBuildingTo install (for Python 3.7+)pip install gitbuilding[gui]If you don't want to use the stand-alone GUI, you can avoid installing PyQT withpip install gitbuilding[gui]More details are available on the website.Running GitbuildingTo run the stand-alone GitBuilding GUI run:gitbuilding-guior to view the same interface in a browser rungitbuilding webappthen navigate tolocalhost:6178in your browser.From this GUI you can open or create new projects. The GUI will launch a live editor in a browser for previewing and editing your documentation.More details are available on the website.Asking for helpYou are welcome to ask for help in the issue tracker. You can also talk to us onour area of the GOSH forumor onGitter(though we may not be too responsive due to Matrix notification issues!)Installing from sourceIf you wish to contribute to development of GitBuilding you can clone the project from GitLab. You will need to install the python package in development mode and build the javascript editor from source.To do so please see thecontribution pageand thedeveloper installation instructions.Syntax for documentationThe syntax for documentation is in a format we call BuildUp.More details are available on the website.
Package: git-cachecow
Caches git repositories locally. Every time a build happens, it uses local
caches for pulling. Submodules especially, which are harder to intercept
for caching.Will also inflate submodules recursively.With 8 submodules, a total of 150MB of data to clone:Before caching:13.79s user 6.36s system 18% cpu 1:49.45 totalAfter caching:2.12s user 2.07s system 25% cpu 16.310 totalCached repositories are stored in~/.git-cowby default. You can override
this by setting$GIT_COW.# InstallationEither:with pypi:sudo pip install git-cachecowOr:Clone git-cachecow and add the directory to your$PATH.# UsageHow to clone a repository with submodules:git scclone git://github.com/grahamc/git-multi.git## git-cclonegit cclone repo_uri [clone_to [hash]]## git-submodule-describeOutputs submodule data into parsable format`git://github.com/nationalfield/symfony.gitlib/vendor/symfony  aec67b5e7ba148c79b884b86988e42f9f9483bcd git@github.com:nationalfield/pheanstalk.git lib/vendor/pheanstalk   5b38924730b70ea720f760369899398479e2ea13 git@github.com:nationalfield/tinymce.git    web/js/tiny_mce 0c3da0cc9e33df0f2b82f70bf7e24405de216bee `## git-submodule-ccloneClones all the submodules recursively at their defined location and hashes.[![Build Status](https://secure.travis-ci.org/grahamc/git-cachecow.png)](http://travis-ci.org/grahamc/git-cachecow)
Package: gitcal
GitcalA python script to visualize when git commits were made in a repository in a calendar-like format.ExamplesDisplay the number of commits in 2 hour blocks in 12 columns. A block with at least 4 commits is colored in green:An example of displaying two tables side-by-side, one with a border and different date range:Compare commits with other members of a collaborative project:InstallationpipinstallgitcalDisplaying Multiple Tablesgitcal uses the-T/--tableargument to display multiple tables.
A table is created based on the arguments on each side of-T, where the command below is used to create multiple tables:gitcal-T-n"My Commits"--num--no-label-f"<my username>"-t4-T-n"Partner 1"-f"<partner 1>"-f"<also partner 1>"#     ^   ^_______________________table 2________________________^    ^______________________table 3______________________^#     |# table 1A sample result of the above command (below describes each table):Table 1Since there are no arguments to the left of the first-T, the default table with all the daily commits is displayed per week.Table 2To the right side of the first-T, we:set the table name with-nturn on commit counts with--num(underlines are used to distinguish number entries since there is no spacing on borderless tables)turn off labels with--no-labelsince the labels from the first table can be used insteadfilter for one user with-fset the color threshold-tto 4 commitsTable 3The second-Tseparates the second and third table options.
Note how table 3 only explicitly sets the table name and user filter, but the settings from the second table are carried over to the third table as well.
Most, but not all, settings are carried over between tables so they do not have to be repeated.
Package: gitcalendar
GitCalendarTool that generates an ICS file from issues, milestones and iterations, of one or more GitLab projects.
Only events with a due date are considered.SetupThe script requires Python >= 3.6 and uses the librariesics(Apache License v2.0) andpython-gitlab(LGPL v3.0).
You can install it fromPyPiwith the following command:pipinstallgitcalendarUsageThere are two options of running the script:Run it with a configRenamegitlab-config.ini.exampletogitlab-config.iniand fit to your needsMake sure that all wanted variables are givenMake sure to declare your private token, a valid project or group id, and the path where your calendar files should be generated at.Once this is done, you can run the script as follows:gitcalendar--config<PATHOFYOURCONFIG>Run it with all the options you needWarning! Please consider using the prior option for not leaking any access tokensHere, there's a need to declare the url of the gitlab instance, your private token, and at least one project or group id.gitcalendar-u<URL>-t<PRIVATETOKEN>-p<LISTOFPROJECTIDS>-g<LISTOFGROUPIDS>For more options please use:gitcalendar-hDevelopmentAfter you cloned the repository and changed into it, you can
perform the following actions.SetupInstall with pip as follows:pipinstall-e.[develop]Package BuildYou can build a source package with the following command:pythonsetup.pysdistYou can build a wheel with the following command:pythonsetup.pybdistChangesPlease see theCHANGELOG.mdfor notable changes.ContributingPlease see theCONTRIBUTING.mdif you want to contribute.ContributorsPlease seeCONTRIBUTORS.mdfor further information about the contributors.LicensePlease seeLICENSE.mdfor further information about how the content is licensed.
Package: gitcal-wilgysef
GitcalA python script to visualize when git commits were made in a repository in a calendar-like format.ExamplesDisplay the number of commits in 2 hour blocks in 12 columns. A block with at least 4 commits is colored in green:An example of displaying two tables side-by-side, one with a border and different date range:Compare commits with other members of a collaborative project:InstallationClone this repository and place somewhere like~/.local/bin/gitcal-pyCreate a symlink from~/.local/bin/gitcal-py/gitcal.pyto~/.local/bin/gitcalDisplaying Multiple tablesgitcal uses the-T/--tableargument to display multiple tables.
A table is created based on the arguments on each side of-T, where the command below is used to create multiple tables:gitcal-T-n"My Commits"--num--no-label-f"<my username>"-t4-T-n"Partner 1"-f"<partner 1>"-f"<also partner 1>"#     ^   ^_______________________table 2________________________^    ^______________________table 3______________________^#     |# table 1A sample result of the above command (below describes each table):Table 1Since there are no arguments to the left of the first-T, the default table with all the daily commits is displayed per week.Table 2To the right side of the first-T, we:set the table name with-nturn on commit counts with--num(underlines are used to distinguish number entries since there is no spacing on borderless tables)turn off labels with--no-labelsince the labels from the first table can be used insteadfilter for one user with-fset the color threshold-tto 4 commitsTable 3The second-Tseparates the second and third table options.
Note how table 3 only explicitly sets the table name and user filter, but the settings from the second table are carried over to the third table as well.
Most, but not all, settings are carried over between tables so they do not have to be repeated.
Package: gitcc
GitCC checks commit messages for certain rules.To use as a GitHub Actions refer to thecommit-check-pythonsection inexample.To expand gitcc to apply your own rules inherit fromgitcc.commit_validator.Validator.
If you use the--validator-fileargument the Validator class in that file must be namedValidator.Shipped validatorsgitcc.validation.SimpleTagFormat:[<tag>] <Good Description>(e.g.[ci] Fix testing suite installation)gitcc [-h] [-v] [--validator | --validator-file] {message, git-hook, commit, history, branch}–validator<Python import path>Python import path to Validator class.
Example:--validatorgitcc.validation.SimpleTag–validator-file<file path>Path to file with Validator..
Example:--validator-filemy_validator.pymessage<text>check the given messagetexttext to checkgit-hook[–force] <action> <hooks> [<hooks> …] <repository>install or uninstall a git hook<action>Install or uninstall. [install, uninstall]<hooks>Choose available hooks. [message]<repository>path to the repository[options]–forceForce install or uninstall, this might override existing files!commit<repository>check current commit<repository>path to the repositoryhistory[–sha <SHA>] [–verbose] <repository>check the current branch history<repository>path to the repository[options]–sha<SHA>check until this commit (exclusive)–verboseprint correct commits toobranch[–verbose] <target> <repository>check the current branch with an other branch common ancestor. Is the same as gitcc history with git merge-base <source> <target><target>target branch<repository>path to the repository[options]–verboseprint correct commits too-h,–helpshow this help message and exit-v,–versionshow program’s version number and exitExamplesgitcc--validatorgitcc.validation.SimpleTagmessage"Is this a valid message?"Webhttps://github.com/IceflowRE/gitccCreditsDeveloperIceflower Siceflower@gmx.deThird PartyGitPythonMichael Trier and contributorshttps://github.com/gitpython-developers/GitPythonBSD-3-ClauseLicenseCopyright 2021-present Iceflower S (iceflower@gmx.de)Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Package: git-cd
git-cdA terminal tool for easy navigation to local git repository. It let you change to a repository directory easily.Table of contentInstallationInstall with pipUsageChange DirectoryIndexing Local RepositoriesUpdate Local Repository IndexAutocompletionDependenciesLicenceInstallationInstall with pip$pip3installgit-cdUsageTypegitcdorgitcd -hwill show you the command help page$ gitcd
Usage: gitcd [OPTIONS] [REPO]

  gitcd [your-repo-name]

  Terminal tool for easy navigation to local git repository

  For more detail: please visit https://github.com/Doma1204/gitcd

Options:
  -i, --index             index all the local repo
  -u, --update            update the local repo index
  -p, --path PATH         only find local repo under this path
  -a, --autocomplete      activate shell autocompletion
  -s, --shell [bash|zsh]  specify the shell
  -h, --help              Show this message and exit.Change Directory$gitcd[repo-name]It changes the current directory to the corresponding local repository. PressTabto autocomplete the repository name if needed(activateautocompletionis required)Indexing Local RepositoriesBefore usinggitcdto change directory, you needs to first index you local repositories. Use the commmand below to start indexing.$gitcd-iThe default root directory is home directory(~/). It starts finding local repositories recursively from the root directory. You can change the root directory by using-p.$gitcd-i-p[root-path]Update Local Repository IndexIf some of the repositories have been deleted, the old index will still contain those invalid repositories directory, and errors occur when you attemps to cd into deleted repositories. Thus, you needs to update the local repository index by the following command. It deletes all invalid repositories.$gitcd-uAutocompletionLimited byClick, autocompletion only supportbashandzshshell. To activate autocompletion, use the command below:$gitcd-aIn normal cases, it detects the current shell and activate the autocompletion of that shell, but you can specify the shell that you wants to activate by using-s.$gitcd-a-s[bashorzsh]To actiavte autocompletion manually, you needs to add the following line to you.bashrc(bash) or.zshrc(zsh).Forbash:eval "$(_GITCD_COMPLETE=source gitcd)"Forzsh:eval "$(_GITCD_COMPLETE=source_zsh gitcd)"DependenciesThe tool is built on top ofClick.LicenceMIT Licence
Package: git-chainsaw
ChainsawA lightweight wrapper around git subtrees that lets you work with many subtrees at onceInstallationpipinstallgit-chainsawDependenciesgit v1.7.11 or abovemake sure thegitcommand is recognized wherever you plan to run thispython3 + pipUsageExample chainsaw.json[{"prefix":"bingo","remote":"https://github.com/nasa/bingo.git","branch":"master"},{"prefix":"trick","remote":"https://github.com/nasa/trick.git","branch":"master"}]Adding subtrees:# From a predefined chainsaw.json filechainsawadd--all[--squash]# From scratch (Subtrees will be added to chainsaw.json)chainsawaddbingohttps://github.com/nasa/bingo.gitmaster[--squash]Updating subtrees:# Pull specific subtrees onlychainsawpullbingotrick[etc.][--squash]# Pull changes from all subtreeschainsawpull--all[--squash]Updating subtree remotes:# Push changes for specific subtrees onlychainsawpushbingotrick[etc.]# Push changes for all subtreeschainsawpush--allList subtrees:# Print the prefix of each subtree found by git logchainsawls# Graph subtree historychainsawgraph
Package: gitchart
GitchartGitchart is a Python script to build charts from a Git repository.It can build following charts, as SVG or PNG:authors, processed tickets by author (pie charts)commits by hour of day, day, day of week, month of year, year, year/month (bar charts)commits by hour of week (dot chart)files by type (pie chart)RequirementsGitchart requires:Python ≥ 3.6Pygal(pip install pygal)Optional dependencies:cairosvg, to generate PNG filesInstallYou can install Gitchart with this command from the source repository:$ python setup.py installUsageSee output of command:$ gitchart --helpExamplesGenerate pie chart with authors:$ gitchart --title "Git authors on project X" --repo /path/to/gitrepo/ authors authors.svgGenerate bar chart with commits by year using dark style:$ gitchart --style gitchart_dark --repo /path/to/gitrepo/ commits_year commits_year.svgGenerate bar chart with commits by version (git tag):$ cd /path/to/gitrepo/
$ git tag | gitchart commits_version /tmp/commits_version.svgDemoGitchart is used to build statistics for WeeChat:https://weechat.org/dev/stats/CopyrightCopyright © 2013-2021Sébastien HelleuThis program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 3 of the License, or
(at your option) any later version.This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.You should have received a copy of the GNU General Public License
along with this program.  If not, seehttps://www.gnu.org/licenses/.
Package: gitcheck
If you working in multiples projects, you want can be analyzed in a
single pass of the changes in your projects. gitcheck is script who scan
recursive directory to find a git directory and analyse all
modifications.Installationpip install git+git://github.com/badele/gitcheck.gitExamples utilizationsSimple versionIn simple version, it show for each repositories if you have
modification not committed and or commits not pushed.>garchdeps.pyGitcheck simpleVerbose versionSubstantially identical to the previous version, in bonus, it print who
files modified and commits not pushed>garchdeps.py-vGitcheck verboseOptions-v, --verbose                     Show files & commits
-r, --remote                      also check with the remote
-b, --bell                        bell on action needed
-w <sec>, --watch <sec>           after displaying, wait <sec> and run again
-i <re>, --ignore-branch <re>     ignore branches matching the regex <re>
-d <dir>, --dir                   Search <dir> for repositoriesFrench version is available herehttp://bruno.adele.im/projets/gitcheck/
Package: gitchecker
Python GIT tool to check pending changes and get last commit infogitchecker.check_status_and_get_commit_info()checks if there is
any pending changes in GIT repository status and returns the last commit info:sha (string): commit SHA (7 digits length)author (string): author nameauthored_datetime (datetime): author datetimecommitter (string): committer namecommitted_datetime (datetime): committer datetimeBy default it raises anExceptionif there are any pending changes but
it can be configured to only show a warning instead.RequirementsPython 3.5 or newerGit 1.7.0 or newer, becausegitpython dependencyInstallpip install gitcheckerDemo Usageimportgitcheckercommit_info=\gitchecker.check_status_and_get_commit_info(repo_path="",warning_instead_of_error=False,ignore_untracked_files=False,ignore_files_regex=None,logger=None)print("commit",commit_info)The displayed values of the parameters are the default ones.If aloggeris provided, it will be used only if it has anerror()orwarning()method. The required method depends on the value ofwarning_instead_of_error. If nologgerprovided or no proper
log function exists inlogger,print()will be used instead.Ignoring untracked files (ignore_untracked_files=True) or
Ignoring by regex (ignore_files_regex="regex") will ignore them completely,
not raising errors and not showing warnings.TestingThe GIT status must be clean to run functional test.python setup.py testTo run only unit tests, use:python -m pytest --pep8 --cov=gitchecker --cov-report=term-missing --cov-report=html -vv -x -k unit
Package: git-check-rebase
Installationpip install git-check-rebaseDescriptiongit-check-rebaseis an utility for different kinds of git branch rebasing control. git-check-rebase compares several git commit ranges and produce a comparison table, where columns corresponds to specified ranges (and there are some additional helping columns).The last range (the rightmost in the command line) producesthe sequence. All rows of the resulting table correspond to comments fromthe sequenceand the column corresponding to the sequence is a kind ofgit log--oneline--reverse.For each commit of the sequencegit-check-rebasesearches for corresponding commit in other ranges and fills corresponding cells in other range columns.Thengit-check-rebasecompares the commits in the each line and mark equal commits by green color. There is also a possibility to compare commits in–interactivemode and mark them as checked. In this case leftmost commit in a row is green and the equal (checked by hand) commit is yellow.Short example:Here first commit is equal in bothv1andv2of thefeaturebranch, second commit is markedokduring–interactivesession, third commit is not checked (and not equal) and the last one is absent inv1, so it’s “new”.Use casesWhengit-check-rebasecan help?Check difference between versions of upstream seriesCheck backported seriesCheck status of rebasing a downstream branch to a new upstream releaseCheck upstreaming status of commits in downstream branchDocumentationFull documentation ishere
Package: git-cherry-pick-helper
git-cherry-pick-helperThe tool aims to help with chaotic git workflows.It provides a small shell with tab completion.The ProblemWorking on feature branches is good practice and should be done. However, I
often end up using a production branch that has diverged from upstream.  I do
merge some of my feature branches.  I also commit directly to this branch.
Then I need to cherry-pick back onto the feature branches.When I then later merge the upstream branch, git does not remove my
cherry-picked commit.git logdoes not help with identifying which commits
might still be applicable for upstream.git-cherry-pick-helper shows what commits are only in the current branch and not upstream.It allows to also exclude additional branches, which you might have pull
requests open. You can also blacklist commits that are not suitable for
upstream.  It excludes commits that are cherry-picked. If the commit is not
cleanly applied and modified, it still shows the commit, and can tell you how
similar they are.Example workflow$ cd path/to/repo # or worktree
$ git stash # make sure this is in a clean state to avoid issues; optional
$ git-cherry-pick-helper
# Set which branch we want to take commits from
gcph> source mydevbranch
# We want to add those commits to a clean upstream branch
gcph> onto origin/next
# Ignore all commits that are already in feature branches
gcph> ignore origin/my-pr1 feature2
# Look what commits we might want to add print that
gcph> update
# If there is something we need to add to a new branch we can do this with
gcph> new my-new-feature
# Select feature branches by the above printed id
gcph> add my-new-feature 1 4 7
# Print the overview again and see what commits we have selected for inclusion
gcph> print
# If we are happy we can apply the change set
gcph> runDifferent commands can be put in the same line, separted by;- this makes the history even more useful:gcph> source mydevbranch ; onto origin/next ; ignore origin/my-pr1 feature2 ; updateAll commandssource <branch>set the source branch from which to cherry-pick commits.onto <branch>set the branch onto which to add commits.ignore_branch <branch> [<branch> ...]set the branch(es) of which all commits are excluded,
e.g. commits that are already cherry-picked.update [quiet]Update what commits are available.printPrint the current state.blacklist_commits <commit> [<commit> ...]Set commits to be ignored. Note
that the commits will be permanently blacklisted. This can be undone by
modifying~/.gcph_blacklist.add <new-branch> <commit-id> [<commit-id> ...]Add commits to a new
branch.delete <new-branch>Delete a previous created branch.info <commit-id> [<commit-id> ...]Show what commits are similar and how
similar they are.show <commit-id> [<commit-id> ...]Show the commit, similar togit show.runExecute the changes and create new branches.exitExit without commiting any changes.