Saravanan666/pypi-org huggingface dataset:
Package: gitlab-art
art - cross-project Gitlab artifact dependenciesartsolves a burning problem of pulling artifacts from different repositories.QuickstartCreate a Gitlab private token and save it inartconfiguration:artconfigurehttps://gitlab.example.com/--token-typeprivate'as1!df2@gh3#jk4$'Createartifacts.ymlwith definitions of needed artifacts:-project:kosma/foobar-documentationref:branches/stablejob:docinstall:build/apidoc/html/:docs/api/VERSION:docs/VERSION-project:kosma/foobar-firmwareref:1.4.0job:firmware-8051install:build/8051/release/firmware.bin:blobs/firmware-8051.blob-project:kosma/foobar-iconsref:69881ebc852f5e02b8328c6b9da615e90b7184b2job:iconsinstall:.:icons/Runart updateto automatically determine latest versions and job numbers
of needed projects and save them intoartifacts.lock.yml. Commit both files
to version control system.Runart downloadto fetch required artifacts to your local cache andart installto install them to the project directory.The LockfileTheartifacts.lock.ymlis conceptually similar to Ruby'sGemfile.lock: it
allows locking to exact revisions and jobs while still semantically tracking
tags or branches and allowing easy updates when needs arise. The following good
practices should be followed:Always runart updateafter editingartifacts.yml.Always commit both files to version control.Do not runart updateautomatically unless you enjoy breaking the build.Continuous integrationAdd the following commands to your.gitlab-ci.yml:before_script:-sudo pip install https://github.com/kosma/art-art configure <url> --token-type {private,job} <token>-art download-art installcache:paths:-.art-cache/File locationsartusesappdirsto store configuration
and cache files. When running under CI environment, the default cache directory is
automatically set to.art-cacheso it can be preserved across jobs.Bugs and limitationsMultiple Gitlab instances are not supported (and would be non-trivial to support).Error handling is very rudimentary: any non-trivial exceptions simply propagate
until Python dumps a stack trace.Logging could be improved.Format of theartifacts.ymlfile is not checked and is barely documented.Some breakage may occur with non-trivial use cases.Like with any other build system, security depends on trusting the developer
not to do anything stupid. In particular, paths are not sanitized; with enough
ingenuity one could probably escape the build directory and wreak havoc.There is nouninstallcommand. If you changed artifact versions and need to
have a clean slate, it's highly recommended to rungit clean -dfx(beware,
however: any local changes to your working copy will be lost without warning).There are probably cleaner solutions to this problem, like using some sort of
cross-language package manager; however, I didn't find any that would satisfy
my needs.Licensingartis open source software; seeCOPYINGfor amusement. Email me if the
license bothers you and I'll happily re-license under anything else under the sun.Authorartwas written by Kosma Moczek <kosma@kosma.pl>, with bugfixes thankfully
contributed by countless good people. Seegit logfor full authorship information.
Package: gitlab-artifacts-downloader
gitlab_artifacts_downloaderSmall class for downloading artifacts in a GitLab CI MR branchFree software: MIT licenseFeaturesTODOCreditsThis package was created withCookiecutterand thegitlab-data/cookiecutter-pypackage, which was forked from theaudreyr/cookiecutter-pypackageproject template.History0.1.0 (2022-11-29)First release on PyPI.
Package: gitlab-attendant
GitLab AttendantDescriptionThe GitLab Attendant is a bot that will tidy and attend to repositories on a specified GitLab installation at a scheduled basis. Currently the bot is capable of removing merged branches, assigning project members to open issues, assigning project members to open merge requests, notifying issue assignees of due or overdue issues, and notifying assignees of stale merge requests.In order to use the GitLab Attendant fully, you should create a new account within the specified GitLab installation with privileges that will allow the bot to read and write any changes necessary to branches, merge requests, issues, etc. The personal access token for this account should then be entered in thetokenparamter when calling the bot from the command line.Python 3.6orPython 3.7are required to run this utility.InstallationThis utility can be installed throughpipby running the following command:pipinstallgitlab-attendantUsagegitlab-attendant--iplocalhost--interval7--tokenTOKEN

