Saravanan666/pypi-org huggingface dataset:
Package: gitblobts
gitblobtsgitblobtsis an experimental Python package forgit-backed time-indexed blob storage.
Even so, a lock-in of the stored files with git is avoided.
If encryption is not enabled, a lock-in of the file contents with this application is also avoided.Its goal is to ensure availability of data both locally and remotely.
It stores each blob as a file in a preexisting local and remote git repository.
Each filename contains an encoded nanosecond timestamp and format version number.Given the pull and push actions of git, collaborative use of the same remote repo is supported.
To prevent merge conflicts, there is a one-to-many mapping of timestamp to filenames.
This is accomplished by including sufficient random bytes in the filename to ensure uniqueness.Subsequent retrieval of blobs is by a time range.
At this time there is no implemented method to remove or overwrite a blob; this is by design.
From the perspective of the package, once a blob is written, it is considered read-only.
An attempt to add a blob with the same timestamp as a preexisting blob will result in a new blob.An effort has been made to keep third-party package requirements to a minimum.LinksCode:https://github.com/impredicative/gitblobts/Docs:https://gitblobts.readthedocs.io/Release:https://pypi.org/project/gitblobts/InstallationUsing Python 3.7+, install the package from PyPI:pip install -U gitblobts.Usage examplesStoragefromtypingimportOptionalimportdatetime,gitblobts,json,time,urllib.requestoptional_compression_module_name:Optional[str]=[None,'bz2','gzip','lzma'][2]optional_user_saved_encryption_key:Optional[bytes]=[None,gitblobts.generate_key()][1]store=gitblobts.Store('/path_to/preexisting_git_repo',compression=optional_compression_module_name,key=optional_user_saved_encryption_key)store.addblob('a byte encoded string'.encode())store.addblob(b'some bytes'*1000,timestamp=time.time())store.addblob(blob=json.dumps([0,1.,2.2,3]).encode(),timestamp=datetime.datetime.now(datetime.timezone.utc).timestamp())store.addblob(blob=urllib.request.urlopen('https://i.imgur.com/3GmPd7O.png').read())store.addblobs(blobs=[b'first blob',b'another blob'])store.addblobs(blobs=[b'A',b'B'],timestamps=[time.time(),time.time()])RetrievalfromtypingimportListfromgitblobtsimportBlob,Storeimporttimestore=Store('/path_to/preexisting_git_repo',compression='gzip',key=b'JVGmuw3wRntCc7dcQHJ5q1noUs62ydR0Nw8HpyllKn8=')blobs:List[Blob]=list(store.getblobs(pull=False))blobs_bytes:List[bytes]=[b.blobforbinblobs]timestamps:List[float]=[b.timestampforbinblobs]blobs2_ascending:List[Blob]=list(store.getblobs(start_time='midnight yesterday',end_time='now'))blobs2_descending:List[Blob]=list(store.getblobs(start_time='now',end_time='midnight yesterday',pull=True))blobs3_ascending:List[Blob]=list(store.getblobs(start_time=time.time()-86400,end_time=time.time(),pull=True))blobs3_descending:List[Blob]=list(store.getblobs(start_time=time.time(),end_time=time.time()-86400))
Package: gitblog
Because you’ve always wanted to blog from a command prompt and/or Python script… Right?Free software: BSD licenseDocumentation:https://gitblog.readthedocs.org.FeaturesPseudo-blogging capabilities brought to a Python shell near you!Already have a <username>.github.io page? Awesome! You can get started right away!Don’t have a <username>.github.io page? Great! You can get started right away!History0.0.1 (2015-03-15)First release on PyPI.
Package: gitblog2
Gitblog2Git + Markdown = BlogGitblog2 is a blog generator focused on speed and simplicity.Blog posts are written in Markdown and that's it.Look at it yourself: thislive exampleis solely based onthis repository.FeaturesBuild static HTML files from Markdown files. No JavaScript, no divs, no css classes.Low footprint (about 10kB compressed).Profile picture and social accounts included based on your Github profile.RSS and Atom feeds.Installationpipinstallgitblog2There's also acontainer imageavailable on docker hub.UsageFrom the command line:gitblog2https://github.com/HenriTEL/gitblog2.git--repo-subdir=example--base-url=https://example.com--no-socialFrom the library:fromgitblog2importGitBlogsource_repo="https://github.com/HenriTEL/gitblog2.git"output_dir="./public"url_base="https://example.com"withGitBlog(source_repo,repo_subdir="example")asgb:gb.write_blog(output_dir,base_url=url_base,with_social=False)From the container:dockerrun--rm-v$PWD/public:/public\-eSOURCE_REPO=https://github.com/HenriTEL/gitblog2.git\-eREPO_SUBDIR=example\-eBASE_URL=https://example.com\-eNO_SOCIAL=true\henritel/gitblog2RoadmapLow priority:If avatar already present, don't attempt to download it and include it in the blog.Add gitlab supportAdd about page (and link to it from pp) based on user bio and README.mdUse user's profile handle first and commit author only as a fallbackE2E testsDeal with code's TODOs or make issues for newcomersImprove score onhttps://pagespeed.web.dev/analysis/https-blog-henritel-com/oktd50o2sy?form_factor=desktopAdd doc for customisationChange template + accessible variablesAdd iconsChange main color themeMake a script to remove unused iconsMake a better TOC extension (remove div and classes)Make markdown renderer set loading="lazy" on img tagsUnit tests, pagespeed testRefactor lib.pyAdd contributing sectionRemove div and classes from footnotesGreat contenthttps://accessiblepalette.comhttps://modernfontstacks.com/https://anthonyhobday.com/sideprojects/saferules/https://lawsofux.com/https://developer.mozilla.org/en-US/docs/Web/HTMLhttps://developer.mozilla.org/en-US/docs/Web/CSShttps://developer.mozilla.org/en-US/docs/Web/SVGhttps://icons.getbootstrap.com/Classless stylesheets candidateshttps://github.com/kevquirk/simple.css/blob/main/simple.csshttps://github.com/yegor256/tacithttps://github.com/kognise/water.csshttps://github.com/xz/new.csshttps://github.com/edwardtufte/tufte-csshttps://github.com/programble/writhttps://github.com/oxalorg/sakurahttps://github.com/susam/spcss
Package: gitbook-dl
gitbook-dlCommand-line program to download books from gitbook.com:warning:This package is currently under developmentPurposeGet StartedInstallingThe easiest way to installgitbook-dlis viapip:pip install gitbook-dlContributingDeveloper GuideClone this repositorygit clone git@github.com:alwinw/gitbook-dl.gitInstall the development versionpip install -v -e .[<extras>](-eneeds pip >= 22.0 for pyproject.toml) orpoetry install --extras "<extras>"Make your changes and commit usingcommitizenand ensurepre-commitis activeWhen bumping version, usecz bump -ch -ccWhen ready, bump the version and runpoetry build -v. If deploying, runpoetry publish --build -v
Package: git-branch-cleaner
GitBranchCleanerGitBranchCleaner is a tool to clean up git repositories.
This tool allows users to delete branches from a local git repository that are not present in the remote repository.
This tool is useful when you have a lot of branches in your local repository, and you want to clean up your local repository.
This tool is not intended to delete remote branches as it is not safe to do so and one might need to do a lot of manual work to recover from such a mistake.InstallationTo use the tool first install using pip or git clone the repository and run the setup.py file:pip install git-branch-cleanerorgit clone https://github.com/Vishnu-Naik/git-branch-cleaner
cd git-branch-cleaner
python setup.py installUsageThis tool can be used as a command line tool or as a library. Let's see those two options in detail.Command Line ToolThe command line tool can be used to delete branches from a local repository that are not present in the remote repository.
The command line tool can be used as follows:repo_cleaner --repo <path to git repository>--repo is the optional flag to the command. If this flag is not provided, the current working directory is assumed to be the git repository.
The tool will show the branches that are on local and remote. As shown below:=================================================
List of remote branches:
main
develop
feature/branch1
=================================================
List of local branches:
main
develop
feature/branch1
feature/branch2
=================================================The tool will ask the user if they want to delete the branches that are not present in the remote repository.
If the user enters anything else other than Y or y, the tool will end its execution. Else it will display the branches that are not present in the remote repository one after the other which are
going to be deleted and ask for confirmation before deleting each of the branches.LibraryTo use this tool as a library, you can import the GitRepoCleaner class from the git_repo_cleaner module and use it as follows:from cleaner import git_repo_cleanerfromcleanerimportgit_repo_cleanergit_repo_cleaner.main('/home/username/git_repos/dummy_project')For finer functionality, you can use the GitRepoCleaner class directly as follows:fromcleaner.git_repo_cleanerimport*local_branches,remote_branches=GitRepoCleaner.get_local_and_remote_branches()print(local_branches)
Package: git-branchdescriptions
This is a small tool to view and set git branch descriptions.UsageWhen invoked without –set git-branchdescriptions shows the current local
branches with following descriptions. The -a, -v, and -r parameters control
which refs are shown.Assuming git-branchdescriptions is on your PATH git will pick it up and it will
be accessible as git-branchdescriptions.Tip: git config –global alias.bd branchdescriptionsgit-branchdescriptions assumes current branch if branch is not provided.
Use –set to set the branch’s description.Example: git branchdescriptions –set This branch addresses issue foo.$ git-branchdescriptions –help
Use –set to set the branch’s description.
Example: git branchdescriptions –set This branch addresses issue foo.Options:-v,--verbosityShow sha1 and commit subject lines-r,--remotesList remote branches-a,--allList both local and remote branches-s,--setUse to set the branch’s description-bBRANCH,--branch=BRANCHWhich branch to operate on. Optional, assumes current
branch--no-colorSkip color formatting (for dumb terminals)--versionshow program’s version number and exit-h,--helpshow this help message and exitThanksThanks to Ben Spaulding for expressing this common need.
Package: gitbrancher
BrancherBrancher is a tool inspired by git flow that is more flexible in how it handles branching. It allows any configuration of branches and simply makes it easier to see which commits are in what branch, as well as advancing changes between branches. A typical branch layout may be like this:┌─────────────────┐   ┌─────────────────┐   ┌─────────────────┐   ┌─────────────────┐
│     develop     ├──▶│     staging     ├──▶│      beta       ├──▶│     master*     │
└─────────────────┘   └─────────────────┘   └─────────────────┘   └─────────────────┘

                                                                 *production branchNote: Brancher can handle other configurations, assuming there's one final "production" branch and any number of sequential pre-production branches to the left of it.Installationpip3installgitbrancherAvailable CommandsCommands:overview (o): Prints an overview of branches with outstanding commitsforward (f): Fast forwards commits into branchbackfix (b): Applies changes on more advanced branches to current onecompare (c): Shows commits in one branch but not anotherinit: Initialize repoAdd-hto any command for usage details.UsageInitializationLet's start with an example of an empty repo.Next, initialize Brancher. Brancher will store your branching model in your repository's local configuration.Advancing commitsNow let's start some development work.That looks good, so we'll advance that commit tostaging, the next branch afterdevelop.Whilestagingis having some Q/A work done, we'll continue development indevelop:Commit overviewWith pending commits indevelopandstaging, let's get an overview of what commits exist where.Backfilling hotfixesWith development work ongoing and Q/A happening onstaging, let's make an urgent bugfix to production. As you can see, once that commit has been made, it only exists on themasterbranch, not other branches.We want to bring that hotfix back intodevelop. After checking outdevelop, we'll apply the hotfix to develop too:An overview confirms that the backfilled changes have been applied todevelop, but notbetaorstaging:We can remedy this by applying the hotfix to those environments, also:
