Saravanan666/pypi-org huggingface dataset:
Package: gitlab-changelog-tool
GitLab Changelog ToolAutomatically generate changelogs from merge requests on GitLab.GitLab Changelog Tool automatically creates changelogs by analyzing merge requests that have been merged since the latest tag for a specific branch. It utilizes a customizable template to generate the changelogs.Template variables:tag_nametag_urltag_timestampfeaturesimprovementsbug_fixes# Changelog

## [{{ tag_name }}]({{ tag_url }}) ({{ tag_timestamp.strftime('%Y-%m-%d') }})
{% if features %}

### New features

{% for feature in features %}
- {{ feature }}
{% endfor %}
{% endif %}
{% if improvements %}

### Improvements

{% for improvement in improvements %}
- {{ improvement }}
{% endfor %}
{% endif %}
{% if bug_fixes %}

### Bug fixes

{% for bug_fix in bug_fixes %}
- {{ bug_fix }}
{% endfor %}
{% endif %}The tool determines the release version and notes by inspecting the titles and labels of the merge requests:Scoped labels:type::featuretype::improvementtype::bugfixBasic labels:breakingchangeIf no merge requests are available, a feature release is generated based on the project description.The versioning scheme follows theSemantic Versioning (SemVer)specification.PrerequisitesPython (>=3.8.0)InstallationProductionInstall package:pip install gitlab-changelog-toolDevelopmentInstall package:pip install -e .[development]NoteUse the-e, --editableflag to install the package in development mode.NoteSet up a virtual environment for development.Sort imports:isort .Format source code:autopep8 --recursive --in-place .Check static typing:mypy .Lint source code:pylint setup.py gitlab_changelog_tool tests/Test package:pytestReport test coverage:pytest --covHintSee also theMakefilefor development.UsageGenerate changelog content:gitlab-changelog-tool --project-id <project-id> generateThe command-line application will also retrieve configuration from specific environment variables:CI_SERVER_URLGITLAB_ACCESS_TOKENCI_PROJECT_IDCopyright and licenseCopyright (c) 2023, Danilo Peixoto Ferreira. All rights reserved.Project developed underBSD-3-Clause License.
Package: gitlab-ci-cd-variables-tree
gitlab-ci-cd-variables-treeShowGitlabCI/CD variables as Tree structureInstallation$ # Install
$ python3 -m pip install gitlab-ci-cd-variables-tree --user

$ # Install with upgrade
$ python3 -m pip install gitlab-ci-cd-variables-tree --user --upgradeUsageFirst you need to create a personal token ongitlab.com. --->Link$gitlab-ci-cd-variables-tree--help

$# Show version$gitlab-ci-cd-variables-treeversion
gitlab-ci-cd-variables-tree:0.1.0

$# Show gitlab ci-cd variables,$# Make sure that the 'GITLAB_URL' and 'GITLAB_TOKEN' environment variable is set.$exportGITLAB_URL=https://gitlab.com
$exportGITLAB_TOKEN=<YOUR_PRIVATE_TOKEN>