Options:--ipTheIPaddressoftheGitLabinstallation.--intervaltaskschedulerintervalinhours(ex.1,10)[default:24]--tokenGitLabpersonalaccesstoken.This will run the GitLab Attendant process, which will begin attending to the specified GitLab installation at the first interval specified.TestsTests for this project utilise thePytestframework. To run the existing suite of unit tests run the following command within the root directory:pytestNotesAll Python code has been formatted byBlack, 'the uncompromising Python code formatter'.Type checking has been provided byPyre.Continuous integration is handled byTravis CI.LicenseSeeLICENSE.md.
Package: gitlab-auto-close-issue
gitlab-auto-close-issueThis is a simple Python cli script that allows you close issues on GitLab automatically. It is intended to be
used during your CI/CD. However you can chose to use it however you wish.UsageFirst you need to create a personal access token,more information here. With the scopeapi, so it can close the issue for you.pipinstallgitlab-auto-close-issuegitlab_auto_close_issue--helpUsage:gitlab_auto_close_issue[OPTIONS]GitLabAutoCloseIssueOptions:--private-tokenTEXTPrivateGITLABtoken,usedtoauthenticatewhencallingtheautoissuecloseAPI.[required]--project-idINTEGERTheprojectIDonGitLabtocreatetheautocloseAPIfor.[required]--gitlab-urlTEXTTheGitLabURL.[required]-i,--issueTEXTTheIssueIDtoclose.[required]-r,--remove-labelTEXTThelabelstoremovefrom(all)theissue(s)beforeclosingit.--helpShowthismessageandexit.$gitlab_auto_close_issue--private-tokenxxx--project-urlhttps://gitlab.com/hmajid2301/test\--project-id14416075--issue1--remove-labelbugGitLab CISet a secret variable in your GitLab project with your private token. Name itGITLAB_PRIVATE_TOKEN(CI/CD > Environment Variables).
This is necessary to close the issue on your behalf.
More informationclick here.
This access token is passed to the script with the--private-tokenargument.
An example CI using this can be foundhere,
look for theclose:issuejob.Add the following to your.gitlab-ci.ymlfile:stages:-postclose:issue:image:registry.gitlab.com/gitlab-automation-toolkit/gitlab-auto-close-issuestage:postbefore_script:[]script:-gitlab_auto_close_issue --issue 1 --remove-label "Doing" --remove-label "To Do"Predefined VariablesPlease note some of the arguments can be filled in using environment variables defined during GitLab CI.
For more informationclick here <https://docs.gitlab.com/ee/ci/variables/predefined_variables.html>_.If--private-tokenis not set the script will look for the ENV variableGITLAB_PRIVATE_TOKENIf--source-branchis not set the script will look for the ENV variableCI_COMMIT_REF_NAMEIf--project-idis not set it will look for for the ENV variableCI_PROJECT_IDIf--gitlab-urlis not set it will look for for the ENV variableCI_PROJECT_URLIf--user-idis not set it will look for for the ENV variableGITLAB_USER_IDSetup Development Environmentgitclonegit@gitlab.com:gitlab-automation-toolkit/gitlab-auto-close-issue.gitcdgitlab-auto-close-issuepipinstalltoxmakevirtualenvmakeinstall-devChangelogYou can find thechangelog here.
Package: gitlab-auto-release
GitLab Auto ReleaseThis is a simple Python cli script that allows you create releases in GitLab automatically. It is intended to be
used during your CI/CD. However you can chose to use it however you wish.UsageFirst you need to create a personal access token,more information here.
With the scopeapi, so it can create the release for you. This access token is passed
to the script with the--private-tokenargument.pipinstallgitlab-auto-releasegitlab_auto_release--helpUsage:gitlab_auto_release[OPTIONS]GitlabAutoReleaseTool.Options:--private-tokenTEXTPrivateGITLABtoken,usedtoauthenticatewhencallingtheReleaseAPI.[required]--gitlab-urlTEXTThegitlabURLi.e.gitlab.com.[required]--project-idINTEGERTheprojectIDonGitLabtocreatetheReleasefor.[required]--tag-nameTEXTThetagthereleaseshouldbecreatedfrom.[required]--release-nameTEXTThenameoftherelease.[required]-c,--changelogTEXTPathtofiletochangelogfile,willappenditselftothedescriptionwithtagmatchingchangelog.Mustbeinkeepachangelogformat.-d,--descriptionTEXTPathtofiletouseasthedescriptionfortheRelease.-a,--assetTEXTAnassettoincludeintherelease,i.e.name=link_to_asset.--artifactsTEXTWillincludeartifactsfromjobsspecifiedincurrentpipeline.Usejobname.--helpShowthismessageandexit.gitlab_auto_release--private-token$(private_otken)--project-id8593636\--gitlab-urlhttps://gitlab.com/stegappasaurus/stegappasaurus-app\--tag-namev0.1.0--release-namev0.1.0--changelogCHANGELOG.mdGitLab CISet a secret variable in your GitLab project with your private token. Name itGITLAB_PRIVATE_TOKEN(CI/CD > Environment Variables).
This is necessary to create the release on your behalf.
An example CI using this can be foundhere,
look for thepost:create:gitlab:release:job.Add the following to your.gitlab-ci.ymlfile:stages:-postpublish:release:image:registry.gitlab.com/gitlab-automation-toolkit/gitlab-auto-releasestage:postbefore_script:[]script:-gitlab_auto_release --changelog CHANGELOG.md --artifacts lint --artifacts reportPredefined VariablesPlease note some of the arguments can be filled in using environment variables defined during GitLab CI.
For more informationclick here <https://docs.gitlab.com/ee/ci/variables/predefined_variables.html>_.If--private-tokenis not set the script will look for the ENV variableGITLAB_PRIVATE_TOKENIf--gitlab-urlis not set it will look for for the ENV variableCI_SERVER_URLIf--project-idis not set it will look for for the ENV variableCI_PROJECT_IDIf--tag-nameis not set it will look for for the ENV variableCI_COMMIT_TAGSetup Development Environmentgitclonegit@gitlab.com:gitlab-automation-toolkit/gitlab-auto-release.gitcdgitlab-auto-releasepipinstalltoxmakeinstall-venvsource.venv/bin/activatemakeinstall-devChangelogYou can find thechangelog here.
Package: gitlab-backup
backup a gitlab user or organizationRequirementsGIT 1.9+InstallationUsing PIP via PyPI:pip install gitlab-backupUsing PIP via Github:pip install git+https://github.com/josegonzalez/python-gitlab-backup.git#egg=gitlab-backupUsageCLI Usage is as follows:usage: gitlab-backup [-h] [--host HOST] [--username USERNAME]
                     [--password PASSWORD] [--oath-token OATH_TOKEN]
                     [--private-token PRIVATE_TOKEN] [--clone-bare]
                     [--clone-lfs] [--disable-ssl-verification]
                     [--namespace NAMESPACE]
                     [--output-directory OUTPUT_DIRECTORY] [--prefer-ssh]
                     [--skip-existing]
                     [--private_key]

