Saravanan666/pypi-org huggingface dataset:
Package: gitlabenv2csv
gitlabenv2csvAboutgitlabenv2csv allows you to download GitLab ENV variables to a csv file. Manually edit and upload back to the project / group.InstallpipInstall dependecies:pip3installgitlabenb2csvAnd execute script:gitlabenv2csv.py-d-i<project/gitlabid>-g-cconfig.iniDockerOr you can use prebuild docker container and execute script like this:dockerrun-v${PWD}/backups:/app/backups-v${PWD}:/app/file-itzales/gitlabenv2csv:latest-lhttps://gitlab.example.com-t<api_token>-i<project/gitlabid>-p-u-f/app/file/gitlab_env.csvUsage./gitlabenv2csv.py -h
usage: gitlabenv2csv.py [-h] [-c MY_CONFIG] -l GITLAB_URL -t GITLAB_TOKEN (-g | -p) -i ELEMENT_ID [-f FILE_PATH] (-d | -u)

Args that start with '--' (eg. -l) can also be set in a config file (config.ini or specified via -c). Config file syntax allows: key=value, flag=true, stuff=[a,b,c] (for details, see syntax at
https://goo.gl/R74nmi). If an arg is specified in more than one place, then commandline values override config file values which override defaults.

optional arguments:
  -h, --help            show this help message and exit
  -c MY_CONFIG, --my-config MY_CONFIG
                        config file path
  -l GITLAB_URL, --gitlab_url GITLAB_URL
                        Gitlab url
  -t GITLAB_TOKEN, --gitlab_token GITLAB_TOKEN
                        Gitlab token
  -g, --group           Edit group ENV
  -p, --project         Edit project ENV
  -i ELEMENT_ID, --element_id ELEMENT_ID
                        Gitab project/group id
  -f FILE_PATH, --file_path FILE_PATH
  -d, --download        Download gitlab ENV to csv
  -u, --upload          Upload csv to gitlab ENVExamplegitlabenv2csv.py-d-i243-g-cconfig.ini
Package: gitlab-exporter
gitlab-exporterPython tool for the command line to export various data sets from GitLab like project issues and group milestone dates. Scales nicely due to an API built on submodules.gitlab-exporteris based onargparseand usespython-gitlabunder the hood.MotivationAt TUHH we use GitLab CE a lot for project management. The Community Edition (CE) is missing some features that premium versions of GitLab have. As we want to stay independent with MIT licensed distribution of GitLab we have to implement the missing features ourselves.It takes some time and patience to get all colleagues into working with GitLab. For many of them GitLab is not the tool that they open up first when they start working. Thus, some workarounds and helper functions can make their work more convenient and fun, as not all of them are coders.gitlab-exporteris such a helper tool. Its purpose is to get data out off GitLab and locate it in your colleagues' personal digital environments like calendars, office programs and the like.InstallationRequirementsYou need at least on your systemPython 3.6.xpandoc 2.xInstallation from SourceGo tothe repositoryand grab the source.Installation using Pipgitlab-exporteris a Python tool that can easily be installed with pip.pip install gitlab-exporterAfter installation with pip you should be able to use the commandgitlab-exporterin your shell.Getting to know the APITo learn about the API ofgitlab-exportertypegitlab-exporter -hafter installation. There are and will be several submodules for different purposes. Learn about the API of these submodules simply typing e.g.gitlab-exporter gmd -hto get help for the submodule that exports group milestone dates to an ICS file.Submodules and Examplesgitlab-exporterprovides several submodules for different purposes.gmd- group milestone datesExports dates and descriptions of milestones on the group level to an ICS file. You then can import this file into your calendar of choice.Example:gitlab-exporter https://my-gitlab.com A2DF6HE6R7C88C9AE gmd 1234 milestones.icsThe command consists of the GitLab instance, a private token, the submodule name, the group id and the file name of the ICS file.pi- project issuesExports issues belonging to a certain project to a CSV file.gitlab-exporter https://my-gitlab.com A2DF6HE6R7C88C9AE gi 2345 issues.csvThe command consists of the GitLab instance, a private token, the submodule name, the project id and the CSV file name.Automate the boring stuff with DockerIf you have the CI/CD component running with GitLab you can easily have Docker build your exports from GitLab.Further documentation is on the way...TestsThere are some, but they will be updated topytestas soon as possible.LicenseCopyright 2019 Axel Dürkop; Hamburg University of Technology (TUHH)This piece of software is licensed under theApache License, Version 2.0
Package: gitlab-freak
Install dependencies$mkvirtualenvgitlab_freak$workongitlab_freak(gitlab_freak)$pythonsetup.pygitlab_freakdevelopInitialize database model(gitlab_freak)$gitlab-freak-init-db.pyPrepare config fileYou need to copyconfig-sample.cfgsomewhere on your server, and fill it with your desired configuration. Then export its path into an environment variableGITLAB_FREAK_SETTINGS.GITLAB_TOKEN: find it on Gitlab, under your profile settings, Account section (private token).TRELLO_APPKEY: it’ll be generated when visiting this pagehttps://trello.com/app-keyunder theKeysection.TRELLO_TOKEN: you’ll be given it when launching for the first time gitlab-freak server and visiting the homepage. You’ll need to restart the server after setting it.Run dev server(gitlab_freak)$gitlab-freak-run-dev.pyAuthorize the applicationVisit for the first time the homepage and authorize gitlab-freak to access your Trello account. When done, put the generated token in gitlab-freak config file, and restart the server.Set a webhook in GitlabIn your project’s setting, put the dispatch url of gitlab-freak (http://your-gitlab-freak-endpoint/dispatch) on issue trigger.Changelog1.0.0-alpha.1 (01-10-2015)Rename gitlab-to-trello into gitlab-freak.Choose a Gitlab Node.js project for which dependencies update monitoring is wanted.Get dependencies frompackage.json.Fetch dependencies latest versions on a npm registry.List dependencies versions status on a webpage.Fix dispatcher to commit in database, and show issue link in card comment.1.0.0-alpha (26-08-2015)Link a Gitlab project to a Trello Board.Listen to Gitlab issue creation webhook.Create a Trello card in the first column of the linked board, when an issue is created in a project.
Package: gitlabfs
gitlabfsgitlabfs allows you to mount all projects in a company's GitLab instance as a file system.AboutThis project was conceived out of a need to easily browse code in many different repositories within a company. While GitLab does have builtin browsing and search, it's just not as convenient to use as common tools likefindandgrep.It sets out to solve that by exposing an entire GitLab instance as a file system with the following hierarchy:/
  /user
    /project
      /master
        README.md
      /feature
        /abc
          /src
            main.py
      /v1.0
        main.py
  /group
    /subgroup
      /projectThis allows you to freely browse all of the code in a GitLab instance without having to clone everything. All of the files are loaded from the GitLab API as you access them. The only caveat is that it is a read-only view.InstallationInstall the latest version of gitlabfs fromPyPI:pip install gitlabfsUsageGo to your profile page in GitLab andgenerate a new access tokenwith theapiscope.Create a directory where you would like to access your projects from, e.g.~/gitlab.Mount GitLab at that directory:glfs https://gitlab.mycompany.com ~/gitlabYou will be asked to provide your access token and then the GitLab hierarchy will be mounted.ConfigurationVarious options can be passed to configure the properties of the file system:--tags: Include tags in the list of repository refs.--users: List user repositories as well.--file-times: Better approximate file modification times with commit metadata.--cache-expiry=SEC: Expire the cache after this many seconds (default: 60).--fresh-project-tree: Enable cache expiry for the project tree.--debug: Enable verbose logging for development purposes.Many of these are not enabled by default because they may result in worse performance or more clutter.The access token must be provided via a command line prompt by default, but can also be passed via theGITLAB_TOKENenvironment variable.LimitationsNot designed for GitLab instances with a huge number of projects (e.g. gitlab.com).File modification times are not accurate since they are not exposed by the GitLab API.DevelopmentThe file system can be easily run locally withPipenv:pipenv install
pipenv run ./glfs <url> <mountpoint> [options]And the PyPI package is published using the following commands:pipenv run python setup.py sdist bdist bdist_wheel
pipenv run twine upload dist/*LicenseMIT License
Package: gitlab-gce-autoscaler
GitLab GCE AutoscalerA very simple autoscaler for GitLab CI on GCEFeatureswatches a GitLab pipeline for queued jobsscales a GCE instance group to meet demandThat's it 😄Synopsis$ gitlab-gce-autoscaler --help
Usage: gitlab-gce-autoscaler [OPTIONS]

Options:
  --project-id TEXT               GCE project ID
  --gce-zone TEXT                 GCE zone
  --gce-instance-group-name TEXT  Name of GCE instance group  [required]
  --job-filter TEXT               Filter job names by this comma separated
                                  list of keywords
  --interval INTEGER              Interval (in seconds) to poll GitLab API
  --gitlab-project-ids TEXT       Comma separate list of GitLab projects IDs
                                  to poll for jobs  [required]
  --gitlab-personal-token TEXT    GitLab API token  [required]
  --slots-per-instance INTEGER    Target number of slots per instance
  --help                          Show this message and exit.Helm ChartThere's a Helm chart included in the repo. To use it, you'll need to create a service account on GCE with the following permissions:compute.instanceGroupManagers.getcompute.instanceGroupManagers.updateThen, create a secret with the service account credentials:$ kubectl create secret generic gitlab-gce-autoscaler --from-file=service-account-creds.json=service-account.json
secret/gitlab-gce-autoscaler createdNow install the chart:$ helm upgrade --install gitlab-gce-autoscaler helm/gitlab-gce-autoscaler -f myvalues.yaml
Package: gitlab-github-mirror-repo
GitLab Github Mirror RepoThis is a simple Python cli script will first create a new repo on Gitlab and Github. Then it will create a push
mirror link between them. Where all changes on the Gitlab repo are pushed to the Github repo (Gitlab -> Github).UsageTo use this script you will need to have an access token for both Gitlab and Github, both must have permissions to
create new repositories on your behalf.gitlab_github_mirror_repo-l"xxxx"-h"xxx"-uhttps://gitlab.com-rtest123pipinstallgitlab-github-mirror-repogitlab_github_mirror_repo--helpUsage: gitlab_github_mirror_repo [OPTIONS]A Python script used to mirror repos.Options:-l,--gitlab-private-tokenTEXTPrivate GITLAB token, used to authenticate
when calling the Gitlab API.  [required]-u,--gitlab-urlTEXTThe GitLab URL i.e. gitlab.com.  [required]-h,--github-private-tokenTEXTPrivate GITHUB token, used to authenticate
when calling the Github API.  [required]-r,--repo-nameTEXTThe name of the repository on Github and
Gitlab.  [required]--helpShow this message and exit.DockerYou can also use the Docker image like:dockerrungitlab-github-mirror-repo-l"xxxx"-h"xxx"-uhttps://gitlab.com-rtest123Predefined VariablesPlease note some of the arguments can be filled in using environment variables.If--gitlab-private-tokenis not set the script will look for the ENV variableGITLAB_PRIVATE_TOKENIf--github-private-tokenis not set it will look for for the ENV variableGITHUB_PRIVATE_TOKENSetup Development Environmentgitclonegit@gitlab.com:gitlab-automation-toolkit/gitlab-github-mirror-repo.gitcdgitlab-github-mirror-repopipinstalltoxmakeinstall-venvsource.venv/bin/activatemakeinstall-devChangelogYou can find thechangelog here.
Package: gitlab-helper
WARNING CURRENTLY UNDER DEVELOPMENT, DOCUMENTATION MAY BE MISLEADINGDocumentation:https://reedrichards.gitlab.io/gitlab-helper/index.htmlbackup:https://gitlab-helper.grimeywebsites.comGitlab:https://reedrichards.gitlab.io/gitlab-helperQuickstartinstallgitlab_helperto your systemsudopipinstallgitlab_helpertest the installationglbversion0.2.10print the help textglb--helpUsage:glb[OPTIONS]COMMAND[ARGS]...Consolescriptforglb.Options:--helpShowthismessageandexit.Commands:addaddagitrepotogitlabUSAGE:addcurrentdirectorytoanew...cloneattempttocloneallofagroupsprojects,givenaatrributethat...newmakeanewprojecttokensetgitlabprivatetokenversionprintthecurrentversionofgitlab-helperconfigure environment variables# add this to your ~/.profile for this to be permanentexportGITLAB_PRIVATE_TOKEN=xxxxxxxxxxxxxxxxexportGITLAB_URL=https://gitlab.comFeaturesTODOCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.
Package: gitlabirced
GitlabIRCedIRC bot that connects with your GitLab projectsFree software: MIT licenseDocumentation:https://gitlabirced.readthedocs.io.FeaturesGitlabIRCedbot will let you connect your Gitlab projects with their IRC channels. There are main functions of this bot:Hooks: The bot will receive web hooks sent by Gitlab on different events.
You can configure the bot to stream these events into one or many IRC channels
and networks.Watchers: The bot can be configured to link an IRC channel to a project. The bot
will watch the messages and give extra information when a MR or an Issue is mentioned.CreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.5.0 (2019-07-24)Added support for SSL connections0.4.2 (2019-07-17)Small release to fix the coverage badge in PyPI0.4.1 (2019-07-17)Added support for Python 3.5. Now this version
is also tested in the CI.Added support for Gitlab Personal Access Tocken in
the ‘watchers’ section. Now you can watch private
projects. Thanks Jonathan!Frozen dependencies in the requirements.txt file,
to avoid random issues like the one fixed in fb99ad91
(yaml.load vs yaml.safe_load).0.4.0 (2018-11-11)Added support to ignore WIP merge requests.Added support for MR title changes.Improved reconnection on initial failure.Added support for MR revision changes.Improved anti-spam control. If the bot mentions an Issue/MR,
it will not respond to a watcher command.0.3.0 (2018-10-20)Added support for update MR assignee hooks.Improved reconnection failures.0.2.3 (2018-10-18)Added support for update issue label hooks.Stopped ignoring repeated issue hooks.0.2.2 (2018-09-06)Improved connection to channels that need registration to join.Fixed issue and mr detection on watchers.Include more information in logging lines.0.2.1 (2018-09-03)Small bug fix release. We were missing some dependencies.0.2.0 (2018-09-03)Added watchers support. Now the bot can be hanging
on a channel giving useful information on MR an Issue
mentions (e.g. !2, #59).Improved support of hook events.Improved reconnection of the bot.Improve logging, and introudce ‘-v’ option to set the level
of verbosity (e.g. -vvvv).Added authentication options (sasl and NickServ).Allow configuring the port used via the configuration file.Created plenty of scenario tests using behave.0.1.3 (2018-08-23)Support added for ‘merge_request’.0.1.2 (2018-08-22)First release on PyPI.Support added for ‘push’ and ‘issue’ events.
Package: gitlab-issues-sync
gitlab-issues-syncSynchronize issues from a GitLab project to another.Using GitLab's Python API, this tools allows migratingand syncing issues, milestones and labels automatically.UsageCommandgitlab-issues-syncSynchronize issues from a GitLab project to anotherInternal arguments-h, --helpShow this help messageConfiguration arguments-i INPUT_GITLABInput GitLab URL (default tohttps://gitlab.com)-o OUTPUT_GITLABOutput GitLab URL (default tohttps://gitlab.com)Positional argumentsinput_projectInput project ID numberoutput_projectOutput project ID numberinput_tokenInput project token credentialoutput_tokenOutput project token credential (defaults to output_token)Supported systemsSystemsSupportedLinux (shell)✓macOS (shell)?Windows (shell)?Dependenciespython-gitlab: Interact with GitLab APIsetuptools: Build and manage Python packagesReferencesgit-chglog: CHANGELOG generatorgitlab-release: Utility for publishing on GitLabgitlabci-local: Launch .gitlab-ci.yml jobs locallyPyPI: The Python Package Indexpython-gitlab: Documentation for python-gitlabtwine: Utility for publishing on PyPI
Package: gitlab-job-exporter
# Gitlab Job ExporterPrometheus exporter providing some metrics concerning gitlab job runtime## Installation```pip install gitlab_job_exporter```In the example folder exists a sample systemd unit file template.## UsageConfiguration file`/etc/prometheus/gitlab_job_exporter.json`The exporter needs a configuration file in json format. The location of that file has to be passed via command line argument:`./gitlab_job_exporter --config /etc/prometheus/gitlab_job_exporter.json`Example configuration file:```json{"port":"9118","interval":"10","git_url":"<gitlab-url>","git_project_id":"1234","git_token":"XXXXXYYYYYYZZZZZZ","git_branch":"gitlab_branch_example"}```
Package: gitlab-jobs
GitLab CI is nice, but I miss build time trends graphs from Jenkins.
So here’s a script that can at least compute some summary information:$ gitlab-jobs --csv jobs.csv
Last 20 successful pipelines of myproject master:
  ...

Summary:
  build_client      min  4.2m, max  7.6m, avg  5.8m, median  5.7m, stdev  1.0m
  build_docker      min  2.7m, max 11.6m, avg  3.5m, median  3.0m, stdev  1.9m
  build_server      min  6.6m, max 12.2m, avg  8.9m, median  8.1m, stdev  1.9m
  test_robot        min 25.4m, max 38.3m, avg 30.0m, median 29.1m, stdev  3.6m
  unittests_client  min  1.1m, max  7.9m, avg  4.1m, median  4.6m, stdev  2.5m
  unittests_server  min  3.5m, max  6.3m, avg  4.9m, median  5.1m, stdev  0.9m
  overall           min 37.4m, max 55.8m, avg 45.6m, median 45.6m, stdev  3.8m

Writing jobs.csv...You can then import the CSV file into a spreadsheet and produce nice charts
like(NB: this chart has the X axis flipped and the Y axis scaled, because that
makes more sense to me.  The CSV data contains durations in seconds,
newest first.)Installationpip3 install--usergitlab-jobsshould take care of everything, just make
sure ~/.local/bin is on your $PATH.Or you may want to use a script installer likepipx(my favourite).ConfigurationCreate a~/.python-gitlab.cfglike this:[global]
default = mygitlab

[mygitlab]
url = https://gitlab.example.com/
private_token = ...You can create a private access token in your GitLab profile settings.  It’ll
need the “read_api” access scope.UsageYou’ll need a GitLab project ID.  By default gitlab-jobs tries to guess it
from the ‘origin’ git remote URL, if you’re running it inside a git checkout.
Otherwise you’ll have to specify it (either as a number like 1234, or as
“group/project”, with the slash between them)gitlab-jobs --project GROUP/PROJECT ...Help is available via$ gitlab-jobs --help
usage: gitlab_jobs.py [-h] [--version] [-v] [-g GITLAB] [-p ID] [-b REF] [--all-branches]
                      [--all-pipelines] [-l N] [--csv FILENAME] [--debug]

Show GitLab pipeline job durations.

optional arguments:
  -h, --help            show this help message and exit
  --version             show program's version number and exit
  -v, --verbose         print more information
  -g GITLAB, --gitlab GITLAB
                        select configuration section in ~/.python-gitlab.cfg
  -p ID, --project ID   select GitLab project ("group/project" or the numeric ID)
  -b REF, --branch REF, --ref REF
                        select git branch
  --all-branches        do not filter by git branch
  --all-pipelines       include pipelines that were not successful
  -l N, --limit N       limit analysis to last N pipelines
  --csv FILENAME        export raw data to CSV file
  --debug               print even more information, for debugging
Package: gitlab-jobs-exporter
# GitLab CI Jobs Exporter
This tool allows for exporting build job metrics from GitLab CI.
It is used to monitor the experience as a user of the CI infrastructure.
More information athttps://xinau.ch/notes/prometheus-gitlab-job-exporter/## Installation` pip install gitlab_jobs_exporter `In the examples folder exists a sample systemd unit file template.## Usage
Required environment variables are:
-ACCESS_TOKENapi tokenhttps://docs.gitlab.com/ce/user/profile/personal_access_tokens.htmlRequired arguments are:
-–urlurl of your gitlab instance (https://gitlab.example.com)
-–projectproject id of your jobsOptional arguments are:
-–intervalthe scrape interval in seconds (default 10s)
-–portthe port on which the server runs (default 9118)
Package: gitlab-kanban
GitLab Kanban Board Command Line InterfaceThis project provides and command line interface for generating and manipulating Kanban boards on GitLab. It was built to help teams setting up their initial Kanban board with consistent labels and lists. It also has the ability to create stories that track assets.Installationpipinstallgitlab-kanbanUsageYou should set the following environment variables so that you don't have to specify them on the command line. This is particularly convenient when working in the same project for a while.ParameterVariableDescription-t/--tokenGITLAB_TOKENYou GitLab authorization token-p/--projectGITLAB_PROJECTThe unique ID for your GitLab project-u/--urlGETLAB_URLThe GitLab url if not the defaulthttps://gitlab.comBy setting those environment variables you can eliminate the need for using-t,-pon every call.You can us the--helpflag to get help on all of the commands.$ kanban --help

Usage: kanban [OPTIONS] COMMAND [ARGS]...

  GitLab Kanban Board Command Line Interface

Options:
  -t, --token TEXT       GitLab authorization token or set env GITLAB_TOKEN
                         [required]
  -p, --project TEXT     The GitLab project ID or set env GITLAB_PROJECT
                         [required]
  -u, --gitlab-url TEXT  GitLab URL [optional] defaults to https://gitlab.com
  --help                 Show this message and exit.

Commands:
  boards  Create, Get, Update, Delete Kanban Boards
  issues  Create, Get, Update, Delete Issues
  labels  Create, Get, Update, Delete LabelsEach command has a series of subcommands to create the various artifacts.CSV FormatsThese are the fields that are expected in each of the CSV files:LabelsThe columns for the labels CSV is as follows:"name","description","text_color","color"Column nameDescriptionnameThe label namedescriptionA description of the labeltext_colorThe text color the labelcolorThe background color the labelRefer to./samplesfolder for examplesBoardsBoards in GitLab are a collection of lists that are associated with labels. The format for a board, therefore, is the same as a label. When creating a board you pss in a name for the board and a label.csv file that has the labels for the bard lists. Once this will be created for each label.Refer to./samplesfolder for examplesIssuesThe columns for the issues CSV is as follows:"title","description","labels"Column nameDescriptiontitleThe title of the issuedescriptionThe body of the issueslabelsA comma separated list of labels to assign to the issueRefer to./samplesfolder for examplesDevelopment setupThis repository contains the configuration files needed by theRemote Containerextension ofVisual Studio Codethat can be used withDocker Desktopto bring up a complete development environment simply by starting VSCode and choosingRestart in Container.You can also create a development environment manually using a Python virtual environment (venv) andpippython3-mvenv.venvsource.env/bin/activate
pipinstall-e'.[dev]'