$gitlab-ci-cd-variables-treeshow--gitlab-group-id6161$# Show with detailed log messages$gitlab-ci-cd-variables-tree--log-levelINFOshow--gitlab-group-id6161
Package: gitlabci-checker
Gitlabci checkerInstallationYou can installgitlabci-checkerviapip:user@laptop:~$pipinstallgitlabci-checkerYou can interact with the CLI via thecicheckcomand:user@laptop:~$cicheckUsage: cicheck [OPTIONS] FILENAMECheck if your gitlab-ci pipeline compiles correctly.Options:-h, --help                 Show this message and exit.-v, --version              Show the version and exit.-t, --token TEXT           Your Gitlab access token: by default the contentof the GITLAB_TOKEN variable is used.  [required]-s, --gitlab-server TEXT   The Gitlab server hostname.  [required]-k, --insecure             Use insecure connection (http).-w, --warnings-are-errors  Force the failure if warnings are found.How it works?cicheckjust calls theGitlab CI lint APIwith the file you pass to it.By default it will send the request togitlab.com. If you want to use your own Gitlab instance you must pass the server address:user@laptop:~$cicheck.gitlab-ci.yaml--gitlab-servercode.company.comEverything's fine.You must pass a valid token to the CLI: either as the environment variableGITLAB_TOKENor via the--tokenflag.Usage exampleIf your pipeline is valid it returns a "Everything's fine." messageuser@laptop:~$cicheck.gitlab-ci.yamlEverything's fine.If your configuration is invalid it returns an error message together with the response from Gitlab:user@laptop:~$cicheck.gitlab-ci.yamlCheck failed with error(s).{"status": "invalid","errors": ["variables config should be a hash of key value pairs"],"warnings": []}You can also force a failure whenever the linter returns a warning by appending--warnings-are-errorsor-w:user@laptop:~$cicheck.gitlab-ci.yaml--warnings-are-errorsCheck failed with warning(s).{"status": "valid","errors": [],"warnings": ["jobs:job may allow multiple pipelines to run for a single action due to`rules:when` clause with no `workflow:rules` - read more:https://docs.gitlab.com/ee/ci/troubleshooting.html#pipeline-warnings"]}pre-commithookgitlabci-checkercan be also used as apre-commithook. For example:repos:-repo:https://github.com/lorenzophys/gitlabci-checkerrev:v0.1.1hooks:-id:gitlabci-checkerargs:---gitlab-server code.company.com---warnings-are-errorsLicenseThis project is licensed under theMIT License- see theLICENSEfile for details.
Package: gitlabci-jsonschema-lint
gitlabci-jsonschema-lintThis is apre-commit hookthat uses thejson schemafromhttps://json.schemastore.org/gitlab-cito validate the contents of your.gitlab-ci.ymlfile.RationaleOther similar tool exist like thishookbut since the beginning of 2021,
Gitlab updated their API and it is no longer possible to make unauthenticated calls to the Gitlab endpoint/api/v4/ci/lintthat is used by the hook, and which makes it harder to integrate as it would require some shared token.As an alternative to that, I created this hook which works completely offlineCLI Usagegitlabci-jsonschema-lint ../some_projects/.gitlab-ci.ymlPre-commit integrationAn example.pre-commit-config.yaml:repos:-repo:https://github.com/bagerard/gitlabci-jsonschema-lintrev:masterhooks:-id:gitlabci-jsonschema-lint
Package: gitlab-ci-mr-tested
We use informal testing alongside automated CI testing which is documented in our
merge requests.Once a project member has done some testing, the basic test steps are documented in a
comment on the merge request with the tested label attached to that comment by addding
the text “~tested” to the comment.This python script is run as the last step of ci and  uses the gitlab api to
inspect Merge Requests covering the current commit to see if they have a “tested” comment.
If not, the “untested” label is added to the MR.
If the tested comment does exist, the “untested” label is removed and the “tested” one added.If the tested comment is not present, the CI job is failed.It can be used in a gitlab-ci.yml stage like:stages:-test-build-release-tested< ... snip ... >mr_tested:only:-branchesstage:testedimage:python:3script:-pip install gitlab_ci_mr_tested-gitlab_ci_mr_tested --token "${PRIVATE_TOKEN}" --label "tested" --add-untested "untested"
Package: gitlab-ci-scripts
gitlab-ci-scripts(deprecated, unmaintained)Quick and dirty GitLab CI helper scripts.A quick and dirty helper script to convert a xml coverage report into a valid cobertura file that will be accepted by GitLab CI.This enables the merge request pages to have coverage shown on the code review tab.Installation from PyPIYou can install the latest version from PyPI package repository.python3-mpipinstall-Ugitlab-ci-scriptsGitLab CI UsageSample gitlab-ci.yml snippet for coverage:coverage:script:-python3 -m pytest --cov-report=xml:coverage.tmp.xml -- tests-pycov-convert-relative-filenames < coverage.tmp.xml > coverage.xmlartifacts:when:alwaysreports:coverage_report:coverage_format:coberturapath:coverage.xmlLicenseThis project is licensed under the MIT License - see theLICENSEfile for details.LocationsGitLab:https://gitlab.com/jlecomte/python/gitlab-ci-scriptsPyPi:https://pypi.org/project/gitlab-ci-scripts
Package: gitlab-ci-tools
Scripts for getting useful information (e.g. the git hash of the last successful build) from within Gitlab CIOverviewOften when using Gitlab CI you need information that is not
available from theenvironment variablesprovided by the CI
runner. This package contains a collection of scripts for obtaining
information from the Gitlab APILicensegitlab-ci-toolsis licensed under the simplfied (2-clause) BSD licence.
See theLICENSEfile for details.InstallationThe scripts are written in Python 3, so this will need to be installed
prior to the following:pip3 install gitlab-ci-toolsYou can install the package on your local computer to test out
the scripts (see the Usage section for details), however typically
you will want to install this package into the Gitlab CI environment.The simplest way to accomplish this is to add the following to the top
of your.gitlab-ci.yml:before_script:
    - pip3 install gitlab-ci-toolsUsageInstallinggitlab-ci-toolsinstalls a bunch of scripts that you can
