open-index/open-npm huggingface dataset:
npm package: @gitlaber/cascade
Description: The idea of this command came from couple feature proposals - [Cascaded Merge Requests proposal](https://gitlab.com/gitlab-org/gitlab/-/issues/11648) - [Inability to create MRs from the default branch using push options](https://gitlab.com/gitlab-org/gitl
Latest version: 0.1.0

# CLI command implementing cascaded merge requests

The idea of this command came from couple feature proposals
- [Cascaded Merge Requests proposal](https://gitlab.com/gitlab-org/gitlab/-/issues/11648)
- [Inability to create MRs from the default branch using push options](https://gitlab.com/gitlab-org/gitlab/-/issues/214123)

Behind both of features I have in mind Gitlab Flow with [environment branches approach](https://docs.gitlab.com/ee/topics/gitlab_flow.html#environment-branches-with-gitlab-flow)

So this approach suggests moving changes to different environments by use of MRs. With numerous environments it may require large number of MRs to be created and I thought that it would be nice to automate MR creation/update process

## Usage
```
Usage: gitlab cascade [options]

Create/Update cascaded merge request

Options:
  --project <projectPath>      Gitlab project path (default $CI_PROJECT_PATH)
  --source <sourceBranch>      Source branch (default $CI_COMMIT_BRANCH)
  --target <targetBranch>      Target branch
  --title <title>              Merge request title
  --description <description>  Merge request description
  -h, --help                   display help for command
```

This command has the following logic:
- It tries to find the existing open merge requests between source and target branches
- In case if there are no requests - it will create a new MR labeled as cascaded
- In case if there are MRs - it will try to update existing MR's( only those labeled with cascaded ) with the provided title and description

This project also delivers an approximate [template](.gitlab/cascade.gitlab-ci.yml) how this feature can be used.

| This command is a part of @giltaber/cli CLI
npm package: @gitlaber/cli
Description: This command line is intended to keep helper funtions which are not available in glab official CLI but might be useful in some CI/CD templates
Latest version: 0.1.4

# Gitlab CI/CD command line

This command line is intended to keep helper funtions which are not available in glab official CLI but might be useful in some CI/CD templates

# Usage

```
Usage: gitlab [options] [command]

Options:
  -h, --help         display help for command

Commands:
  cascade [options]  Create/Update cascaded merge request
  wait [options]     Wait for another pipeline
  help [command]     display help for command
```

## Commands

### cascade: cascade merge requests
```
Usage: gitlab cascade [options]

Create/Update cascaded merge request

Options:
  --project <projectPath>      Gitlab project path (default $CI_PROJECT_PATH) (default: "/theplenkov-npm/gitlab-ci-cli")
  --source <sourceBranch>      Source branch (default $CI_COMMIT_BRANCH) (default: "main")
  --target <targetBranch>      Target branch
  --title <title>              Merge request title
  --description <description>  Merge request description
  -h, --help                   display help for command
```
### wait

```
Usage: gitlab wait [options]

Wait for another pipeline

Options:
  --project <projectPath>  Gitlab project path (default $CI_PROJECT_PATH) (default: "/theplenkov-npm/gitlab-ci-cli")
  --ref <pipelineRef>      Pipeline reference
  --delay <delayInSec>     Poll every <delay> seconds (1 second by default) (default: "1")
  -h, --help               display help for command
```
npm package: @gitlaber/sdk
Description: Contains only needed queries and mutations.
Latest version: 0.1.0

# Generated SDK for GraphQL API

Contains only needed queries and mutations.

## How to extend

- add new command to `commands` folder
- run `graph-codegen` command again
- [sdk.ts file](src/generated/sdk.ts) will be regenerated
- it's not stored in the source code - but is available as job artifact and also published on npm
npm package: @gitlaber/wait-for
Description: Pretend we have the situation when we use tag pipelines to build some artifacts like packages or images. Using tags guarantees uniqueness also they can be protected so it's a quick win for many compliance controls. However, pretend you have a deployment (
Latest version: 0.1.4

# Wait for another pipeline in Gitlab CI/CD
Pretend we have the situation when we use tag pipelines to build some artifacts like packages or images. Using tags guarantees uniqueness also they can be protected so it's a quick win for many compliance controls. However, pretend you have a deployment ( especially using gitlab flow with environment branches ) via MRs. So it may happen quite easily that by moment when MR got approved Tag pipeline is not yet finished and artifacts are not yet fully build so deployment is not ready. So it would be nice to have something like this `gitlab wait --ref v${npm_package_version}`.

## Usage

```
Usage: wait [options]

Wait for another pipeline

Options:
  --project <projectPath>  Gitlab project path (default $CI_PROJECT_PATH) (default: "/theplenkov-npm/gitlab-ci-cli")
  --ref <pipelineRef>      Pipeline reference
  --delay <delayInSec>     Poll every <delay> seconds (1 second by default) (default: "1")
  -h, --help               display help for command
```

| This command is a part of @giltaber/cli CLI