Saravanan666/pypi-org huggingface dataset:
Package: commitguard
Library for managing and writing git hooks in Python using `pyproject.toml` for its settings ✨InstallationYou can add commitguard in a few easy steps. First of all, install the dependency:$pipinstallcommitguard

--->100%

Successfullyinstalledcommitguard-0.1.0or Using poetrypoetryadd--devcommitguard
poetryruncommitguardactivate--modepoetryThe output ofcommitguard activateshould be similar to:✓commitguardpre-commithookinstalledat/commitguard/.git/hooks/pre-commitusingpoetrymode.CommitGuard offers an adaptable plugin architecture where each plugin offers unique features that might require the installation of supplementary dependencies.To manage these dependencies, CommitGuard presently supports three modes:pythonpathfor dependency management via [pip]poetryfor dependency management via [poetry] (recommended)pipenvfor dependency management via [pipenv]These modes dictate how CommitGuard, the plugins, and their dependencies are loaded during git hook execution.LicenseThis project is licensed under the terms of the MIT license.
Package: commitizen-cz-fogoprobr
commitizen-cz-fogoprobrCommitizen personalizado por melattofogoUsoListar commitizen instaladoscz lsCommitdecodeemstagecz --name cz_fogoprobr commitAlternativamente, definindo o commitizen do projeto em um arquivo.czdo projeto(echo [commitizen] & echo.name = cz_fogoprobr) >> .cz
cz commitRequisitoscommitizen2.21.2AutorJoao Fogo (melatto.fogo@live.com)
Package: commitizen-gitmoji
cz-conventional-gitmojiAcommitizenplugin that combinesgitmojiandconventional commits.Installationpoetryaddcz-conventional-gitmojior with pip:pipinstallcz-conventional-gitmojiUsageThis package can be used as a normalcommitizenplugin, either by specifying the name on the command linecz--namecz_gitmojicommitor by setting it in yourpyproject.toml[tool.commitizen]name="cz_gitmoji"This will makecommitizenuse the commit message parsing rules defined by this plugin, which are 100% compatible withconventional commits. As such, the gitmojis are completely optional and all commands will continue to validate commit messages in conventional format just fine. This is useful if you're transitioning an existing repo tocontentional-gitmojior you work in a team in which some colleagues don't like gitmojis.gitmojifyApart from the conventional-gitmoji rules, this package provides thegitmojifycommand which is also available as a pre-commit hook. The command reads a commit message either from cli or a commit message file and prepends the correct gitmoji based on the type. If the message already has a gitmoji, it is returned as is.$gitmojify-m"init: initial version"🎉init:initialversionTo use it as a pre-commit hook, install this packages as well ascommitizenand put the following into your.pre-commit-config.yamlrepos:-repo:https://github.com/ljnsn/cz-conventional-gitmojirev:mainhooks:-id:conventional-gitmojiCommit with a message in conventional format that contains a valid type mapped by conventional gitmoji and the gitmoji will automagically be added.FeaturesEnable conventional gitmoji commit messages viacz commit.Add--simple-emojisoption to use only the emojis relating tocz_conventional_commitstypes.Add--simple-typesoption to use only the types used bycz_conventional_commits.Add--conventionaloption to put the emoji in the commit message, making it compatible withcz_conventional_commits.Add hook to automatically prepend the appropriate gitmoji for the commit's type.Inspirationcommitizen-emoji
Package: commitlint
commitlintcommitlint is a tool designed to lint your commit messages according to theConventional Commitsstandard for your pre-commit hook and GitHub Actions.How to useFor pre-commitAdd the following configuration on.pre-commit-config.yaml.repos:...-repo:https://github.com/opensource-nepal/commitlintrev:v0.2.1hooks:-id:commitlint...Install thecommit-msghook in your project repo:pre-commitinstall--hook-typecommit-msgNOTE:Installing using onlypre-commit installwill not work.For github-actionsIf you have any existing workflows, add the following steps:steps:...- name:Run commitlintuses:opensource-nepal/commitlint@v0.2.1...If you don't have any workflows, create a new GitHub workflow, e.g..github/workflows/commitlint.yaml.name:Commitlinton:push:branches:['main']pull_request:jobs:commitlint:runs-on:ubuntu-latestname:Commitlintsteps:-uses:actions/checkout@v4-name:Run commitlintuses:opensource-nepal/commitlint@v0.2.1NOTE:commitlint GitHub Actions will only be triggered by "push" or "pull_request" events.ContributionWe appreciate feedback and contribution to this package. To get started please see ourcontribution guide.
Package: commit-linter
commit-linterAn easy to use tool to that lints your commit messages according to commit conventions .commit-linter is a Python tool that helps you standardize your commit messages to a knowncommit conventions. the tool also add emojies to your commits.InstallationUse the package managerpipto install commit-linter.pipinstallcommit-linterUsagein your git repository just executecommit-linterorcommit-linterinstallif you want to remove the hook, just executecommit-linterremoveHow it workscommit-linter uses git-hooks which are scripts that exists in each repository.
Take a look at any repo you have, you will have.gitdirectory, and inside you
will findhooksdirectory, commit-linter just puts a simple script namedcommit-msginside that  directory and makes it executable so each time you right a commit message
it will get linted as per the conventions, you can look at script in your repository
inside.git/hookspath.Read more aboutGit Hooks.ContributingPull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.LicenseThis Tool is UnderMITLicense.
Package: commitment
commitmentAn incomplete Python 3 wrapper for theGitHub API.Note this project does not aim to provide a complete abstraction over the GitHub API - just a few high-level convenience methods for pushing data to a GitHub repo.Installationpip install commitmentUsageGenerate a GitHub API key:https://github.com/settings/tokensfromcommitmentimportGitHubCredentials,GitHubClientcredentials=GitHubCredentials(repo="myuser/somerepo",name="myuser",email="someone@example.com",api_key="f00b42",)client=GitHubClient(credentials)client.create_branch('my_new_branch',base_branch='master')client.push_file('Hello World!','directory/filename.txt','my commit message',branch='my_new_branch')client.open_pull_request('my_new_branch','title','body',base_branch='master')
Package: commit-message-validator
commit-message-validatoris a tool that validates git commit messages to
theWikimedia commit message guidelines.Please see <https://www.mediawiki.org/wiki/commit-message-validator> for more
details.UsageUse locally as a Pre-commit plugincommit-message-validatorcan be used as a plugin for thepre-commitgit
hooks system. Add the following to your.pre-commit-config.yaml:-repo:https://gitlab.wikimedia.org/repos/ci-tools/commit-message-validatorrev:# Fill in a tag / sha here (like v2.0.0)hooks:-id:commit-message-validatorThen install the pre-commit hook:pre-commitinstall--hook-typecommit-msgUse with gitlab.wikimedia.org’s CI/CDA GitLab CI/CD template is provided in this repo for linting of commit
messages in a merge request. Add the following to your.gitlab-ci.yml:include:-project:repos/ci-tools/commit-message-validatorfile:/templates/lint-merge-request.ymlContributingSeeCONTRIBUTING.rstfor guidelines on contributing tocommit-message-validator.Bug reportsPlease reports bugs and feature requests athttps://phabricator.wikimedia.org/tag/commit-message-validator/.LicenseLicensed under theGPL-2.0-or-laterlicense. SeeCOPYINGfor the full
license.
Package: commit-msg-git-hook
Commit Message Git HookA set of tools to validate git Conventional Commit messages.See theConventional Commits Specification.NOTE: It doesn't affect any previous commit on your repository.Installation InstructionsInstall from PyPI (Python Package Index)Run the script below to install the latest version of this package:pipinstallcommit-msg-git-hook--upgradeSetup the Local Git Hookcommit-msgRun one of the scripts below to scaffold the hook:For Linux and macOS:python3-mcommit_msg_git_hook.setupFor Windows:python-mcommit_msg_git_hook.setupIt does the following steps:Reads and then shows the type of your Operating System.Exits with an error message if the OS is unsupported.Creates a directory for git-hooks, by default./.github/git-hooks.Creates subdirectories for each of the supported OS's.Creates thecommit-msghook file for each OS if it doesn't exist.Fills it with a basic script to callcommit_msg.main(), from this package.If the OS is Linux or macOS, makes the hook file executable.Sets the hooks (relative) path to the current repository as the directory respective to the OS type (for example:./.github/git-hooks/linux).Creates a configuration filecommit-msg.config.jsonif it doesn't exist.Ends with a success message referencing again the type of your OS.Configuration InstructionsCustomize the configuration filecommit-msg.config.jsonto fit your project's needs.Probably you will want to addscopes, to fully utilize theConventional Commits Specification.Basic UsageAfter setting up and adding the new files to your git remote repository, your collaborators will
need to run theinstallationandsetupsteps again.
But, this time, the setup will only set the hooks path and make sure the filecommit-msgis
executable.Every time you make a commit, the hook will check if its message is in accordance to the
specification and the project's customization.How To Edit CommitsIf your branch is not shared yet (not merged intodevelop, for example), you can edit your commits
with the command below. Git will list the lastncommits and ask you whether you want to keep or
edit each one of them.gitrebase-iHEAD~nMore information here:https://docs.github.com/pt/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-messageCreditsThis package was created from aCraicoverflowtutorial.See the tutorial at the link:https://dev.to/craicoverflow/enforcing-conventional-commits-using-git-hooks-1o5p
Package: commit-msg-hook
commit-msg-hookThis hook is made as a custom plugin under thepre-commithook framework and checks if commit message matches the chaos-hub team commit rules.Installationpip install commit-msg-hookUsing commit-msg-hook with pre-commitFor more details see:pre-commitInstall pre-commit package managerpip install pre-commitCreate a file.pre-commit-config.yamlin the root folder with the following configuration- repo: https://github.com/dimaka-wix/commit-msg-hook.git
  rev: v0.3.4
  hooks:
    - id: commit-msg-hook
      stages: [commit-msg]To enable commit-msg hook with pre-commit run:pre-commit install --hook-type commit-msgUpdate to the latest release (optional)pre-commit autoupdate --repo https://github.com/dimaka-wix/commit-msg-hook.gitCommit RulesWrite up to72characters(preventing ellipsis in git)Capitalize the subject lineUse the imperative mood(e.g.Addinstead ofAdded,AddsorAdding)Do not end the lines with any punctuation characterUse the description to explain what and why vs howIn case of multiline message do the following:PressShift+Enterto create a new line and to write more characters then vscode lets youSeparate subject line from message body with a blank lineFollow the rules above when writing each line of the messageExampleRefactor foo function in x file from y component