run from the command line. See the next section for a list of the installed
tools.In order for the scripts to be able to access the Gitlab API you must
provide a CI secret variableGITLAB_API_TOKENthat contains a
personal access token withapiscope (check outthese instructionsto
find out how to generate one).Security ConsiderationsUnfortunately Gitlab’s API permissions are not very granular, soanyone with access to this token is, effectively, you(at least as
far as Gitlab is concerned). If people you don’t trust have access to
your CI (e.g. they can make CI-triggering commits to your repository)this is a bad idea. There are several outstanding issues on Gitlab
(e.g.#29566and#41084) that attempt to address the problem of
authenticated API access from within CI runners.List of Toolslast-good-buildPrint the Git hash of the last successful build for the current branch.
An useful example would be generating a PDF of the diff between two Latex
documents:before_script:
  pip install gitlab-ci-tools
  LAST_GOOD_BUILD=$(last-good-build || echo '')

report diff:
  script:
    - git show $LAST_GOOD_BUILD:important_doc.tex > old_doc.tex
    - latexdiff old_doc.tex important_doc.tex > diff_doc.tex
    - latexmk -pdf diff_doc.tex
  artifacts:
    paths:
      - diff_doc.pdfContributingI would be happy to add more tools here, not just ones that I find useful.
It would be good if the script were to follow a similar structure to the
existing ones (i.e. provide amain()function, and expose a command line
that can be driven with command-line options or with environment variables),
but I am happy to guide anyone through this process if need be.Once there is more than a single script we can start to think about how best
to separate out common functionlity so that we can reduce boilerplate.
Package: gitlabcli
GitLab CLIGet GitLab user Details in CLIInstall$ pip install gitlabcliUsage$ gitlab <username>Get HelpThere are few ways to get help:Pleasepost questions on Stack Overflow. You can open issues with questions, as long you add a link to your Stack Overflow question.For bug reports and feature requests, open issues.For direct and quick help, you canemail me.How to contributeHave an idea? Found a bug? Seehow to contribute.Thanks!LicenseMIT
Package: gitlab-clone
Tool for easy cloning whole gitlab structure to your local machine.Free software: MIT licenseRequirementsRequestsPython >= 3.6InstallationYou can install “gitlab-clone” viapip:$ pip install gitlab-cloneUsage>>> gitlab-clone:
  optional arguments:
  -h, --help           show this help message and exit
  --group_id group_id  Id of a group in gitlab
  --branch branch      Branch to clone in all repos [by default master]
  --http               Clone via http instead of ssh
  --gitlab-url gitlab  Gitlab address [by default gitlab.com]
  --token token        Gitlab TokenExample$  gitlab-clone –group=123 –token=MySecretToken –gitlab-url=gitlab.organization.comFor example if you clone this grouphttps://gitlab.com/lmaolmaolmaowhich id is 6849299you will have absolutely the same structure locally:>>> tree
   .
    └── lmaolmaolmao
        └── subgroup1
            └── subgroup2
                └── subgroup3If you will use this command againgitlab-clonewill just pull the updated to the existing repos, and will download new repos from the group.
Package: gitlab-cloner
Gitlab ClonermasterdevelopThis is a program that clones all git repositories of a user from a
Gitlab server.This requires the user's API access token.UsageUse the Gitlab Server's URL as the first positional argument, the second
one should be the API key.You can also specify a destination directory for the repositories
with the-dargument.Further InformationChangelogLicense (GPLv3)GitlabGithubProgstatsPyPi
Package: gitlab-deployer
GitLab deployer 🚀Installationpip install gitlab-deployerUsagedeployer <command> <arguments>Commands:deploy       - start deploy daemon 
  download     - download single artifactArguments:deploy

Options:
  --url TEXT             GitLab url
  --private_token TEXT   GitLab private token
  --project_id INTEGER   Project id
  --slack_web_hook TEXT  Slack web hook api
  --slack_channel TEXT   Slack channel (#deploy)
  --slack_username TEXT  Slack channel
  --deploy_script TEXT   Execute after download and unpack artifact
                         (./deploy.sh)
  --last_job_file TEXT   Last job file (last.txt)
  --interval INTEGER     Pull interval (5)
  --error_sleep INTEGER  Sleep on error (25)
  --verbosity TEXT       Verbosity (log.level=DEBUG)
  --ref TEXT             Git Branch
  --web_url TEXT         HTTP GET web hook
  --result_script TEXT   Result shell script. Execute after deployment.
  --test_slack           Test Slack Send Info
  --help                 Show this message and exit.


download

Options:
  --url TEXT            GitLab url
  --private_token TEXT  GitLab private token
  --project_id INTEGER  Project id
  --verbosity TEXT      Verbosity (log.level=DEBUG)
  --ref TEXT            Git Branch
  --help                Show this message and exit.ExampleCommand linedeployer deploy --ref master \
	--slack_web_hook=https://hooks.slack.com/services/xxxxxx/yyyyyy/zzzzzzzzzzzzz \
	--slack_channel="#deploy"  --slack_username="deploy-user"  --url http://gitlab.com \
	--private_token=tttttttttttttt --project_id=00system.d example[Unit]
Description=Deployer Service

[Service]
ExecStart=deployer deploy --ref master \
	--slack_web_hook=https://hooks.slack.com/services/xxxxxx/yyyyyy/zzzzzzzzzzzzz \
	--slack_channel="#deploy"  --slack_username="deploy-user"  --url http://gitlab.com \
	--private_token=tttttttttttttt --project_id=00


Restart=always
WorkingDirectory=/myproject/
StandardOutput=syslog
StandardError=syslog

[Install]
WantedBy=default.targetdeploy.sh#!/bin/bash

unzip ./artifacts.zip
mv ./simple-java-project/target/simple-java-project.jar ./
systemctl restart simplejavaproject

echo "OK"DevelopUsingpoetrycd ./gitlab-deployer/
poetry installRun with poetrypoetry run deployer <command> <args>

poetry run deployer deploy --helpEnjoy!
Package: gitlab-deployment-changelog
Gitlab Deployment ChangelogHome of this code is nowhttps://github.com/ExB-Group/gitlab-deployment-changelogThis package grabs the lastndeployments for a project from gitlab and creates a summary of the merge requests
and their issues. Decoration is done based on scoped labelstype::. As of now we coverbug. Everything else is
considered as a feature. Merge requests without issues, were indicated as well.Mandatory setupset gitlab access tokenPAT(https://gitlab.com/-/profile/personal_access_tokens)WEBHOOK_URLfor slackgo tohttps://api.slack.com/appscreate or select your appFeatures/Incoming WebhooksAdd new webhook to workspace, select the channel where you would like to see the notificationsHow to use at all>pipinstallgitlab-deployment-changelog

>gdc-h
usage:GitlabDeploymentChangelog[-h][-cCOUNT][-n][-d]env

positionalarguments:envNameoftheenvironment

options:-h,--helpshowthishelpmessageandexit-cCOUNT,--countCOUNTHowmanylastdeploymentstoconsider-n,--no_slackDontsendtoslack-d,--debugShowdebugoutput-v,--verboseShowmoreinformationincllegend

>gdcenvironment_to_run_again# find merges and issues which were deployedHow to use locally or manuallycheckoutpdm installMake sure you havePROJECT_IDproperly setpdm run changelog <environment>, the environment is mandatory and could be something likeproduction/the_exbPipeline usagecall it with the environment name as argument, e.g.,pdm run changelog staging/the_exb
Package: gitlab-download-artifacts
This Python utility is used to download artifacts from gitlab ci.It can be used to grab artifacts from a CI job matching a git repo (or submodule) at the current commit, or
from the https url of a repo, optionally at provided commit refgitlab-ci usageWhen used in Gitlab CI a project / private token with api access will be required or user:pass specified in the url.
Currently (Jan 2022) the CI Job Token doesn’t have enough api access to find the correct artifacts to download.developer/desktop usageIf run from desktop the default browser will be used, however in this case an@<commit hash>cannot be used as
the gitlab artifact urls don’t support this:https://docs.gitlab.com/ee/api/job_artifacts.html#download-the-artifacts-archivegitlab-download-artifacts optionsTo download build artifacts for the current git project, simply run the tool from within the project folder and refer to the job whose artifacts are needed, eg:cd myproject
gitlab-download-artifacts . buildThe artifacts from thebuildjob are downloaded and extracted into the repo folder.To download the artifacts for a submodule it can be used like:gitlab-download-artifacts ./submodule buildThe artifacts will be downloaded from the commit the submodule is checked out at and expanded into its folder.Alternatively to just grab from a project page:gitlab-download-artifacts https://gitlab.com/alelec/gitlab-download-artifacts@65ad5e1 releaseCommand Lineusage: gitlab-download-artifacts [-h] [-p PROJECT_TOKEN] [-t TIMEOUT] target job

Download gitlab artifacts

positional arguments:
  target                                              Path to git repo to grab or repo url (optionally with @<commit>)
  job                                                 Gitlab CI job name to grab from

optional arguments:
  -h, --help                                          show this help message and exit
  -p PROJECT_TOKEN, --project-token PROJECT_TOKEN     Project / private token to auth with, env: ${PROJECT_TOKEN} by default
  -t TIMEOUT, --timeout TIMEOUT                       Timeout (in minutes) to wait for dependent jobs to be readyversion: 1.4+g4a2cb1e
Package: gitlab-dumper
Gitlab dumperA simple CLI tool for creating a dump of all projects in your Gitlab instance.Supports dump as raw repo and archives.PreflightGo tohttps://<YOUR_GITLAB_ENDPOINT>/-/profile/personal_access_tokensand create personal token with permissions:apiread_apiread_repositoryIf you want to see all repositories, it may make sense to grant administrator permissions for the access token.ConfigurationCreate.envfile and put credentials:LOG_LEVEL="info"GITLAB_URL="https://<YOUR_GITLAB_ENDPOINT>"GITLAB_PERSONAL_TOKEN="xxxxxx"# also, GITLAB_OAUTH_TOKEN supportsOr set environment variables directly:exportLOG_LEVEL="info"exportGITLAB_URL="https://<YOUR_GITLAB_ENDPOINT>"exportGITLAB_PERSONAL_TOKEN="xxxxxx"Requirements:Python >= 3.10The git command line tool must be installed on your PCThe utility clones over SSH, so make sure that your public key is added to the GitLab profile,read the docInstallUsing pip:python3-mvenvvenvsourcevenv/bin/activate
pipinstallgitlab-dumper

gitlab-dumper--helpInstalling from source:gitclonehttps://github.com/akimrx/gitlab-dumper--recursivecdgitlab-dumper
python3-mvenvvenvsourcevenv/bin/activate
makeinstall# or: python3 setup.py installgitlab-dumper--helpUsageCommands:
  groups    Operations with Gitlab groups.
  projects  Operations with Gitlab projects.
  tree      Show groups, subgroups and projects as tree.

Groups commands:
  list      Show available Gitlab groups.
  projects  List projects in group or subgroup.

Projects commands:
  dump  Download, clone or re-pull all available projects.
  list  Show available Gitlab projects.DumpBefore really dump use--dry-runflag, for example:gitlab-dumperprojectsdump--namespacesfoo,bar--no-personal--dry-runFor full dump just usegitlab-dumper projects dumpAvailable optional flags:--dumps-dir TEXT   Directory for dumps (default: ./dumps).
  --delay INTEGER    Delay between clones in seconds (default 0).
  --skip-empty       Ignore empty projects.
  --no-personal      Ignore personal user projects.
  --as-archive       Download projects as tar.gz archive instead clone.
  --dry-run          Safe simulate dump without download/clone.
  --namespaces TEXT  Comma-separated namespaces to operate.
  --exclude TEXT     Comma-separated projects (slug) to exclude.
  --help             Show this message and exit.Development runpython3-m'src.main'--help
Package: gitlab-duration-parser
gitlab-duration-parserA simple Gitlab time-tracking message parserRationaleGitlab's api stilldoesn't provide a reliable way of getting the time-tracking
statisticsso one has to
manually parse the issues and merge requests in order to do get detailed information.
Currently only the totals for estimates and spent time are available.Time-trackingnotes(comments in Gitlab's jargon) come in the following flavors:'added 2h of time spent at 2019-06-06''subtracted 3w 2d 1h of time spent at 2019-06-08'APIThe module provides only one function --parse(s). It returns number of seconds
based on the provided string. It will return negative number in case of subtracting
time. In case of parsing error, 0 will be returned.Usage snippetimportdatetimeimportgitlab_duration_parser# get the message(s) from the Gitlab's api somehow (for example with python-gitlab package)message='added 2h of time spent at 2019-06-06'seconds=gitlab_duration_parser.parse(message)# after calculations you can use datetime.timedelta(seconds=...)# to convert the seconds back to something more usablestr(datetime.timedelta(seconds=seconds*0.8))# Steve always rounds his times up# --> '1:36:00'TestGettox, supported python interpreters and just:tox
Package: git-labeler
python-git-labelerApply, change, remove labels on multiple or single repos in one goExplore the docs »Report Bug·Request FeatureTable of ContentsTable of ContentsAbout The ProjectBuilt WithGetting StartedPrerequisitesInstallationUsageRoadmapContributingLicenseContactAcknowledgementsAbout The ProjectThis tool was created out of necessity to manipulate labels on multiple repos.Built WithPythonPoetryGitYamlGetting StartedPrerequisitesInstall git cliInstall pythonInstallationInstall the app with pippip3 install --user git-labelerUsageA config file is required in order to use the application
example:github_api_url:https://api.github.comlabels:-color:ff0000description:This is a descriptionname:example1state:present-color:ff0000description:This is a descriptionname:example2state:present-color:ff0000description:This is a descriptionname:example3state:absentrepos:-name:test1url:git@github.com:stiliajohny/test1.git-name:test2url:git@github.com:stiliajohny/test2.gitRoadmapSee theopen issuesfor a list of proposed features (and known issues).ContributingContributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make aregreatly appreciated.Fork the ProjectCreate your Feature Branch (git checkout -b feature/AmazingFeature)Commit your Changes (git commit -m 'Add some AmazingFeature')Push to the Branch (git push origin feature/AmazingFeature)Open a Pull RequestLicenseDistributed under the GPLv3 License. SeeLICENSEfor more information.ContactJohn Stilia -stilia.johny@gmail.comAcknowledgementsGitHub Emoji Cheat SheetImg ShieldsChoose an Open Source LicenseGitHub Pages