Package: gitbrew
Gitbrew: Your LLM-Powered GitHub Companion 🚀✨Welcome to Gitbrew, the innovative tool that harnesses the power of language models to streamline your GitHub experience. Gitbrew is designed to assist developers in managing repositories, handling issues, reviewing pull requests, and generating beautiful READMEs with ease.Table of ContentsIntroductionFeaturesExamplesInstallationUsageContributingIntroduction👋Gitbrew is a command-line application that simplifies your GitHub workflow. It uses advanced language models to interpret natural language commands, generate git commands, handle GitHub issues, and create comprehensive READMEs for your projects. Gitbrew is your go-to utility for a more efficient and intelligent way to interact with GitHub.Features🌟Command Handling: Process user input to generate and execute git commands safely with user confirmation.Issue Management: Manage GitHub issues by listing, creating, finding duplicates, and identifying similar issues.Pull Request Review: Automate the review of GitHub pull requests with insightful comments and suggestions.Readme Generation: Generate visually appealing READMEs with structured content and visual elements.Interactive Shell Interface: Use Gitbrew's interactive CLI to perform a variety of GitHub-related tasks.Examples🌟Readme generation? What would you like to do?  Generate a Readme
? Enter the repository url:   https://github.com/<username>/<repositoryname>
100%|██████████████████████████████████████████████████████████████| 2/2 [00:47<00:00, 23.85s/it]
? What would you like to save the file as?   Readme.mdPull Request Review? What would you like to do?  Review a pull request
Enter the pull request URL: https://github.com/<username>/<repositoryname>/pull/<number>Natural language interface for gitInstallation🛠️pipinstallgitbrewUsage💻Rungitbrewin your Terminal:gitbrewThis will launch the Gitbrew interactive shell.Provide the API keys for GitHub, openai, pinecone etcStart using Gitbrew!Contributing🤝🌐Contributions and feature requests are welcome!Issues and Feature RequestsPlease use theissue trackerto report any bugs or file feature requests.DevelopmentFork and clone the repository.Make your changes and commit them with a descriptive commit message.Install pre-commit hooks by runningpre-commit install.Push your changes to your fork and submit a pull request.Thank you for checking out Gitbrew! 🚀✨This readme was generated by gitbrew! 🤖
Package: git-browse
Git BrowseOpen git repositories, commits, directories, and files in the browser. See also,git-reviewers.This script can be added as a gitconfig alias to easily browse
repositories on Git hosting services (e.g. github). It is built to modelarcanist's browsecommand. It is specifically designed to have no
dependencies so it should be easily installable and very portable.Git Browse supports opening git repositories, commits, directories, and files:BitbucketGithubGitlabGoDocsPhabricatorSourcegraphInstallationHomeBrew (preferred for MacOS)If you use Homebrew, you can install git-browse through thehomebrew-albertyw tap:brewinstallalbertyw/albertyw/git-browseManualIf you don't use Homebrew, first clone this repository to somewhere on
your system (perhaps in yourdotfilesrepository), then run<REPOSITORY_LOCATION>/install.sh.Usage$ git browse -h
'browse' is aliased to '!~/.dotfiles/scripts/git/git-browse/git_browse/browse.py --path=${GIT_PREFIX:-./}'
usage: browse.py [-h] [--path PATH] [-d] [-c] [-s] [-g] [-v] [target]