* Remove duplications
* Add docstrings
* Update the types of argumentsBypass the hook in one of the following waysSKIP=commit-msg-hook git commit -m "Your message"git commit -m "Your message" --no-verifygit commit -m "Your message" -n (not recommended)
Package: commit-msg-regex-hook
commit-msg-regex-hookBefore the readme, big shoutout to @dimaka-wix who's repocommit-msg-hookwas the basis for this repository. Go check out his repo for more information.This hook is designed to be used with thepre-commithook framework. It will check your commit string against the provided regex.UtilizingFirst you will need to setuppre-commitusing their documentation. Then you will be able to add this repository under it with the following:- repo: https://github.com/dimaka-wix/commit-msg-hook.git
  rev: v0.3.1
  hooks:
    - id: commit-msg-hook
      args: ["regex='[A-Z]{3,4}-[0-9]{3,6} \| [\w\s]* \| .+'"]
      stages: [commit-msg]To enable commit-msg hook with pre-commit run:pre-commit install --hook-type commit-msgUpdate to the latest release (optional)pre-commit autoupdate --repo https://github.com/dtaivpp/commit-msg-regex-hook.git
Package: committed
committedNitpicking commit history sincebeabf39Enforce commit standards, whether for:Readability, especially in logsConsistent stylingCompatibility with programmatic processingInstallDownloada pre-built binary
(installable viagh-install.Or use rust to install:cargoinstallcommittedpre-commitTo usecommittedwithpre-commit, point its
config at this repository:repos:-repo:https://github.com/crate-ci/committedrev:v1.0.20hooks:-id:committedThecommittedid installs a prebuilt executable from GitHub releases. If
one does not exist for the target platform, or if one built from
sources is preferred, usecommitted-srcas the hook id instead.Be sure to changerevto use the desiredcommittedgit tag or
revision.The hook, by default, will verify your commit message.Basic UsageVerify your latest commitcommittedHEADVerify your branchcommittedmaster..HEAD--no-merge-commitHave your CI verify your PR (assuming it does a no-ff merge into yourmaster)committedHEAD~..HEAD^2--no-merge-commitSeeimperativefor an Azure Pipeline
exampleor look atcommitteds ownazure-pipelines.yml,.travis.yml, orappveyor.yml.ReferenceContributeLicenseLicensed under either ofApache License, Version 2.0, (LICENSE-APACHEorhttp://www.apache.org/licenses/LICENSE-2.0)MIT license (LICENSE-MITorhttp://opensource.org/licenses/MIT)at your option.
Package: commix
Installation$ pip install commix && commixFeaturescommix, ** Automated All-in-One OS Command Injection Exploitation Tool. **How to install ?$ pkg install python -y
$ pip install commix
$ commixRun ?$ commixDisclaimerWe are not responsible for your loss by this tool.
this tool is made for Education/Learning Purpose.
Dont harm anyone using this tool.Usage$ commix -h

Author : Commix Project
PIP module : Parixit Sutariya
Github : github.com/Bhai4You
Blogspot : https://bhai4you.blogspot.comGithub
Package: commodity-tool
Copyright (c) 2019 johnnymac0515Permission 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.Description: # Commodity-ProjectThe purpose of this project is to produce time-series visualizations that allow the user to identify the extent to which the indistrial revolution affected the price of various commodities across various countries.
Data set courtesy of Robert Allen and Richard Unger and can be found athttps://www.kaggle.com/sohier/allenunger-global-commodity-pricesPhase 1: User can run tool with a filter on individual contries and individual commodities
Phase 2: Implement time-series statistcal measures to score the influence the Industrial Revolution had on the price of a              commodity
Phase 3: Wrap in GUIPlatform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: MacOS X
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Natural Language :: English
Classifier: Programming Language :: Python :: 3.7
Classifier: Topic :: Scientific/Engineering :: Information Analysis
Package: commodore
Manage and maintain your user’s scripts and toolsInstallationFrom pypi:$ pip install commodore… or from the project root directory:$ python setup.py installThen runcommodorefrom the command line to create the required configuration and binary directory, and define your desired editor.UsageCreate a new script:$ commodore create helloworldEdit your script, including the shebang line:#!/usr/bin/env python
print('Hello world!')Then run it!:$ helloworld
Hello world!List your scripts:$ commodore list
helloworldEdit an existing script:$ commodore edit helloworldAnd finally, delete it:$ commodore delete helloworldUse –help/-h to view info on the arguments:$ commodore --help
usage: commodore [-h] {create,list,edit,delete} ...

positional arguments:
  {create,list,edit,delete}

  optional arguments:
    -h, --help            show this help message and exitYou can manually check the history of created, edited and deleted scripts by navigating
to the commodore binary directory (default ~/.commodore/bin) and using git commands to
see changelogs. Every create, edit and delete will be tracked as a git commit.You can also run git commands via commodore:$ commodore git 'log -p'
...
$ commodore git 'remote add origin ssh://git@bitbucket.org/me/my_commodore_bin_dir'
$ commodore git 'push -u origin master'Release Notes0.1.4:Fix bug where file might disappear while editing causing a crash. Alerts user.Now works with gvim if--noforkis passed0.1.3:Support EDITOR command line args (eg. emacs -t)0.1.2:Addgitcommand0.1.1:Updated README and notes on usage0.1.0:commodore create, edit, delete works0.0.1:Project created
Package: common
Copyright (c) 2016 Marcel HellkampPermission 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: common-app
Not On PyPiThis is a reserved package name to preventdependency confusion / substitution attack. If installed, will immediately raise an error indicating that the wrong PyPi repository was used.If someone would like to use this package name, I would be happy to discuss handoff. Please contact me through a Github issue onKyleKing/not-on-pypior if I don't respond, you can try mygmailaccountdev.act.kyle
Package: commonbase
Commonbase Python SDKCommonbase allows developers to integrate with any popular LLM API provider
without needing to change any code. The SDK helps with collecting data and
feedback from the users and helps you fine-tune models for your specific use
case.Installationpip install commonbaseUsageA Project ID and API Key are required for all Commonbase requests. You can find
your project ID and generate an API key in theCommonbase Dashboard.To create a text completion, provide your Project ID, API Key, and prompt toCompletion.create.importcommonbaseresult=commonbase.Completion.create(api_key="API_KEY",project_id="PROJECT_ID",prompt="Hello!")print(result.best_choice.text)To stream a completion as it is generated, useChatCompletion.stream.For more examples, see/examplesor check out ourDocs.
Package: common-bootstrap
Not On PyPiThis is a reserved package name to preventdependency confusion / substitution attack. If installed, will immediately raise an error indicating that the wrong PyPi repository was used.If someone would like to use this package name, I would be happy to discuss handoff. Please contact me through a Github issue onKyleKing/not-on-pypior if I don't respond, you can try mygmailaccountdev.act.kyle
Package: commoncode
license: Apache-2.0copyright: copyright (c) nexB. Inc. and othershomepage_url:https://github.com/nexB/commoncodekeywords: utilities, scancode-toolkit, commoncodeCommoncode provides a set of common functions and utilities for handling various things like paths,
dates, files and hashes. It started as library in scancode-toolkit.
Visithttps://aboutcode.organdhttps://github.com/nexB/for support and download.To install this package use:pip install commoncodeAlternatively, to set up a development environment:./configure --dev
source venv/bin/activateTo run unit tests:pytest -vvs -n 2To clean up development environment:./configure --clean
Package: common-cols-project
Common Columns PackageThis package contains a function calledcommon_columnsthat can be used to find the common columns between all pairs of data frames.InstallationTo install this package, you can use pip. Open your terminal and run the command provided above.UsageTo use the common_columns function, you first need to import it from the package:from common_columns import common_columnsThe function takes in a variable-length argument list of pandas data frames. Here's an example of how to use it:import pandas as pdfrom common_columns import common_columnsdf1 = pd.DataFrame({'A': [1, 2, 3], 'B': [4, 5, 6]})df2 = pd.DataFrame({'B': [7, 8, 9], 'C': [10, 11, 12]})df3 = pd.DataFrame({'B': [13, 14, 15], 'D': [16, 17, 18]})common_cols_all = common_columns(df1, df2, df3)In this example, we have three data frames (df1, df2, and df3). We call the common_columns function with these data frames as arguments, and store the result in the common_cols_all variable. The common_cols_all variable will contain a set of column names that are common to all three data frames, if any.Function DescriptionThe common_columns function takes in a variable-length argument list of pandas data frames, and returns a set containing the names of columns that are common to all data frames, if any. It works as follows:Initialize a list of common columns.Get the names of the data frames, assigning a default name to any data frames without a name attribute.Loop over all pairs of data frames.Find the common columns between the two data frames.
If there are common columns, add them to the list of common columns.Find the common columns across all data frames.Return a set containing the names of columns that are common to all data frames, if any.ContributingIf you'd like to contribute to this package, please feel free to fork the repository and submit a pull request. We welcome contributions from the community! You can also contact me on my personal email adress:elenagarciamanes@gmail.com