'gitlab' 검색 결과

Build a GitLab CI/CD pipeline with automated checks for vulnerable code, dependencies, container images, running applications, and exposed secrets. Covers scanner configuration, consolidated findings, and approval policies for serious vulnerabilities before production deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add automated security scans to .gitlab-ci.yml
• Check dependencies and container images for known vulnerabilities
• Detect credentials and API keys committed to source control

Build GitLab workflows that automate building, testing, and deployment. The skill covers pipeline stages, dependency caching, runners that execute jobs, and manual approval before production deployment, with examples for Docker, Kubernetes, and Terraform.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating builds and tests in GitLab
• Reviewing caches to improve pipeline performance
• Separating staging and production deployments

Review a GitLab merge request linked to a Factory work item, verify the current commit, and publish findings with a test report. It records the review verdict on the card and prepares a session handoff without merging.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review a GitLab merge request assigned through Factory
• Verify earlier review findings against the current commit
• Publish test results and an evidence-based verdict

Push the current Git branch and get a link to its GitLab CI or GitHub Actions runs. The workflow checks for uncommitted changes and blocks direct pushes to main, master, and production before proceeding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Pushing a committed feature branch
• Finding the GitLab CI tracking link after a push
• Finding GitHub Actions runs for the current branch

Check CI, the automated checks run on code changes, for the current branch alongside recent commits. Supports GitLab CI and GitHub Actions, with optional pull request or merge request numbers and links when command-line tools are unavailable.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking CI progress after a push
• Reviewing checks for a specific pull request
• Viewing a GitLab merge request

GitHub, GitLab, Perforce 변경의 검토 의견, 자동 검사 실패와 설명 누락을 확인하고, 할 일을 정리하며 요청에 따라 수정과 처리된 스레드 해결을 지원합니다.

• 변경 사항을 제출하기 전에 점검합니다
• 실패한 검사와 수정할 항목을 확인합니다
• 사람과 봇의 검토 의견을 정리합니다

Re-review a GitLab merge request after new commits, track the outcome of every previous finding, and inspect both new changes and the full proposal. Verify the current code, then publish a test report and review verdict.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Re-reviewing a merge request after fixes
• Tracking the resolution of earlier review findings
• Checking new commits for regressions and incomplete fixes

Inspect project files to identify languages and build tools, then generate starter GitHub Actions or GitLab CI workflows. Set up automated checks, caching, and deployment stages that reflect the project’s commands and target environments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up automated checks for a new project
• Reworking fragile pipeline configuration
• Moving between GitHub Actions and GitLab CI

Provides GitHub Actions and GitLab CI templates for automating tests, builds, and releases. It adapts configurations to project types and covers caching, parallel jobs, credential handling, and controls for production deployments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up CI/CD for a frontend or backend project
• Automating tests and releases for a library
• Running checks only for changed parts of a monorepo

Set up Strix security checks in CI/CD to test pull request changes, report verified vulnerabilities, and gate merges. Covers both a CLI running on your own infrastructure and a managed service with pull request comments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check pull request changes for vulnerabilities before merging
• Add Strix scans to GitHub Actions or GitLab CI
• Choose between managed reviews and scans on your own runners

Review code changes on GitHub or GitLab and investigate failed CI checks, the automated checks run on code. Use logs to guide fixes, push commits, and share review comments and repair summaries.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review code changes and leave inline comments
• Investigate failed CI checks and fix the code
• Share fix summaries with human reviewers

Inspect GitHub and GitLab repositories, issues, and proposed code changes, then prepare small fixes with tests and review summaries. Uses existing command-line authentication and requires approval before publishing changes or modifying repository records.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review open issues and proposed code changes
• Summarize changes using commit history
• Prepare and test a small code fix

Take an agreed code change through a GitHub or GitLab pull request, automated checks, independent review, and fixes. Merge only after the latest commit passes all checks and has no unresolved review findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn an agreed code change into a pull request
• Wait for automated checks and investigate failures
• Arrange an independent review and address findings

Design automated build, test, and deployment workflows for GitHub Actions, GitLab CI/CD, and Jenkins. Covers job ordering, dependency caching, secret handling, and gradual releases that use health checks before expanding deployment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Automating builds, tests, and deployments
• Reducing pipeline time with caching and parallel jobs
• Planning gradual releases and rollbacks

Build CI workflows that use mirrord to test applications against services in a real Kubernetes cluster. Configure runner access, start and stop application sessions, validate configuration files, and troubleshoot connection, permission, and logging problems.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Run integration and end-to-end tests against staging
• Create mirrord workflows for GitHub Actions or GitLab CI
• Configure Kubernetes access from a CI runner

Review build and deployment pipelines for unsafe workflows, exposed credentials, and configuration flaws across GitHub Actions, Jenkins, GitLab CI, and Terraform state files. Use concrete evidence and false-positive checks to distinguish exploitable issues from suspicious settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review GitHub Actions workflows for unsafe execution paths
• Investigate Jenkins exposure and affected versions
• Check logs, artifacts, and container images for leaked secrets

Helps configure Playwright tests in automated CI/CD pipelines across major providers. Covers splitting tests across runners, Docker execution, shared login setup, code coverage, and saving reports and debugging artifacts to investigate failures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running Playwright tests in GitHub Actions or GitLab CI
• Splitting tests across multiple runners
• Saving traces and reports after test failures

Configure GitLab CI/CD pipelines and runners for automated building, testing, and deployment. Create .gitlab-ci.yml configurations, manage runners, and implement DevOps workflows. Use when working with GitLab repositories or self-hosted GitLab instances.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GitLab CLI for managing issues, merge requests, CI/CD pipelines, and repositories. Use when: (1) Creating, reviewing, or merging MRs, (2) Managing GitLab issues, (3) Monitoring or triggering CI/CD pipelines, (4) Working with self-hosted GitLab instances, (5) Automating GitLab workflows from the command line. Requires GITLAB_TOKEN (recommend minimal scopes). The `glab api` command enables arbitrary API calls - use read-only tokens when possible.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate and optimize CI/CD pipelines for GitLab CI and CircleCI. Use when a user asks to set up GitLab CI, create a CircleCI pipeline, build a CI pipeline for GitLab, automate deployments with CircleCI, add test automation to GitLab, or configure continuous integration on non-GitHub platforms. For GitHub Actions pipelines, use the github-actions skill instead.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when designing or validating GitLab CI/CD and automatic release lifecycles, inspecting pipeline and job state read-only, composing non-interactive merge-request commands, or setting up protected refs and release credentials. Also covers reusable components and inputs, GitLab Functions, gitlab-ci-local, glab command composition, and GitLab Flavored Markdown. For pipeline execution or retry requests, provide inspection and command drafting while leaving execution to the operator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when authoring or debugging GitLab CI/CD pipelines (.gitlab-ci.yml) — e.g. "add a CI pipeline for this Drupal project", "run phpcs/phpstan/phpunit in GitLab CI", "deploy with drush from a pipeline", "why is my job not running", "cache composer dependencies", or anything involving stages, rules, artifacts, environments, or GitLab runners.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

スケーラブルな自動化のためのマルチステージワークフロー、キャッシング、分散ランナーを備えたGitLab CI/CDパイプラインを構築。GitLab CI/CDの実装、パイプラインパフォーマンスの最適化、または自動テストとデプロイメントのセットアップ時に使用。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review GitHub pull requests and GitLab merge requests for security, test gaps, compatibility, and performance risks. Trace affected code and services, then produce a prioritized report with suggested fixes and a structured review checklist.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing shared libraries and API changes before merging
• Organizing feedback on large pull requests
• Checking authentication and payment code changes