Open repositories, directories, and files in the browser. https://github.com/albertyw/git-browse

positional arguments:
  target             file, directory, git hash, or git branch you wish to browse

optional arguments:
  -h, --help         show this help message and exit
  --path PATH        relative path to the current git repository
  -d, --dry-run      Do not open the url in the brower, and only print to stdout
  -c, --copy         Copy url to clipboard, if available
  -s, --sourcegraph  Open objects in sourcegraph
  -g, --godocs       Open objects in godocs
  -v, --version      show program's version number and exitExamplesCommandOpensgit browsehttps://github.com/albertyw/git-browsegit browse README.mdhttps://github.com/albertyw/git-browse/blob/master/README.mdgit browse git_browsehttps://github.com/albertyw/git-browse/tree/master/git_browse/git browse v1.1.1https://github.com/albertyw/git-browse/commit/80b219dee0aaa86b378993cbf88511126b813c5fgit browse --sourcegraphhttps://sourcegraph.com/github.com/albertyw/git-browsegit browse --godocshttps://godocs.io/github.com/albertyw/git-browsegit browsefor Bitbuckethttps://bitbucket.org/albertyw/asdfgit browsefor Gitlabhttps://gitlab.com/albertyw/asdfgit browsefor Uber Phabricatorhttps://code.uberinternal.com/diffusion/rASDF/repository/master/Related Projectsgit-brwshub browsegit openopen-browser-github.vimDevelopmentpipinstall-rrequirements-test.txt