Backup a gitlab account

optional arguments:
  -h, --help            show this help message and exit
  --host HOST           gitlab host
  --username USERNAME   username for basic auth
  --password PASSWORD   password for basic auth. If a username is given but
                        not a password, the password will be prompted for.
  --oath-token OATH_TOKEN
                        oath token, or path to token (file://...)
  --private-token PRIVATE_TOKEN
                        private token, or path to token (file://...)
  --clone-bare          clone bare repositories
  --clone-lfs           clone LFS repositories (requires Git LFS to be
                        installed, https://git-lfs.github.com)
  --disable-ssl-verification
                        disable ssl verification
  --namespace NAMESPACE
                        specify a gitlab namespace to backup
  --output-directory OUTPUT_DIRECTORY
                        directory at which to backup the repositories
  --prefer-ssh          Clone repositories using SSH instead of HTTPS
  --skip-existing       skip project if a backup directory exists
  --with-membership     Backup projects provided user or key is member of
  --private_key         To specify a private key
Package: gitlab-bk
Gitlab Backup ToolClone all projects in Gitlab account by group at once.Report Bug·Request FeatureTable of ContentsAboutGetting StartedPrerequisitesInstallationUsageLicenseContactTLDR; The last stand before sanctions...Five days ago#gitlabblocked#Iranians’ access without prior notice! and today we faced with a BIG surprise from GitLab! Blocking our Accounts!#discriminationpic.twitter.com/7Dk6E8Yo0L— Ahmad Haghighi (@haghighi_ahmad)October 8, 2020In last days,GitLabhas decided toblockIranian accounts fromcontributingand being part of theopen-sourceecosystem.They didn't send any messages before this decision and our codes and projects have been locked!"Although we understand GitLab might make this decision under the pressure of the US government, we were expecting a more respectful action from GitLab.GitLab blocked our access to private repositories suddenly, but at the very least we wanted GitLab to warn us before limiting our access.GitLab decided to take one step further and ban every user that used Iran's IP address somewhere their history no matter where she/he is living, while they could just restrict access by IP address like other US-based companies. This action is a kind of ban by nationality.Let usdownloadour private repositories and gists and also make them public (setting control).Some text above belong here but repeated again:https://github.com/1995parham/github-do-not-ban-usGetting StartedYou just get the GitLab token and put in this script.PrerequisitesThis tool wrote in python language, so it needs:python3 or above (with pip)Installation$pipinstallgitlab-bkUsageAt first, you have to getGITLAB_PERSONAL_ACCESS_TOKENfromhere.Ensure to check all scopes.For more examples, please refer to theGitLab Official Documentation.Then run script:You can use with advanced options:Usage: gitlab-bk [-t str] [--verbose] [-u str] [-o str] [-m str] [-v] [-h]

Gitlab backup tool, clone all project at once!

Required arguments:
  -t str, --token str   Gitlab personal access token

Optional arguments:
  --verbose             Enable verbose output
  -u str, --url str     Specify Gitlab instance URL
  -m str, --method str  Specify clone method (default is "http")
  -o str, --output str  Output directory (default is "./gitlab-backup")
  -v, --version         Show program's version number and exit
  -h, --help            Show this message and exit.LicenseDistributed under the MIT License. SeeLICENSEfor more information.ContactThe easiest way to contact me is by sending me anemail. But you have
several other options available, too.
Package: gitlab-bm
Gitlab Backup Manager (GLBM)Gitlab Backup Manager is a tool to help manage Backups of Gitlab in one place.Main Backup= gitlab-rake gitlab:backup:createBackup Config= gitlab-ctl backup-etcGetting startedConfiguration OptionsConfiguration settings are used in the following order:Config YAML file ( see order below )OS Environment VariablesThe order of config file checking locationlocal directory where executable is running (Mostly used for dev.) - config.yaml$HOME/.config/glbm/config.yaml/etc/glbm_config.yamlOS Environment VariablesGLBM_S3_BUCKET# Bucket name(required)GLBM_S3_ENDPOINT_URL# URL to S3(required)GLBM_S3_DIRECTORY# Directory path in bucket(required)GLBM_DAYS_TO_KEEP# KeepXdays worth of backups(default: 30)GLBM_NOTIFICATIONS_ENABLED#Send to Slack(default: "false")GLBM_SLACK_TOKENGLBM_SLACK_CHANNEL_IDGLBM_LOGGING_LEVEL# INFO, DEBUG, WARNING, ERROR & CRITICAL(defualt: INFO)GLBM_SKIP_BACKUP_OPTIONS# db, repositories, uploads, artifacts, lfs, registry, and pages(optional)Config file example*Config file used same settings as OS Env above, but lowercase, and removeGLBM_s3_bucket: bucket1s3_endpoint_url: https://<domain>/<path>:<port>s3_directory: gl_backupsdays_to_keep: 14notifications_enabled: "true"slack_token: xoxb-xxxxxxxxxxxxx-xxxxxxxxxxx-xxxxxxxxxxxxslack_channel_id: "ABCDEFGHIJC"logging_level: "DEBUG"skip_backup_options: ['registry', 'artifacts']Installation (Preferred)$pipinstalllgitlab_bmAfter install run the following to see default opitions:$ glbm
Usage: glbm [OPTIONS] COMMAND [ARGS]...

  Gitlab Backup Manager (GLBM) Ver. (x.x.x)

Options:
  --version  Show application Version
  --help     Show this message and exit.

Commands:
  backup              Run main backup
  backup-etc          Run Backup Config and upload to S3
  complete            Run backup, backup_etc, upload_to_s3 and delete_files
  delete-files        Delete old files on S3 based on (X) days to keep
  show-active-config  Show Active ConfigCurrent LimitationsOnly supports Slack NotificationsManual setup ofMain Backupingitlab.rbstill needed(Scheduling of jobs) - Need to manually setup.DevelopmentWant to contribute? Great!  No specifics at this point.  Just basic GitHub Fork and Pull request.For further info, seegithub guideon contributing to opensource project.After cloning your Forked branch locally, and installing Poetry, you can run the following to setup dev env and test:$poetryinstallThen to run, do the following:$ poetry run glbmLicenseMITLICENSE.txt
Package: gitlab-branch
Manage branch for gitlab projectInstallationfrom pypipython3-mpipinstallgitlab-branchor install from sourcegitclonegit@github.com:joelee2012/gitlab-branch.git
python3-mpipinstallgitlab-branchUsage$gitlab-branch-h
usage:gitlab-branch[-h]{create,delete,list,protect,unprotect}...

managebranchforgitlabproject

optionalarguments:-h,--helpshowthishelpmessageandexitsubcommands:thefollowingcommandsaresupported{create,delete,list,protect,unprotect}createcreatebranchdeletedeletebranchlistlistbranchprotectprotectbranchunprotectunprotectbranch
Package: gitlabbuildvariables
GitLab Build VariablesTools for dealing with GitLab CI pipeline build variables.ToolsManaging Multiple ProjectsUpdating GitLab Build VariablesSets project build variables based on a configuration file:gitlab-update-variables--url${gitlabUrl}--token${accessToken}--default-setting-extension${extensions}\--setting-repository${repositoryDirectories}--${configLocation}`See Example 1 <#example-1>`__ for a more intuitive example of how to
use this tool!Managing a Single ProjectSetting a GitLab Build VariablesThis tool allows a GitLab CI project’s build variables to be set from a
ini config file, a JSON file or a shell script that just exports
variables:gitlab-set-variables--url${gitlabUrl}--token${accessToken}${project}${locationOfVariables}Getting GitLab Build Variablesgitlab-get-variables--url${gitlabUrl}--token${accessToken}${project}ExamplesExample 1Using theexample configurationto update the
variables for a number of projects:$exportgitlabUrl=https://gitlab.example.com$exportaccessToken=personalAccessToken$gitlab-get-variables--url${gitlabUrl}--token${accessToken}cn13/my-project-1{'VALUE_1':'other'}$gitlab-get-variables--url${gitlabUrl}--token${accessToken}cn13/my-project-2{}$gitlab-update-variables--url${gitlabUrl}--token${accessToken}--default-setting-extensionjsoninish\--setting-repositoryexamples/settings--examples/config.jsonReadconfigfrom"examples/config.json"Setvariablesfor"cn13/my-project-1":{'VALUE_1':'abc','VALUE_2':'other','VALUE_3':'other'}Setvariablesfor"cn13/my-project-2":{'VALUE_1':'abc','VALUE_2':'other','VALUE_3':'ghi'}Example 2Using the settings defined inthe example
directoryto update a project’s variables:$exportgitlabUrl=https://gitlab.internal.example.com$exportaccessToken=applicationAccessToken$gitlab-get-variables--url${gitlabUrl}--token${accessToken}my-project{'VALUE_1':'other'}$gitlab-set-variables--url${gitlabUrl}--token${accessToken}group/my-projectcommon.jsons3.shproject.iniVariablesforproject"my-project"setto:{'VALUE_1':'abc','VALUE_2':'def','VALUE_3':'ghi'}
Package: gitlab-bulkcheckout
Gitlab Bulk Checkout ToolSimple utitlity written inPythonfor the local repositories.
In a Time of SaaS, Isac and microservices, it can happen that you need many small repositories at your local Machine for Development, so it didn`t make fun to pull so many repositories.Featuressort gitlab grops to fs folderappend a prefix to the repospull changes from originUsing Tox Build Scriptsource~/development/lib/virtualenv/tox/bin/activatetoxThe tox script create a installable dist under./.tox/dist/*.tar.gzDockerFor easy usage, the tool can be wrapped with docker, so you don`t need a local python env for using.Builddockerbuild-tnolte/gitlab-bulkcheckout.ssh agenthttps://kb.iu.edu/d/aewwUsagedockerrun-it\--user=${UID}:$(id-g$(whoami))\-v$SSH_AUTH_SOCK:/ssh-agent\-eSSH_AUTH_SOCK=/ssh-agent\-eGROUPS_MAPPINGS=/app/gitlab_groupMapping.yml\-eGITLAB_TOKEN=$(pass/internet/gitlab.com/tokens/management)\-ePROJECTS_BASE=/tmp/bulkcheckout\-w/tmp/bulkcheckout\-v/tmp/bulkcheckout:/tmp/bulkcheckout\-v${HOME}/.ssh:/home/builder/.ssh:ro\-v${PWD}/gitlab_groupMapping.yml:/app/gitlab_groupMapping.yml:ro\nolte/gitlab-bulkcheckout-vcheckoutbulk
Package: gitlab-changelog-gen
Gitlab Changelog GeneratorA command line utility to generate CHANGELOG.md for a gitlab repository.The merged merge requests tagged with a milestone will be collected to generate the changelog.Install# pip install gitlab-changelog-genUsage# chg-gen initGitlabhost:https://your-gitlab.com
Gitlabgroup:your-group
Gitlabproject:your-project
Gitlabprivatetoken:your-token# chg-gen outputChangelogisgeneratedto'./CHANGELOG.md'success.ConfigurationBefore generate the changelog file, you need to runchg-gen initto init the config first. The default config file
is.chg-gen.configunder the working directory.The config file isYAMLformat, and this is the instructions:// host address of your gitlabhost:https://gitlab.example// group name of your repogroup:foo// project name of your repoproject:bar// private_token to access your gitlab APIprivate_token:yourtokenGeneration RulesThe generation rules of a changelog consist of:Release: Areleasesection containsfeaturesandbug fixes. The release name is the title ofmilestoneof the project.Features: Composed by the mergedmerge requestslabeled withfeatureorenhancement.Bug Fixes: Composed by the mergedmerge requestslabeled withbug.Change Items: Components ofFeaturesandBug Fixes. The content is the title of themerge requestwith its
reference and theauthorreference.An example ofCHANGELOG.md.
Package: gitlab-changelog-generator
GitLab CHANGELOG GeneratorDescriptionA simple command line utility to produce a CHANGELOG.md file from the commit differences between two GitLab project branches.Python 3.6orPython 3.7are required to run this utility.InstallationThis utility can be installed throughpipby running the following command:pipinstallgitlab-changelog-generatorUsagechangegen--iplocalhost--grouptest-projects--projecttest-project--branchesmasterrelease--version1.1TestsTests for this project utilise thePytestframework. To run the existing suite of unit tests run the following command within the root directory:pytestNotesAll Python code has been formatted byBlack, 'the uncompromising Python code formatter'.Type checking has been provided byPyre.Continuous integration is handled byTravis CI.LicenseSeeLICENSE.md.