Saravanan666/pypi-org huggingface dataset:
Package: gitlab-sync
gitlab-syncThis provides the gitlab-sync tool which clones GitLab and updates repositories.ConfigYou will need to haveSSH access configured for GitLab, and
have created apersonal access tokenwith API access.The config goes in~/.config/gitlab-sync.tomlor~/.gitlab-sync.toml,
which isTOML.["~/team-x"]access-token="9koXpg98eAheJpvBs5tK"# you can see the paths of groups from the URL on GitLabpaths=["path/to/team-x"]# strip the common prefix from the given pathstrip-path=truestrategy="mirror"["~/gitlab"]# get the gitlab access token from running a commandaccess-token=["pass","GitLab/api-access-token"]# paths to clone from GitLab, can include slashes for groups/projectspaths=["mintel","obristow"]strategy="mirror"Usage$ gitlab-sync local-updateStrategiesYou have to define a strategy for each local copy you define in config, the
strategy defines what will happen when gitlab-sync runs over the given copy.mirrordelete repositories which no longer exist remotelymove repositories which have been moved remotelyupdate local repositoriesclean local repositories (prune+gc)clone new repositoriesThis is good for having a local copy which you can use to perform searches
in using something likeag.The local copies should not be modified by users.To doflesh out integration testscater for new repositories being made locally and pushed remotelycompare (toasted-)marshmallow as a replacement for attr+voluptious - marshmallow uses attr
Package: gitlab-tags-to-pip-index
This python script uses the gitlab api to inspect all tags for the a project and build a
python repository index to be used for automated installations with pip.
This is best used in Gitlab CI in conjunction with gitlab_release package to first attach a python package
to the current build tag, after which this can be used to generate a static web page to be hosted by gitlab
which pip can be pointed to as an index to install your package.
This can assist in distributing python packages that aren’t suitable for publishing on PyPI official index.It can be used in a gitlab-ci.yml stage like:release:
  stage: release
  script:
    - python3 setup.py sdist bdist_wheel
    - pip3 install gitlab_release
    - python3 -m gitlab_release $PRIVATE_TOKEN dist/*
  only:
    - tags

pages:
  stage: deploy
  script:
    - pip3 install gitlab_tags_to_pip_index
    - python3 -m gitlab_tags_to_pip_index ./public
  only:
    - tags
  artifacts:
    paths:
    - public

# Or if you want to include master builds as pre-release
pages:
  stage: deploy
  script:
    - mkdir -p ./public
    - mv ./*.whl ./public/
    - pip3 install gitlab_tags_to_pip_index
    - python3 -m gitlab_tags_to_pip_index --pre './public/*.whl' ./public
  artifacts:
    paths:
    - publicSeehttps://pypi.python.org/pypi/gitlab-releasefor more information about gitlab_release script.
Package: gitlab-to-codecommit-migration
gitlab-to-codecommit-migrationGitLab to AWS CodeCommit MigrationScript to migrate from GitLab to Amazon CodeCommit easily and setup your AWS environment with CodeCommit, CodePipeline and CodeDeploy as well.Installation through pip::pip install gitlab-to-codecommit-migrationMigrating one project::gitlab-to-codecommit --gitlab-access-token <your-access-token> --gitlab-url https://gitlab.youdomain.com --projects namespace/project-nameMigrate all projects from a GitLab server that the secure access token gives you access to read:gitlab-to-codecommit --gitlab-access-token <your-access-token> --gitlab-url https://gitlab.youdomain.com --allOr projects for a specific user or users:gitlab-to-codecommit --gitlab-access-token <your-access-token> --gitlab-url https://gitlab.youdomain.com --users user1 user2Or some groups:gitlab-to-codecommit --gitlab-access-token <your-access-token> --gitlab-url https://gitlab.youdomain.com --groups group1 group2And you can specify a Chime Webhook to receive notifications in a chat room as well:gitlab-to-codecommit --gitlab-access-token <your-access-token> --gitlab-url https://gitlab.youdomain.com --projects namespace/project-name --chime-webhook-url <chime-webhook-url>Free software: MIT-0 license (https://github.com/aws/mit-0)Documentation:https://gitlab-to-codecommit-migration.readthedocs.io.FeaturesLet me know :-)CreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2010-03-29)First release on PyPI.
Package: gitlab-todotxt
gitlab-todotxtA tool to synchronize GitLab issues to a todo.txt file.When started, gitlab-todotxt will read the configuration file, load all
issues, and write them into a todo.txt-type file of your choice.Configurationgitlab-todotxt requires a configuration file. It expects the configuration
file by default in ~/.config/gitlab-todotxt/gitlab-todotxt.conf.Each GitLab configuration is a separate section in the configuration file. The
title of that section must not contain any spaces.This is an example configuration:[example.org]
url = https://gitlab.example.org
token = your-access-token
projects = project1, project2
unassigned = noThe minimal required options are:url, the URL to the GitLab instance you are using.token, your personal API access token.file, the file where to write the tasks into.Additional options are:namespaces, the list of namespaces to consider when importing issues.
Only namespaces on this list will be considered when imporrting issues.
When left empty (the default), all accessible namespaces are considered.projects, the list of projects to consider when importing issues. Only
projects on this list will be considered when importing issues. When left
empty (the default), all accessible projects are considered.users, the list of users to consider when importing issues. Only issues
that are assigned to a user of this list (or to yourself) are considered
for importing. When empty (the default) no issues, unless assigned to you,
are imported.labels, the list of labels of which an issue must have at least one to
be included in the import.unassigned, whether or not unassigned issues should be imported.labels-are-projects, whether or not labels of issues should be added as
project tags.milestone-prefix, the prefix you would like to have before themilestoneelement, if there is a milestone. Defaults tomilestone:.format, the format to write the todo.txt task in. See below for details.Format OptionTheformatoption in the configuration can be used to customize in what
form your todo.txt tasks are written to file.The default is{delegate} {title} {due} {project} {milestone} {estimate} {spent} {url}These are also all possible fields:delegate: if an issue is assigned to someone else than you,@delegatedwill be written in this place, followed byto:and the username of those
the issue is assigned totitle: the title of the issue,due: the due date of the issue or, if there is none, the due date of the
milestone this task belongs to (if any); in form of adue:tag.project: the project this task belongs to.spent: the time spent on the task.estimate: the estimated time for the task.milestone: the milestone of the issue.url: the URL to the actual issue at the GitLab website
Package: gitlab-to-sqlite
gitlab-to-sqliteSave data from GitLab to a SQLite database.AttributionThe overall structure and CLI is taken fromhttps://github.com/dogsheep/github-to-sqlite/.How to installAuthenticationUsing custom gitlab instanceFetching projectsFetching merge requestsFetching pipelinesFetching environmentsFetching deploymentsFetching commitsHow to install$ pip install gitlab-to-sqliteAuthenticationCreate a GitLab personal access token:https://gitlab.com/-/profile/personal_access_tokensRun this command and paste in your new token:$ gitlab-to-sqlite authThis will create a file called auth.json in your current directory containing
the required value. To save the file at a different path or filename, use the
--auth=myauth.json option.As an alternative to using an auth.json file you can add your access token to an
environment variable called GITLAB_TOKEN.Using custom gitlab instanceWhen runningauthyou may specify an optional--hostparameter pointing
to a custom instance.$ gitlab-to-sqlite auth --host gitlab.internalFetching projectsTheprojectscommand retrieves a single project.$ gitlab-to-sqlite projects gitlab.db group/project-nameFetching merge requestsThemerge-requestscommand retrieves updated or created merge requests.$ gitlab-to-sqlite merge-requests gitlab.db group/project-nameThis command can be run regularly. Based on the most recent created or updated
merge request it only fetches changes that happened afterwards.Fetching pipelinesThepipelinescommand retrieves updated or created pipelines with their
corresponding jobs.$ gitlab-to-sqlite pipelines gitlab.db group/project-nameThis command can be run regularly. Based on the most recent created or updated
pipeline it only fetches changes that happened afterwards.Fetching environmentsTheenvironmentscommand retrieves all environments of a single project.$ gitlab-to-sqlite projects gitlab.db group/project-nameFetching deploymentsThedeploymentscommand retrieves all deployments of a specific environment in
a single project.$ gitlab-to-sqlite deployments gitlab.db group/project-name environment-nameThis command can be run regularly. Based on the most recent created or updated
deployment it only fetches changes that happened afterwards.Fetching commitsThecommitscommand retrieves all commits of a single project.$ gitlab-to-sqlite commits gitlab.db group/project-name
Package: gitlabui
gitlabuiFlask App over Gitlab Api to browse projects tags and to search into repository filesInstallationpipinstallgitlabuiRun Flask AppRun with gunicornexportGITLAB_URL=http://localhost/api/v4exportGITLAB_TOKEN=<YOUR_PRIVATE_TOKEN>
gunicorn-b0.0.0.0:5000gitlabui:appRun with dockerdockerrun-d\-eGITLAB_URL=http://localhost/api/v4\-eGITLAB_TOKEN=<YOUR_PRIVATE_TOKEN>\-p5000:5000batou9150/gitlabuigunicorn-b0.0.0.0:5000gitlabui:app
Package: gitlab-users
gitlab-usersA simple command line interface to manage GitLab user accounts, based onpython-gitlab.InstallationInstall the package on your systempipinstallgitlab-usersEdit the~/.python-gitlab.cfgfollowing thepython-gitlab package instructionsto setup the GitLab instance to connect with (present version only targets default instance).UsageGet helpgitlab-users-hList all users with their emailgitlab-usersList emails from a given groupgitlab-users-ga_group--email-onlyCreate multiple user accounts at once from a csv filegitlab-users--create-fromexample.csvwhereexample.csvcontains# username, name, email, [organization], [location], [group], [access_level]
wayne,Bruce Wayne,bruce.wayne@wayne-entreprises.com,Wayne Entreprises,Gotham City,Board,owner
kent,Clark Kent,clark.kent@krypton.univ,,SmallvilleList unused accounts (never sign-in or last connection is older than 1 year)gitlab-users--unused
Package: gitlab-v4
Gitlab ClientInstallTo install latest version:pip install gitlab-v4To install a specific version, for example: 0.0.1pip install gitlab-v4==0.0.1Usagefrom gitlab_client.gitlab_client import Gitlab

client = Gitlab(
	project_id="1234",
	access_token="abcd1234-efgh5678",
	gitlab_base_url="https://gitlab.com/api/v4"
)Once you instantiated a client instance as shown above, you can call different api methods available.
To list all branches in project:client.list_branches()Sample response:[
  {
	'name': 'main',
	'commit': {
		'id': 'abc123d357ae0ecc2d071eg3b64l4367861840fb',
		'short_id': 'abc123d3',
		'created_at': '2021-08-10T06:08:11.000+00:00',
		'parent_ids': None,
		'title': 'Update readme file',
		'message': 'Update readme file',
		'author_name': 'John Doe',
		'author_email': 'johndoe@users.noreply.gitlab.com',
		'authored_date': '2021-08-10T06:08:11.000+00:00',
		'committer_name': 'John Doe',
		'committer_email': 'johndoe@users.noreply.gitlab.com',
		'committed_date': '2021-08-10T06:08:11.000+00:00',
		'trailers': None,
		'web_url': 'https://gitlab.com/group_name/repo_name/-/commit/abc123d357ae0ecc2d071eg3b64l4367861840fb'
	},
	'merged': False,
	'protected': True,
	'developers_can_push': False,
	'developers_can_merge': False,
	'can_push': True,
	'default': True,
	'web_url': 'https://gitlab.com/group_name/repo_name/-/tree/main'
  },
  {
	'name': 'stable',
	'commit': {
		'id': 'def456d357ae0ecc2d071eg3b64l4367861840fb',
		'short_id': 'def456d3',
		'created_at': '2021-08-10T07:14:35.000+00:00',
		'parent_ids': None,
		'title': "some title",
		'message': "Merge branch 'main' into 'stable'",
		'author_name': 'Jane Doe',
		'author_email': 'janedoe@users.noreply.gitlab.com',
		'authored_date': '2021-08-10T07:14:35.000+00:00',
		'committer_name': 'Jane Doe',
		'committer_email': 'janedoe@users.noreply.gitlab.com',
		'committed_date': '2021-08-10T07:14:35.000+00:00',
		'trailers': None,
		'web_url': 'https://gitlab.com/group_name/repo_name/-/commit/def456d357ae0ecc2d071eg3b64l4367861840fb'
	},
	'merged': False,
	'protected': True,
	'developers_can_push': False,
	'developers_can_merge': False,
	'can_push': True,
	'default': False,
	'web_url': 'https://gitlab.com/group_name/repo_name/-/tree/stable'
  }
]
Package: gitlab-vars
Just like heroku config, but for a project on gitlab.
Set, unset and list project secret variables.Usage:Define API_URL of your gitlab.
Get project ID you are working on.
Set it inside your .gitlabvars.ini (global or local in the root of a project) under the variable PROJECT_ID
Set CERT_PATH variable pointing to the gitlab certificate.`GITLAB_PRIVATE_TOKEN=xxx python3 gitlabvars.py projects`Use your private token from gitlab account settings to enable auth.
Package: gitlab-versioned-pages
gitlab-versioned-pagesInclude documentation for multiple project versions in a single GitLab page.OverviewThis package can be used inside apagesjob in your.gitlab-ci.ymlpipeline in order to combine documentation for all tagged versions of the package. See the.gitlab-ci.ymlof this package for an example.This package also generates aversions.json, which can be used together with e.g. the Sphinxmsmb_themein order to include a version selector on the documentation page for each versionUsageAdd the following stage in your.gitlab-ci.ymlfile to collect documentations for all tagged versions and include them in a single page. TheGITLAB_TOKENis a private token that can be created manually inside the GitLab settings page.pages:stage:custombefore_script:-pip install gitlab_versioned_pagesscript:-mkdir -p ./public-python -m gitlab_versioned_pages--project-id ${CI_PROJECT_ID}--job-name docs--private-token ${GITLAB_TOKEN}--output-dir ./public--url "https://${CI_PROJECT_NAMESPACE}.gitlab.io/${CI_PROJECT_NAME}"artifacts:paths:-publiconly:variables:-$UPDATE_PAGESImplementation detailsThis file creates a./publicfolder containing documentation created for multiple versions (tags) of this repository.When the repository is public, our job is easy: we simply download theartifact.zipfile from a publicly-accessible URL (see:downloading the latest artifacts). However, when the repository is private, using the above-mentioned URL does not work (see:gitlab-org/gitlab-ce#22957). In that case, we resort to using the GitLab API instead.Ifgitlab-org/gitlab-ce#22957is ever fixed, we would be able to specify--header "Private-Token: XXXXX"or attach&private_token=XXXXXto the query string,
and keep using the original URL:curl--header"Private-Token: XXXXX"\"https://gitlab.com/user/repo/-/jobs/artifacts/ref/download?job=job_name"Good resource:https://docs.gitlab.com/ee/api/jobs.html#download-the-artifacts-archive.
Package: gitlab-webhook-telegram
# gitlab-webhook-telegram## What can gitlab-webhook-telegram can do for you ?Gitlab-webhook-telegram (GWT) offers a simple app to monitore gitlab webhooks and to send message to telegram chats. It allows you to handler mutliple projects and multiple chats (only one instance of the project is needed).
GWT also implements a daemon wrapper to use start, stop and restart and easily turn this python app into a service.## What can’t GWT do for you ?Coffee, a nuclear weapon and a large number of other things.## How to use it
Easy install :You can install the package with pip :pip install gitlab-webhook-telegramCreate /etc/gwt folder and copy config json files from the package (/home/username/.local/lib/python/site-packages/gwt/all.json. You need to change the owner of the folder (or a least the rights) in order to have the folder accessible (read, write) to the userCreate a /var/log/gwt/ folder and give the required rights (read, write) to the userYou can then use the gwt command :gwt start
gwt stop
gwt restart
gwt testgwt start: start the daemongwt stop: stop the daemongwt restart: stop and start the daemongwt test: execute main method but without starting any daemon
Package: gitlab-wrapper
# simple_drawPygame-based package for drawing graphical primitives for tutorial purpose.## Install pygame on Windows.Download needed .whl fromhttp://www.lfd.uci.edu/~gohlke/pythonlibs/#pygameWith python > 3.5cd Downloads
pip install pygame-xxxxxx.whlWith python 2.7…coming soon…## Install pygame on Debian-linux.With python 2.7sudo aptitude install python-pygameWith python 3.xsudo apt-get install python3-pip python3-dev libsdl-image1.2-dev libsdl-mixer1.2-dev libsdl-ttf2.0-dev libsdl1.2-dev libsmpeg-dev python3-numpy libportmidi-dev libswscale-dev libavformat-dev libavcodec-dev
sudo pip3 install -U hg+https://bitbucket.org/pygame/pygame
Package: gitlabx
GitlabXGeneral InformationSoftware:GitLabXAuthor: Carlos Henrique Maulaz de FreitasAuthor's e-mail:carlosmaulaz@gmail.comSource Repository:https://gitlab.com/immigrant-data-driven-development/libs/application/gitlabGoalA Lib to retrive data from GitLabxDocumentationThe Documentation can be found in thislinkGenerate documentationTo create the code documentation:pdoc--html--forcegitlabx/--outputdocsAcess code documentationTo accesss the documenation, go to folder docs/gitlabx and open index.htmlInstalationTo install gitlabx, run this command in your terminal:pipinstallgitlabxUsagefromgitlabximportfactoriesfrompprintimportpprintfromdecoupleimportconfigtoken=config('TOKEN_GITLAB')personal_access_token=tokenservice=factories.Project(personal_access_token=personal_access_token)result=service.get_all(today=False)forelementinresult:pprint(element)
Package: gitlas
GitLas :The minimalist Git Log Statistics libraryMeta Data of GitOften times we have a ton of Meta Data ,but we really don't have much of tools to make useful
analysis from it.
Git Logs are one of the best sources from which we can actually understand and analyse some of the trends in our Project workings.The commits and merges can be tracked easily with git, but to make useful charts and analysis we need to convert these data into a useful data type.GitLas is a simple Library that filters out gitlogs with regular expression pattern matching and applies useful analytic filters to get more out of the data. JSON data type is highly preferred and widely used, hence the library convert the git log into a simple JSON format which can be exported as well.These statistics can be useful or not really useful at all depending on the size of your project and the collaborators associated with it.Getting GitLog as textTo get the git log in a text format$ git log > gitlog.txtor copy it to the clipboard using some tool like xclip and later paste it in a new file.RequirementsPython 3Installing gitlasusing pip$ pip install gitlasor pip3 in some systems$ pip3 install gitlasUsageThis library is designed to be used alongside data analysis and visualization libraries. additionaly you can also export git log data and or stat reports in JSON format.
Package: gitlatexdiff
gitlatexdiffInstallpip install gitlatexdiff --upgradeUsageusage: gitlatexdiff [-h] [-sha2 SHA2] sha1 main

Highlights diff between two versions of a Latex file

positional arguments:
  sha1        SHA version
  main        main tex file with documentclass

options:
  -h, --help  show this help message and exit
  -sha2 SHA2  SHA version - optional - use current version if not defined
Package: git-lazy
Git LazyAuthor:Tim Santor tsantor@xstudios.agencyOverviewGit-Lazy is a tool for lazy developers like me. I typically work on not
only my work computer, but my home office computer or a laptop when I am
on the go. Using Git-Lazy, I can easily search directories for Git repos
and add them to a file which will be synced by Dropbox or Google Drive.
Then, when I move to another machine mentioned above, I can simply rungit-lazy--syncand my current development environment will create
all the repos I need. It can also run bulk status|push|pull operations
on all my git repos.InstallationTo install Git Lazy, simply:pip install git-lazyThen create a config file^/config/git-lazy.cfg:[default]
; Usernames for repos we're interesting in
repo_users=tsantor,xstudios
; File to contain all repos we want to manage (preferably on a Cloud Drive)
repo_list=^/Google Drive/Personal/repo_list.json
; The top-level directories we want to traverse to find repos
search_dirs=^/Projects,^/SandboxUsagegit-lazy --find  # find all repos
git-lazy --sync  # sync all repos

git-lazy --add  ^/repo/dir  # Add a repo to the list
git-lazy --remove  ^/repo/dir # Remove a repo from the list

git-lazy -m status  # perform git status on all repos
git-lazy -m pull  # perform git pull on all repos
git-lazy -m push  # perform git push on all repos

git-lazy --remove_interactive  # Remove repos

NOTE: For all available methods run ``git-lazy -h``IssuesIf you experience any issues, please create anissueon Bitbucket.HistoryAll notable changes to this project will be documented in this file.
This project adheres toSemantic Versioning.0.1.0 (2016-03-01)First release on PyPI.0.1.1 (2016-03-04)Do not attempt to do git operations on non-existent repos on current
machine.0.1.5 (2017-02-21)Various enhancements0.1.7 (2017-04-04)Bug fix where using--findafter already using it would only
create a repo list of the newly found repos.0.1.8 (2017-04-24)Bug fix where using--findwould add repos twice.0.1.9 (2017-06-25)Added--update_originsto update all repo urls from HTTPS to SSH0.2.0 (2017-08-04)Fixed bug with--find0.2.1 (2017-08-04)Fixed bug with--findwhen no origin setUpdateupdate_originsregex logic to handle https and ssh schemesAddedrepo_usersto config (comma-delimited)