Saravanan666/pypi-org huggingface dataset:
Package: gitea-auto-update
Gitea Auto UpdateScript for an automatic update of gitea. Should be run locally on the gitea server. Has options for updating via new binary file or build from source.Want to update more?If you want to update Gitea and other software (like Drone, Caddy, Podman, Python, Zitadel and Kanboard), you should check outAutoupdate.This new tool of mine was built as a single binary with a config file and tested on multiple Linux systems.ProcedureGet Gitea Version from the Gitea CLI and if that fails from the Gitea APIGet latest Release via GitHub APICheck if there is a newer VersionIf there is a newer Version:If binary file was selected:Download new versionCheck sha256Overwrite old versionIf build from source is active:Checkout new release branchBuild binaryOverwrite old binaryGeneral InformationLicense: GNU General Public LicenseAuthor: Christoph Daniel Miksche (m5e.de)Uses python version 3DependenciesEnsurepip3,setuptools,xz-utilsandwheeldependencies are installed on the system you are running this script in. (Most Linux OS like Ubuntu or Debian come with these pre-installed)InstallationCreate a settings.ini file on your system. Example:[Gitea]
site=https://your-gitea-instance.com/api/v1/version
apiUrl=https://api.github.com/repos/go-gitea/gitea/releases/latest
system=linux-amd64
file=/usr/local/bin/gitea
tmpDir=/tmp/
buildFromSource=
sourceDir=
logFile=update.logUse the following command to install gitea-auto-update.sudo pip3 install gitea-auto-updateEnter the commandgitea-auto-update --settings=/path/to/settings.iniin your commandline.If you want to schedule your updates, edit your /etc/crontab file.TutorialsEnglish:http://blog.m5e.de/gitea/update/upgrade/bash/script/2018/11/26/gitea-auto-update-script.htmlGerman:https://blog.wronnay.net/automatische-gitea-updates/DevelopmentThe following instructions help you for developing.Check out theContribution Guidelines.Clone this git repoInstall pipenv:pip install pipenvInstall all dependencies:pipenv installInstall git pre-commit hooks (for pylint and gitlint) withpre-commit installYou can run the tests withpython -m unittestAfter pushing, you should check the build status which currently checks the tests, pylint and the commit message format.NotesThe following steps are automatically executed via pre-commit hooks.You can run pylint withpylint gitea_auto_updateAfter changes and commit, you can check if your commit message follows the contribution guidelines withgitlint. If there is a problem, gitlint will show you a error message.ContributorsSeehttps://github.com/CMiksche/gitea-auto-update/graphs/contributorsThank you for your support!Interested in contributing to this project? Check out theContribution Guidelines.
Package: gitea-github-sync
gitea-github-syncgitea-github-sync provides a simple CLI to sync Github repositories to your Gitea instance.Installationpip install gitea-github-syncIf you are interested in using a pre-packaged docker image, please look at theDocker ReadmeSetupCreate a file in$HOME/.config/gitea-github-sync/config.ymlwith the following template and fill up the missing values:gitea_api_url:https://<your-gitea-instance>/api/v1gitea_token:<your-gitea-token>github_token:<your-github-token>Creating a Gitea tokenGo to https://<your-local-gitea-instance>/user/settings/applications and generate a new token.Creating a Github tokenGo tohttps://github.com/settings/tokens/newand create a token with the following values set:Note: this is a note to help you understand how the token is used.Expiration: No expirationrepo: Select all of repoGithub token limitationGithub allows you to createPersonal access tokens. These tokens now exist in two different flavors:Fine-grained tokensClassic tokensBoth work with gitea-github-sync, but given that Gitea does not allow the modification of the access token through the API, anon-expiringtoken must be used which limits the usage to Classic tokens.Usagegitea-github-sync --helpShows the helpgitea-github-sync list-all-gitea-repositoriesLists all available Gitea repositories in your accountgitea-github-sync list-all-github-repositoriesLists all available Github repositories in your accountgitea-github-sync migrate-repo FULL_REPO_NAMEMigrates one repo from Github to Giteagitea-github-sync syncMigrates all repos not present in Gitea from GithubAutomate gitea-github-sync executionThere are multiple ways to automate the execution of gitea-github-sync. One of them is using cron:First, executecrontab -eto open the cron configuration file in edit mode.Then add the following line:0 12 * * * gitea-github-sync syncThis will execute the sync operation every day at twelve.LimitationsWhen using the migration feature of Gitea, a Github token must be passed for Gitea to continuously pull the new changes from Github.The token used by gitea-github-sync to list repositories is the same that is used by Gitea for continuous monitoring. Updating the value of this token is unfortunately not possible through the API as of now.
Package: giteamigration
[![Build Status](https://cloud.drone.io/api/badges/amritanshu-pandey/migr82gitea/status.svg)](https://cloud.drone.io/amritanshu-pandey/migr82gitea)Program to create and sync gitea migrations from various supported git servers### Supported serversGiteaGitlab (self hosted and gitlab.com)Github.comFree software: MIT licenseDocumentation:https://gitback.readthedocs.io.### CreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2020-02-22)First release on PyPI.
Package: gitease
GitEaseA tool to simplify git usage with sprinkles of AI magic.Humans think in simpler terms than git operates in. This tool aims to bridge that gap by providing a simpler language to
do common git tasks. Plus an LLM can write your commit messages for you.You can load recent information withgs load, save current changes withgs saveand share them withgs share.Behind the scenes it's exactly what you would expect from git, but with a simpler interface.InstallGet anopenai api key$exportOPENAI_API_KEY=...
$pipinstallgiteaseIf OPENAI_API_KEY is not set, you will be prompted to enter a commit message manually.UsageWithin a repo, run:$ge--help

Commands:--help:Showthismessageandexit.save<message>:Addandcommitfilestogit.Massageisgeneratedifnotprovidedshare<message>:Sharetoremote-Add,commitandpushchangestogit.Massageisgeneratedifnotprovidedload:Pullrecentupdatesfromgitmessage:GeneratecommitmessagefromdiffusingAI.undo:Undolastgitaction-onlyworksusingAIExamples$gesave

>EnteringnewStuffDocumentsChainchain...


>EnteringnewLLMChainchain...
Promptafterformatting:
Writeaconcisesummaryofthefollowing:
...
>Finishedchain.

Yourcommitmessageis:
docs:Updatedocumentation,configuration,andindexfiles
Thiscommitupdatesthedocumentation,configuration,andindexfilesfortheproject,includingMakefile,
conf.py,andindex.rst.Thesechangesprovideinformationabouttheproject,itsfeatures,andquickstart
instructions.Additionally,itupdatestheversionofgiteasefrom0.0.5to0.0.6.

Toconfirm,pressEnter.
Otherwise,writeyourownmessage:
PressCTRL+Ctocancel
Response:# Add and Commit all python files in src with the message "feat: Add new script"gesave-a'src/*.py'-m'feat: Add new script'# Add multiple filesgesave-aREADME.md-agitease/cli.py# Add and commits everything without prompting for validationgesave-y# Add the README.md file and commit with a generated messagegeshare-aREADME.md-y# Add and commit README.md file with "upload readme" message, merges to main, and deletes the original branchgeshare-aREADME.md-m"upload readme"--merge=main--delete# Pull recent changes from gitgeload$geundo

WelcometoGitEase
Lastgitactionis:UpdateREADMEandCLIfiles
Arevertcommandis:gitresetHEAD@{0}ShellIrunthecommandforyou?[y/n]:Running:gitresetHEAD@{0}Unstagedchangesafterreset:
MREADME.md
Mgitease/cli.py
Package: git-easy-crypt
git-easy-cryptThe easy way to encrypt/decrypt private files in the git repo.Installyou can install git-easy-crypt by pip:$ pip install git-easy-cryptor download the script directly:$ sudo curl -o /usr/local/bin/gecrypt https://raw.githubusercontent.com/taojy123/git-easy-crypt/master/gecrypt.py 
$ sudo chmod a+x /usr/local/bin/gecryptUsagegecrypt setkey mysecretkey             Set a secret key for encrypt/decrypt in current repo
  gecrypt setkey mysecretkey -y          Set a secret key without input yes
  gecrypt showkey                        Show secret key
  gecrypt encrypt file                   Encrypt a file (decrypt file to file.sec)
  gecrypt encryptall                     Encrypt all decrypted files in current repo
  gecrypt decrypt file.sec               Decrypt a file (decrypt file.sec to file)
  gecrypt decrypt file.sec anther_file   Decrypt file.sec to anther_file
  gecrypt decryptall                     Decrypt all encrypted files in current repo
  gecrypt version                        Show version
  gecrypt help                           Show help for commandsBest PracticeAlice, encrypt the secret files and push:$ git clone https://github.com/taojy123/test
Cloning into 'test'...
...
Unpacking objects: 100% (3/3), done.
$ cd test

$ gecrypt setkey abc123
`abc123` has saved in .git-easy-crypt-key

$ echo MYSECRET=AAA > keys.txt
$ ls
README.md    keys.txt

$ gecrypt encrypt keys.txt 
Encrypt success!
The secret code has been saved in `keys.txt.sec`, and `keys.txt` is ignored by git.
You must keep the secret key `abc123` in mind for decrypt the file in the future!!!
$ ls
README.md    keys.txt     keys.txt.sec

$ git add .
$ git commit -m "add encrypted secret file"
[master 3d8ef6f] add encrypted secret file
 2 files changed, 5 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 keys.txt.sec

$ git push
...
To https://github.com/taojy123/test
   4d86b27..3d8ef6f  master -> master
$Bob, pull and decrypt the secret files:$ git clone https://github.com/taojy123/test
Cloning into 'test'...
...
Unpacking objects: 100% (7/7), done.
$ cd test

$ ls
README.md    keys.txt.sec

$ gecrypt setkey abc123
`abc123` has saved in .git-easy-crypt-key

$ gecrypt decryptall
`./keys.txt.sec` has been decrypted to `./keys.txt`.

$ ls
README.md    keys.txt     keys.txt.sec

$ cat keys.txt
MYSECRET=AAA 
$
Package: git-edit-index
This command represents a faster alternative togit add-iorgit gui.
It allows you to stage or unstage files from the index in an editor, just like
when you perform an interactive rebase.For example, let’s assume you have the following three modified files (git status--short):M path/to/file1
M another/path/to/file2
M yet/another/path/to/file3After runninggitedit-index, an editor will show up with the above output.
To stage (add) the first two files, simply change the text toA path/to/file1
A another/path/to/file2
M yet/another/path/to/file3The supported statuses areM,A,D, and?. They allow you to
not only stage files but also unstage them, delete them, or revert changes done
to them since the last commit.See theproject’s homepagefor
more information.
Package: gitee-deleter
IntroductionGitee账号注销[砖]家，一键删光「我的仓库」。Requirementsgoogle-chromePython3.8+Usage项目依赖 google-chrome 运行，请确保你的计算机已装有谷歌浏览器。下载依赖pipinstallgitee-deleter六根清净方为道，退步原来是向前拷贝如下参考代码，填入必要的账号信息，执行程序。该脚本启动有头模式浏览器进行自动化作业。由于「删库」是相当敏感的操作，所以在本人在不影响脚本性能的情况下插入了非常多的sleep语句。如果你发现情况不对，手动关闭浏览器杀死进程即可。fromgitee_deleterimportremove_allGITEE_USERNAME:str=""GITEE_PASSWORD:str=""if__name__=="__main__":remove_all(username=GITEE_USERNAME,password=GITEE_PASSWORD)
Package: giteesdk
giteesdk介绍gitee的api封装软件架构软件架构说明安装教程pip安装pipinstallgiteesdkpip安装（使用淘宝镜像加速）pipinstallgiteesdk-ihttps://mirrors.aliyun.com/pypi/simple使用说明demoimportgiteesdkgitee_basic=giteesdk.Basic()gitee_basic.repos()文档官方主文档：https://gitee.com/api/v5/swagger
Package: gitee-utils
gitee-utilsA command-line tool ported fromgithub-utilsto manage repositories on Gitee.Installpip install gitee-utilsConfigurationsIn file~/.gitee-utils/config.ini[auth]
access_token = GITHUB_ACCESS_TOKENCommandsList all repositoriesgitee-utils list-reposCreate new repositoriesgitee-utils create-repo [--private] [--description DESC] [--path PATH] [--homepage URL] [--has-issues] [--has-wiki]
                        [--can-comment] [--auto-init] [--gitignore_template LANG] [--license-template LICENSE]
                        NAME...Delete existing repositoriesgitee-utils delete-repos [--all] [NAME...]LicenseCopyright (C) 2020 HE Yaowenhe.yaowen@hotmail.comThe GNU General Public License (GPL) version 3, seeCOPYING.
Package: gitegginfo
IntroductionPackagegitegginfoadds twosetuptoolscommands to make it possible to
use setuptools with git repositories when building development eggs.  Problems
occur in that setuptools specifically looks forsubversionrevision numbers,
even when subversion is not the underlying SCM.This package is intended for use withgit-svn, which I use as an interface
between git and subversion.gitegginfoThegitegginfocommand is an extension of setuptools’ egg_info command.
Where the egg_info command is unwisely specific to thesubversionversion
control system, the gitegginfo command is unwisely and explicitly tied to the
Git DVCS (distributed version control system).gitsdistThesdistcommand that comes with setuptools is used to generate source
distributions, i.e. tarballs. When building a development (“dev”) egg,
setuptools attempts to query the current revision number via theegginfocommand, which fails for reasons described above.  Thegitsdistcommand
instead uses thegitegginfocommand to get the revision information.Sample CommandsTo build an.egg-infofolder withgit-svnrevision data:python setup.py gitegginfo -rTo build a development source distribution:python setup.py gitegginfo -rDb dev gitsdistTroubleshootingIf you run into the problem where setuptools isn’t including all your code in
the created egg, you may need to install packagesetuptools-git.EditorialAs I write this, the Python packaging infrastructure is in a dismal state.See Alsodistutils,git,git-svn,sdist,setuptools,setuptools-git,subversionChanges0.3 - 2011-07-08added gitsdist command [jt]0.2 - 2010-06-22bug fix / ‘git-svn’ invocation [jt]0.1 - 2010-04-08pulls git-svn revision [jt]
Package: git-empty-dirs
# GitEmptyDirs !!Ever came up with a scenario where you have extracted a software platform and initialised a git repository on it so that you can start building things on it ? If in case, the extracted platform contains lot of empty directories, those directories don’t get committed to you repository which can lead to lot of errors for your co worker. GitEmptyDirs is helpful in those kind of scenarios. It creates an empty .gitignore file or copies a specified file in all empty folders so that every folder gets committed.## InstallationEasily install using one simple command:pip install git-empty-dirs## UsageGitEmptyDirs can be triggered in below ways.git_empty_dirsIt uses the current directory as the base directory and creates an empty .gitignore file in all empty directories.git_empty_dirs  -b <path  to  base  folder>It uses the path provided as the base directory and creates an empty .gitignore file in all empty directories.git_empty_dirs -s <path  to  sample  file>It uses the current directory as the base directory and copies the sample file in all empty directories.git_empty_dirs  -b <path  to  base  folder> -s <path  to  sample  file>It uses the path provided as the base directory and copies the sample file in all empty directories.For help please invokegit_empty_dirs -husage: git_empty_dirs [-h] [-b BASE_DIR] [-s SAMPLE_FILE]optional arguments:-h,--helpshow this help message and exit-bBASE_DIR,--base-dirBASE_DIRSpecify the base directory for searching empty
directories-sSAMPLE_FILE,--sample-fileSAMPLE_FILESpecify the file to be copied to each empty directory
Package: gitenberg.metadata
# metadata
metadata development - formats and machinery for GITenberg![travis status](https://img.shields.io/travis/gitenberg-dev/metadata.svg)
![PyPI version](https://img.shields.io/pypi/v/gitenberg.metadata.svg)## InstallationThese metadata tools are hosted on PyPI as the namespaced package [gitenberg.metadata](https://pypi.python.org/pypi/gitenberg.metadata/)pip install gitenberg.metadataHistory0.1.5 (2015-07-25)Corrects author and other PyPi metadata0.1.4 (2015-07-25)Adds python package requirements to setup.py0.1.3 (2015-07-25)fixes manifest and history loading for pypi0.1.0 (2015-07-16)First release on PyPI.
Package: giteo
GiteoTable of ContentsAboutGetting StartedUsageContributingAboutGiteo is a CLI-based URL shortener written in Python which uses GitHub'sgit.ioURL shortening service.Getting StartedThese instructions will get you a copy of the project up and running on your local machine.PrerequisitesPython 3.7+PipenvDocker (Optional)Development SetupFork this repoSet up your Pipenv environment (pipenv install)Set up your Docker environment (docker build -t giteo:latest .) (Optional)InstallingBare Metal Installpip install giteoDocker Installdocker pull TuxOtaku/giteo:latestUsageBare Metalgiteo --url <url_to_be_shortened> --code <shortened_url_suffix>Dockerdocker run --rm TuxOtaku/giteo:latest --url <url_to_be_shortened> --code <shortened_url_suffix>
Package: giterm
FeaturesGiterm is a ncurses-based terminal GUI for Git. It brings information about the current status of your Git working copy right in your terminal,real-time.It exposes in a single view:local branches, and which branch you’re currently onremote branches, and which branch the current local branch is
trackingcommit history, and which commit you are currently working fromcurrent changesadiffview of the selected file in thechangeslistReal-time!Every change to the working copy (file edition/move or any Git command)
updates the GUI instantly. You can work as usual, and keep a terminal
open with giterm to get instant feedback on your actions.NoteGiterm essentiallyshowsGit information. It does not support git actions like commit, checkout, branch switching, committing. Only staging/unstaging is supported at this time.InstallationpipinstallgitermOr even better:pipxrungitermIf you don’t havepipinstalled yet:curl-shttps://bootstrap.pypa.io/get-pip.py|sudopythonpipinstallgitermNoteWindows users beware, Python for Windows doesn’t come with curses. You need to visitcurses repository, download the version of curses that corresponds to your Windows and version of Python, and then pip install the whl file with the python you plan on using.Usagecdpath/to/git/working/copygitermKeymap[tab]: Toggle panel[shift + tab]: Reverse Toggle[up]/[down]: Scroll line by line[page up]/[page down]: Scroll screen by screen[h]: Log history[c]: Changes view[s]: Staging area[d]: Diff view[b]: Branches[r]: Remotes[t]: Tags[space]: Stage/unstage current file[q]: QuitRequirementsGiterm needs thegitexecutable to be installed and available in the
PATH of your system. Others dependencies should be automatically handled
bypip.Technical backgroundGiterm uses subprocesses to call Git shell-based commands, and parses
their outputs to bring the relevant information to the user interface.It also uses a watchdog to listen file changes in the current working
directory.LicenseThis software is provided under the BSD 2-Clause License. Please read
theLICENSE filefor further information.ContributeSee theCONTRIBUTING filefor how to help out.Many thanks for your support!
Package: git_export_hardlink
This package implements a git export command that can be given a list of
already exported worktrees and the tree SHAs these worktrees correspond
too. For every file to export it then looks in the existing worktrees whether
an identical file is already present and in that case hardlinks to the new
export location instead of writing the same file again.Use Case: A git based web deployment system that exports git trees to be
served by a web server. Every new deployment is written to a new folder. After
the export, the web server should start serving new requests from the new
folder.Be aware of the dangers of hardlinks. Hardlinks on linux do not
have copy-on-write semantics! This command also does not verify the integrity
of old exported trees. Use git reset –hard after this command to guarantee
a correct export.
Package: git-ext
Create PullRequest, view activities/discussion from command line.A git extension that allows you submit pullrequests from command line.Current support:gitlabbitbucketTo support:githubinstallUse pip to install.:pip install git-extThen run init-git-ext command to write your bitbucket account infomation to ~/.git_ext.yml(Pullrequests need account info with HTTP BASIC AUTH.:init-git-extOr edit~/.git_ext.ymlby hand:bitbucket:
  email: ''
  password: ''
gitlab:
  domain: ""
  private_token: ""
git_ext:
  logging: {format: '%(name)s - %(message)s', level: DEBUG}OptionalYou can add a git alias if you are lazy like me :):git config --global alias.pr pullrequestusage$ git pullrequest create test_b master
Reviewers(start with @):
201 Created!
#2 This is your commit title.[test_b->master]  by boson_laixintao(just now)
Reviewers:

$ git pullrequest list
#2 This is your commit title.[test_b->master]  by boson_laixintao(just now)

$ git pullrequest
Usage: git-pullrequests [OPTIONS] COMMAND [ARGS]...

Options:
  --help  Show this message and exit.

Commands:
  activity  Show a pr's activity, display lastest 10...
  create
  listDevelopExport a enviroment to see the logs:export GITEXT=debugLicensesGPLv3
Package: git-extract
git-extractExtract files or directories from a git repositoryInstallation$pipinstallgit-extract--upgradeOfficial PyPi RepositoryUsageExtract files with multiple patterns:$git-extractfilehttps://github.com/mfdeux/git-extract--pattern"*.md"--pattern"*.py"--dest~/Downloads/test--recursiveExtract directory with pattern:$git-extractdirhttps://github.com/mfdeux/git-extract--pattern"tests"--dest~/Downloads/testPatternsMultiple patterns are acceptable -- as many as you want!You can think of patterns as filters.  When git-extract is looking throughout the git repository, it will match files or directories based on the patterns supplied.All patterns are based on standard Python glob patterns.You can read more about how to construct the patterns at:https://docs.python.org/3/library/glob.html
Package: gitfaces
gitfacesgitfaces collects avatars for all contributors of a given Git repository. (This
can be used forGource's--user-image-dir, for example.)Simply typegitfaces /path/to/git/repo out/and gitfaces will start fetching fromGravatarandGitHub. Once done, theout/directory will contain
all the avatars.Installationgitfaces isavailable from the Python Package
Index, so simply typepip install -U gitfacesto install or upgrade.TestingTo run the gitfaces unit tests, check out this repository, set the environment
variableGITFACES_TESTto the local path of a Git repository on which you
would like the tests to be performed, and typepytestLicenseThis software is published under theGPLv3 license.
Package: git-feature-notion
Git NotionSyncs Github markdown files in your repository to Notion.This utility is described in the followingblog post.See exampleNotion page.Installationpip install git-feature-notionor for local installation:gitclonehttps://github.com/NarekA/git-feature-notion.gitcdgit-feature-notion
pipinstall-e.ConfiguringNOTION_TOKEN_V2- Can be found in yourbrowser cookiesfor Notion's website.NOTION_ROOT_PAGE- URL for notion page. Repo docs will be a new page under this page.NOTION_IGNORE_REGEX- Regex for paths to ignore.NOTION_SEARCH_BY_REGEX- Regex for pattern for file search.These environment variables can be set.exportNOTION_TOKEN_V2=<YOUR_TOKEN>exportNOTION_ROOT_PAGE="https://www.notion.so/..."# Can be in setup.cfg as wellexportNOTION_IGNORE_REGEX="models/.*"# Can be in setup.cfg as wellexportNOTION_SEARCH_BY_REGEX="**/*.md"# Can be in setup.cfg as wellThese parameters can be set in thesetup.cfgfor the repo.[git-feature-notion]
ignore_regex = models/.*
notion_root_page = https://www.notion.so/...
search_by_regex = "**/*.md"Usage# To upload your current directorygit_feature_notion# To upload another directorygit_feature_notion--pathpath/to/your/repoPushing to PYPIbumpversionpatch# Look-up bumpversionrm-rfdist/
python3setup.pysdistbdist_wheel
python3-mtwineuploaddist/*orbumpversion--current-version0.2.6majorsetup.py