ruffcheck.
mypy.--strict--ignore-missing-imports
coveragerun-munittest
coveragereportPublishingUpdate changelog and__version__variable with a semantic versionCommit changes, create a version tag, and push bothUpdatealbertyw/homebrew-albertyw
Package: gitbrowserinteract
Automatically get and set GitHub & GitLab personal access tokens/ssh deploy keysHorrible boiler plate to automate 2 tasks in GitHub, and 1 in GitLab:Set an ssh deploy key in your GitHub account, such that you can push the
GitLab build status icons to a specific (hardcoded) repository in your GitHub
account.Generate and get/export a GitHub personal access token, such that you can
set the commit statuses of your GitHub commits. (This is used to display the
GitLab CI results in your GitHub repository pull requests).Get a GitLab runner token in your own GitLab server. (I did not yet find
out how to do that through docker itself using bash only).Usage: do onceDownload/clone this repository.If you don't have pip: open Anaconda prompt and browse to the directory of
this readme:cd /home/<your path to the repository folder>/To use this package, first make a new conda environment and activate (it
this automatically installs everything you need).conda env create --file environment.ymlUsage: do every time you start AnacondaActivate the conda environment you created:conda activate get_gitlab_generation_tokenUsage: do every run (Set ssh-deploy key in GitHub for pushing build status icons)python -m gitbrowserinteract --d --ssh <the public ssh key that was created>The--dindicates you are setting the deploy ssh key in GitHub.The-ssh <some ssh key>is used to absorb/take in the public ssh key that
you want to add to github.Usage: do every runCreate and get GitHub personal access token for setting commit build statusespython -m gitbrowserinteract -hubcpatThe--hubcpatindicates you are letting GitHub create a personal access
token and storing it.More complete:cd$repo_name&&condadeactivate&&condaactivateget_gitlab_generation_token\&&python-mgitbrowserinteract--hubcpat-hu$github_username-hp$github_pwdcd$repo_name&&condadeactivate&&condaactivateget_gitlab_generation_token\&&python-mgitbrowserinteract--d-hu$github_username-hp$github_pwdUsage: do every run (Create and get GitLab runnertoken)python -m gitbrowserinteract --gor, to run it from bash as a pip package:python-mgitbrowserinteract.__main__--glrThe--gindicates you are letting GitLab generate a personal access token
and storing it.TestingTesting is as simple as running the following command in the root directory
of this repository in Anaconda prompt:python -m pytestfrom the root directory of this project.UpdatingBuild the pip package with:pip install --upgrade pip setuptools wheel
# pip install "keyring>=23.11"
pip install twineInstall the pip package locally with:pip install -e .Upload the pip package to the world with:rm -r dist
rm -r build
python3 setup.py sdist bdist_wheel
python -m twine upload dist/\*
Package: gitbuglink
gitbuglinkThe stupid commit-bug traceability linker for the stupid content trackerThe aim for gitbuglink is to be as stupid as possible. Other
multi-layered approaches exist (e.g.,
[MLink](http://home.engineering.iastate.edu/~anhnt/Research/MLink/index.php)),
but gitbuglink is not meant to replace those. At the moment, gitbuglink
will only use a series of regular expressions to determine the link.Initial support for link finding will work for Bugzilla bug
repositories. Additional repository types (e.g., JIRA, github issues)
should be able to be easily added (it may find a few accidentally).If you find a commit message that was not linked, please send a pull
request with the appropriate test case. Please include a project repo
url and commit id in the comment of the test.UsageFor input, gitbuglink accepts a file path to a local git repository. It
uses thedulwichPython module to access the repository log. Output is
a couple CSV files:links.csv– a CSV of(commit id, bug id)for confirmed linkshumans.csv– a CSV of(commit id, bug id_1, bug id_2, …, bug
id_n)for links that require some form of human knowledge to
establish the correct link(s). The tool makes no assumptions about a
commit when it finds multiple links. You should investigate the
commit message yourself to confirm or correct the output.But my subject system uses CVS/Subversion/…I don’t care. Send a pull request when you get it working.Search for an (un)official project git mirror of the repository[Use a conversion tool](http://lmgtfy.com/?q=cvs+to+git):[cvs2git](http://cvs2svn.tigris.org/cvs2git.html)[svn2git](https://github.com/nirvdrum/svn2git)(Send pull request for links to other tools you can recommend)
Package: git-build-branch
Utility tool for building Git branches by merging multiple other branches together.Free software: BSD licenseFor guidelines on contributing to the project please read theCONTRIBUTINGdocumentation.DocumentationIn some cases it may be desirable to have full control over what code is deployed. This can
be accomplished by creating a YAML configuration file to describe what should be included in your branch.The format of the file is as follows:trunk:mastername:autostaging# name of the branch to buildbranches:# list of branches to merge into final branch-feature1-feature2-forkowner:feature3# branch from fork of repositorysubmodules:submodules/module1:branches:-feature1-forkowner:feature2# branch from fork of repositorysubmodules/module2:trunk:developbranches:-feature2To add some safety around this file you should use thesafe-commit-filesutility:safe-commit-files--push/path/to/branch_config.ymlBuilding the branchThis configuration file can be used to build a deploy branch:gitcheckoutmastergit-build-branchpath/to/branch_config.ymlConflict ResolutionFirst, determine where the conflict lies.a). branchfooconflicts withmastergitcheckout-bfooorigin/foogitpulloriginmaster# try to resolve conflictgitpushoriginfoob). branchfooconflicts with branchbarYou can’t just merge foo into bar or vice versa, otherwise the PR
for foo will contain commits from bar.  Instead make a third,
conflict-resolution branch:gitcheckout-bfoo+bar--no-trackorigin/foogitpulloriginbar# try to resolve conflictgitpushoriginfoo+barNow add the branchfoo+bartobranch_config.ymland move branches foo and
bar to right below it.Later on branch B gets merged into master and removed frombranch_config.yml.Perhaps the person who removes it also notices the A+B and does the
following. Otherwise anyone who comes along and sees A+B but not both
branches can feel free to assume the following need to be done.Merge A+B into A. Since B is now gone, you want to merge the
resolution into A, otherwise A will conflict with master.Remove A+B frombranch_config.yml. It’s no longer necessary since it’s
now a subset of A.If you are unsure of how to resolve a conflict, notify the branch owner.