Skip to content

G
gitlab-ce
Commit 4555e1b2 authored by GitLab Bot's avatar GitLab Bot
Browse files
Options

Add latest changes from gitlab-org/gitlab@13-12-stable-ee

parent e570267f
Expand all Hide whitespace changes
Inline Side-by-side
Showing with 19427 additions and 11157 deletions

Too many changes to show.
Plain diff Email patch

To preserve performance only 1000 of 1000+ files are displayed.

.gitignore
View file @ 4555e1b2
......@@ -105,3 +105,4 @@ ee/changelogs/unreleased-ee
tags.lock
tags.temp
.stylelintcache
.solargraph.yml
.gitlab-ci.yml
View file @ 4555e1b2
......@@ -53,21 +53,36 @@ workflow:
variables:
RAILS_ENV: "test"
NODE_ENV: "test"
BUNDLE_WITHOUT: "production:development"
BUNDLE_INSTALL_FLAGS: "--jobs=$(nproc) --retry=3 --quiet"
# we override the max_old_space_size to prevent OOM errors
NODE_OPTIONS: --max_old_space_size=3584
SIMPLECOV: "true"
GIT_DEPTH: "20"
GIT_SUBMODULE_STRATEGY: "none"
GET_SOURCES_ATTEMPTS: "3"
KNAPSACK_RSPEC_SUITE_REPORT_PATH: knapsack/report-master.json
FLAKY_RSPEC_SUITE_REPORT_PATH: rspec_flaky/report-suite.json
RSPEC_TESTS_MAPPING_PATH: crystalball/mapping.json
RSPEC_PACKED_TESTS_MAPPING_PATH: crystalball/packed-mapping.json
BUILD_ASSETS_IMAGE: "false"
ES_JAVA_OPTS: "-Xms256m -Xmx256m"
ELASTIC_URL: "http://elastic:changeme@elasticsearch:9200"
DOCKER_VERSION: "20.10.1"
CACHE_CLASSES: "true"
CHECK_PRECOMPILED_ASSETS: "true"
FF_USE_FASTZIP: "true"
DOCS_REVIEW_APPS_DOMAIN: "178.62.207.141.nip.io"
DOCS_GITLAB_REPO_SUFFIX: "ee"
REVIEW_APPS_DOMAIN: "gitlab-review.app"
REVIEW_APPS_GCP_PROJECT: "gitlab-review-apps"
REVIEW_APPS_GCP_REGION: "us-central1"
BUILD_ASSETS_IMAGE: "true" # Set it to "false" to disable assets image building, used in `build-assets-image`
RSPEC_FAIL_FAST_ENABLED: "true" # Set it to "false" to disable RSpec fail-fast
SIMPLECOV: "true"
# Preparing custom clone path to reduce space used by all random forks
# on GitLab.com's Shared Runners. Our main forks - especially the security
......@@ -91,30 +106,4 @@ variables:
GIT_CLONE_PATH: "/builds/gitlab-org-forks/${CI_PROJECT_NAME}"
include:
- local: .gitlab/ci/build-images.gitlab-ci.yml
- local: .gitlab/ci/cache-repo.gitlab-ci.yml
- local: .gitlab/ci/cng.gitlab-ci.yml
- local: .gitlab/ci/docs.gitlab-ci.yml
- local: .gitlab/ci/frontend.gitlab-ci.yml
- local: .gitlab/ci/global.gitlab-ci.yml
- local: .gitlab/ci/memory.gitlab-ci.yml
- local: .gitlab/ci/pages.gitlab-ci.yml
- local: .gitlab/ci/qa.gitlab-ci.yml
- local: .gitlab/ci/reports.gitlab-ci.yml
- local: .gitlab/ci/rails.gitlab-ci.yml
- local: .gitlab/ci/vendored-gems.gitlab-ci.yml
- local: .gitlab/ci/review.gitlab-ci.yml
- local: .gitlab/ci/rules.gitlab-ci.yml
- local: .gitlab/ci/setup.gitlab-ci.yml
- local: .gitlab/ci/dev-fixtures.gitlab-ci.yml
- local: .gitlab/ci/test-metadata.gitlab-ci.yml
- local: .gitlab/ci/yaml.gitlab-ci.yml
- local: .gitlab/ci/releases.gitlab-ci.yml
- local: .gitlab/ci/notify.gitlab-ci.yml
- local: .gitlab/ci/dast.gitlab-ci.yml
- local: .gitlab/ci/workhorse.gitlab-ci.yml
- local: .gitlab/ci/graphql.gitlab-ci.yml
# switch the remote include to a local include until this is resolved:
# https://gitlab.com/gitlab-org/gitlab/-/issues/327299
# - remote: 'https://gitlab.com/gitlab-org/frontend/untamper-my-lockfile/-/raw/main/.gitlab-ci-template.yml'
- local: .gitlab/ci/untamper-my-lockfile.yml
- local: .gitlab/ci/*.gitlab-ci.yml
.gitlab/CODEOWNERS
View file @ 4555e1b2
This diff is collapsed.
.gitlab/ci/build-images.gitlab-ci.yml
View file @ 4555e1b2
......@@ -9,8 +9,18 @@ build-qa-image:
- .build-images:rules:build-qa-image
stage: build-images
needs: []
variables:
QA_IMAGE: "${CI_REGISTRY}/${CI_PROJECT_PATH}/gitlab-ee-qa:${CI_COMMIT_REF_SLUG}"
script:
- export QA_IMAGE="${CI_REGISTRY}/${CI_PROJECT_PATH}/gitlab-ee-qa:${CI_COMMIT_REF_SLUG}"
# With .git/hooks/post-checkout in place, Git tries to pull LFS objects, but the image doesn't have Git LFS, and we actually don't care about it for this specific so we just remove the file.
# Without removing the file, the error is as follows: "This repository is configured for Git LFS but 'git-lfs' was not found on your path. If you no longer wish to use Git LFS, remove this hook by deleting .git/hooks/post-checkout."
- rm .git/hooks/post-checkout
# Use $CI_MERGE_REQUEST_SOURCE_BRANCH_SHA so that GitLab image built in omnibus-gitlab-mirror and QA image are in sync.
# This falls back to $CI_COMMIT_SHA (the default checked out commit) for the non-merged result pipelines.
# See https://docs.gitlab.com/ee/development/testing_guide/end_to_end/index.html#with-pipeline-for-merged-results.
- if [ -n "$CI_MERGE_REQUEST_SOURCE_BRANCH_SHA" ]; then
git checkout -f ${CI_MERGE_REQUEST_SOURCE_BRANCH_SHA};
fi
- /kaniko/executor --context=${CI_PROJECT_DIR} --dockerfile=${CI_PROJECT_DIR}/qa/Dockerfile --destination=${QA_IMAGE} --cache=true
retry: 2
......
.gitlab/ci/cache-repo.gitlab-ci.yml
View file @ 4555e1b2
......@@ -28,9 +28,9 @@ cache-repo:
before_script:
- '[ -z "$CI_REPO_CACHE_CREDENTIALS" ] || gcloud auth activate-service-account --key-file=$CI_REPO_CACHE_CREDENTIALS'
script:
# Enable shallow repo caching only if the $ENABLE_SHALLOW_REPO_CACHING variable exists
# Enable shallow repo caching unless the $DISABLE_SHALLOW_REPO_CACHING variable exists (in the case the shallow clone caching isn't working well)
# The `git repack` call works around a Git bug with shallow clones: https://gitlab.com/gitlab-org/git/-/issues/86
- if [ -n "$ENABLE_SHALLOW_REPO_CACHING" ]; then
- if [ -z "$DISABLE_SHALLOW_REPO_CACHING" ]; then
cd .. && rm -rf $CI_PROJECT_NAME;
today=$(date +%Y-%m-%d);
year=$(date +%Y);
......@@ -47,8 +47,8 @@ cache-repo:
time gzip /tmp/$SHALLOW_CLONE_TAR_FILENAME;
[ -z "$CI_REPO_CACHE_CREDENTIALS" ] || (echo "Uploading /tmp/$SHALLOW_CLONE_TAR_FILENAME.gz to GCloud." && time gsutil cp /tmp/$SHALLOW_CLONE_TAR_FILENAME.gz gs://gitlab-ci-git-repo-cache/project-$CI_PROJECT_ID/$SHALLOW_CLONE_TAR_FILENAME.gz);
fi
# By default, we want to cache the full repo, unless the $DISABLE_FULL_REPO_CACHING variable exists (in the case the shallow clone caching is working well)
- if [ -z "$DISABLE_FULL_REPO_CACHING" ]; then
# Disable the full repo caching unless the $DISABLE_SHALLOW_REPO_CACHING variable exists (in the case the shallow clone caching isn't working well)
- if [ -n "$DISABLE_SHALLOW_REPO_CACHING" ]; then
cd .. && rm -rf $CI_PROJECT_NAME;
echo "Cloning $CI_REPOSITORY_URL into $CI_PROJECT_NAME.";
time git clone --progress $CI_REPOSITORY_URL $CI_PROJECT_NAME;
......
.gitlab/ci/cng.gitlab-ci.yml
View file @ 4555e1b2
......@@ -7,4 +7,4 @@ cloud-native-image:
GIT_DEPTH: "1"
script:
- install_gitlab_gem
- CNG_PROJECT_PATH="gitlab-org/build/CNG" BUILD_TRIGGER_TOKEN=$CI_JOB_TOKEN ./scripts/trigger-build cng
- CNG_PROJECT_PATH="gitlab-org/build/CNG" ./scripts/trigger-build cng
.gitlab/ci/dast.gitlab-ci.yml
View file @ 4555e1b2
......@@ -3,7 +3,7 @@
- prm
# For scheduling dast job
extends:
- .reports:schedule-dast
- .reports:rules:schedule-dast
image:
name: "registry.gitlab.com/gitlab-org/security-products/dast:$DAST_VERSION"
resource_group: dast_scan
......
.gitlab/ci/dev-fixtures.gitlab-ci.yml
View file @ 4555e1b2
......@@ -3,7 +3,7 @@
- .default-retry
- .rails-cache
- .default-before_script
- .use-pg11
- .use-pg12
stage: test
needs: ["setup-test-env"]
variables:
......@@ -29,7 +29,7 @@ run-dev-fixtures-ee:
extends:
- .run-dev-fixtures
- .dev-fixtures:rules:ee-only
- .use-pg11-ee
- .use-pg12-ee
script:
- cp ee/db/fixtures/development/* $FIXTURE_PATH
- *run-dev-fixtures-script
.gitlab/ci/docs.gitlab-ci.yml
View file @ 4555e1b2
......@@ -44,7 +44,7 @@ docs-lint markdown:
- .default-retry
- .docs:rules:docs-lint
# When updating the image version here, update it in /scripts/lint-doc.sh too.
image: "registry.gitlab.com/gitlab-org/gitlab-docs/lint-markdown:alpine-3.12-vale-2.8.0-markdownlint-0.26.0"
image: registry.gitlab.com/gitlab-org/gitlab-docs/lint-markdown:alpine-3.13-vale-2.10.2-markdownlint-0.26.0
stage: test
needs: []
script:
......@@ -52,9 +52,10 @@ docs-lint markdown:
docs-lint links:
extends:
- .default-retry
- .docs:rules:docs-lint
image: "registry.gitlab.com/gitlab-org/gitlab-docs/lint-html:alpine-3.12-ruby-2.7.2"
image: registry.gitlab.com/gitlab-org/gitlab-docs/lint-html:alpine-3.13-ruby-2.7.2
# TODO: revert to .default-retry when https://gitlab.com/gitlab-org/gitlab/-/issues/331002 is fixed.
retry: 2
stage: test
needs: []
script:
......
.gitlab/ci/frontend.gitlab-ci.yml
View file @ 4555e1b2
......@@ -58,38 +58,34 @@ compile-test-assets as-if-foss:
update-assets-compile-production-cache:
extends:
- compile-production-assets
- .assets-compile-cache-push
- .shared:rules:update-cache
stage: prepare
artifacts: {} # This job's purpose is only to update the cache.
cache:
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
update-assets-compile-test-cache:
extends:
- compile-test-assets
- .assets-compile-cache-push
- .shared:rules:update-cache
stage: prepare
artifacts: {} # This job's purpose is only to update the cache.
cache:
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
update-yarn-cache:
extends:
- .default-retry
- .yarn-cache
- .yarn-cache-push
- .shared:rules:update-cache
stage: prepare
script:
- *yarn-install
cache:
policy: push
.frontend-fixtures-base:
extends:
- .default-retry
- .default-before_script
- .rails-cache
- .use-pg11
- .use-pg12
stage: fixtures
needs: ["setup-test-env", "retrieve-tests-metadata", "compile-test-assets"]
variables:
......@@ -121,7 +117,7 @@ rspec frontend_fixture as-if-foss:
rspec-ee frontend_fixture:
extends:
- .frontend-fixtures-base
- .frontend:rules:default-frontend-jobs
- .frontend:rules:default-frontend-jobs-ee
parallel: 2
graphql-schema-dump:
......@@ -156,7 +152,7 @@ eslint-as-if-foss:
needs: []
script:
- *yarn-install
- run_timed_command "yarn run eslint"
- run_timed_command "yarn run lint:eslint:all"
.karma-base:
extends: .frontend-test-base
......@@ -169,8 +165,10 @@ karma:
extends:
- .karma-base
- .frontend:rules:default-frontend-jobs
# Don't use `needs` since `rspec-ee frontend_fixture` doesn't exist in `gitlab-foss` pipelines.
dependencies: ["rspec frontend_fixture", "rspec-ee frontend_fixture"]
needs:
- job: "rspec frontend_fixture"
- job: "rspec-ee frontend_fixture"
optional: true
coverage: '/^Statements *: (\d+\.\d+%)/'
artifacts:
name: coverage-javascript
......@@ -201,8 +199,10 @@ jest:
extends:
- .jest-base
- .frontend:rules:default-frontend-jobs
# Don't use `needs` since `rspec-ee frontend_fixture` doesn't exist in `gitlab-foss` pipelines.
dependencies: ["rspec frontend_fixture", "rspec-ee frontend_fixture"]
needs:
- job: "rspec frontend_fixture"
- job: "rspec-ee frontend_fixture"
optional: true
artifacts:
name: coverage-frontend
expire_in: 31d
......@@ -222,8 +222,11 @@ jest-integration:
script:
- *yarn-install
- run_timed_command "yarn jest:integration --ci"
# Don't use `needs` since `rspec-ee frontend_fixture` doesn't exist in `gitlab-foss` pipelines.
dependencies: ["rspec frontend_fixture", "rspec-ee frontend_fixture", "graphql-schema-dump"]
needs:
- job: "rspec frontend_fixture"
- job: "rspec-ee frontend_fixture"
optional: true
- job: "graphql-schema-dump"
jest-as-if-foss:
extends:
......
.gitlab/ci/global.gitlab-ci.yml
View file @ 4555e1b2
......@@ -16,75 +16,147 @@
- source scripts/utils.sh
- source scripts/prepare_build.sh
.ruby-gems-cache: &ruby-gems-cache
key: "ruby-gems-v1"
paths:
- vendor/ruby/
policy: pull
.ruby-gems-cache-push: &ruby-gems-cache-push
<<: *ruby-gems-cache
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.gitaly-ruby-gems-cache: &gitaly-ruby-gems-cache
key: "gitaly-ruby-gems-v1"
paths:
- vendor/gitaly-ruby/
policy: pull
.gitaly-ruby-gems-cache-push: &gitaly-ruby-gems-cache-push
<<: *gitaly-ruby-gems-cache
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.go-pkg-cache: &go-pkg-cache
key: "go-pkg-v1"
paths:
- .go/pkg/mod/
policy: pull
.go-pkg-cache-push: &go-pkg-cache-push
<<: *go-pkg-cache
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.node-modules-cache: &node-modules-cache
key: "node-modules-${NODE_ENV}-v1"
paths:
- node_modules/
- tmp/cache/webpack-dlls/
policy: pull
.node-modules-cache-push: &node-modules-cache-push
<<: *node-modules-cache
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.assets-cache: &assets-cache
key: "assets-${NODE_ENV}-v1"
paths:
- assets-hash.txt
- public/assets/webpack/
- tmp/cache/assets/sprockets/
- tmp/cache/babel-loader/
- tmp/cache/vue-loader/
policy: pull
.assets-cache-push: &assets-cache-push
<<: *assets-cache
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.rubocop-cache: &rubocop-cache
key: "rubocop-v1"
paths:
- tmp/rubocop_cache/
policy: pull
.rubocop-cache-push: &rubocop-cache-push
<<: *rubocop-cache
# We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up but RuboCop has a mechanism
# for keeping only the N latest cache files, so we take advantage of it with `pull-push`.
policy: pull-push
.qa-ruby-gems-cache: &qa-ruby-gems-cache
key: "qa-ruby-gems-v1"
paths:
- qa/vendor/ruby/
policy: pull
.qa-ruby-gems-cache-push: &qa-ruby-gems-cache-push
<<: *qa-ruby-gems-cache
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.setup-test-env-cache:
cache:
key: "setup-test-env-v1"
paths:
- vendor/ruby/
- vendor/gitaly-ruby/
- .go/pkg/mod/
policy: pull
- *ruby-gems-cache
- *gitaly-ruby-gems-cache
- *go-pkg-cache
.setup-test-env-cache-push:
cache:
- *ruby-gems-cache-push
- *gitaly-ruby-gems-cache-push
- *go-pkg-cache-push
.rails-cache:
cache:
key: "rails-v5"
paths:
- vendor/ruby/
- vendor/gitaly-ruby/
policy: pull
- *ruby-gems-cache
- *gitaly-ruby-gems-cache
.static-analysis-cache:
cache:
key: "static-analysis-v2"
paths:
- vendor/ruby/
- node_modules/
- tmp/rubocop_cache/
policy: pull
- *ruby-gems-cache
- *node-modules-cache
- *rubocop-cache
.static-analysis-cache-push:
cache:
- *ruby-gems-cache # We don't push this cache as it's already rebuilt by `update-setup-test-env-cache`
- *rubocop-cache-push
.coverage-cache:
cache:
key: "coverage-cache-v1"
paths:
- vendor/ruby/
policy: pull
- *ruby-gems-cache
.danger-review-cache:
cache:
key: "danger-review-v1"
paths:
- vendor/ruby/
- node_modules/
policy: pull
- *ruby-gems-cache
- *node-modules-cache
.qa-cache:
cache:
key: "qa-v2"
paths:
- qa/vendor/ruby/
policy: pull
- *qa-ruby-gems-cache
.qa-cache-push:
cache:
- *qa-ruby-gems-cache-push
.yarn-cache:
cache:
key: "yarn-v1"
paths:
- node_modules/
- tmp/cache/webpack-dlls/
policy: pull
- *node-modules-cache
.yarn-cache-push:
cache:
- *node-modules-cache-push
.assets-compile-cache:
cache:
key: "assets-compile-${NODE_ENV}-v1"
paths:
- vendor/ruby/
- node_modules/
- assets-hash.txt
- public/assets/webpack/
- tmp/cache/assets/sprockets/
- tmp/cache/babel-loader/
- tmp/cache/vue-loader/
- tmp/cache/webpack-dlls/
policy: pull
- *ruby-gems-cache
- *node-modules-cache
- *assets-cache
.assets-compile-cache-push:
cache:
- *ruby-gems-cache # We don't push this cache as it's already rebuilt by `update-setup-test-env-cache`
- *node-modules-cache-push
- *assets-cache-push
.use-pg11:
image: "registry.gitlab.com/gitlab-org/gitlab-build-images:ruby-2.7.2.patched-golang-1.14-git-2.31-lfs-2.9-chrome-89-node-14.15-yarn-1.22-postgresql-11-graphicsmagick-1.3.36"
......@@ -128,7 +200,7 @@
.use-kaniko:
image:
name: gcr.io/kaniko-project/executor:debug-v1.3.0
name: registry.gitlab.com/gitlab-org/gitlab-build-images:kaniko
entrypoint: [""]
before_script:
- source scripts/utils.sh
......
.gitlab/ci/memory.gitlab-ci.yml
View file @ 4555e1b2
......@@ -37,7 +37,7 @@ memory-static:
memory-on-boot:
extends:
- .only-code-memory-job-base
- .use-pg11
- .use-pg12
stage: test
needs: ["setup-test-env", "compile-test-assets"]
variables:
......
.gitlab/ci/pages.gitlab-ci.yml
View file @ 4555e1b2
......@@ -3,7 +3,7 @@ pages:
- .default-retry
- .pages:rules
stage: pages
dependencies:
needs:
- rspec:coverage
- coverage-frontend
- karma
......
.gitlab/ci/qa.gitlab-ci.yml
View file @ 4555e1b2
......@@ -4,11 +4,13 @@
- .qa-cache
stage: test
needs: []
variables:
USE_BUNDLE_INSTALL: "false"
SETUP_DB: "false"
before_script:
- '[ "$FOSS_ONLY" = "1" ] && rm -rf ee/ qa/spec/ee/ qa/qa/specs/features/ee/ qa/qa/ee/ qa/qa/ee.rb'
- !reference [.default-before_script, before_script]
- cd qa/
- bundle install --clean --jobs=$(nproc) --path=vendor --retry=3 --without=development --quiet
- bundle check
- bundle_install_script
qa:internal:
extends:
......@@ -39,12 +41,11 @@ qa:selectors-as-if-foss:
update-qa-cache:
extends:
- .qa-job-base
- .qa-cache-push
- .shared:rules:update-cache
stage: prepare
script:
- echo "Cache has been updated and ready to be uploaded."
cache:
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.package-and-qa-base:
image: ${GITLAB_DEPENDENCY_PROXY}ruby:2.7-alpine
......
.gitlab/ci/rails.gitlab-ci.yml
View file @ 4555e1b2
This diff is collapsed.
.gitlab/ci/reports.gitlab-ci.yml
View file @ 4555e1b2
# include:
# - template: Jobs/Code-Quality.gitlab-ci.yml
# - template: Security/SAST.gitlab-ci.yml
# - template: Security/Dependency-Scanning.gitlab-ci.yml
# - template: Security/DAST.gitlab-ci.yml
include:
- template: Jobs/Code-Quality.gitlab-ci.yml
- template: Security/SAST.gitlab-ci.yml
- template: Security/Secret-Detection.gitlab-ci.yml
- template: Security/Dependency-Scanning.gitlab-ci.yml
- template: Security/License-Scanning.gitlab-ci.yml
# We need to duplicate this job's definition because the rules
# defined in the extended jobs rely on local YAML anchors
# (`*if-default-refs`)
code_quality:
extends:
- .default-retry
- .reports:rules:code_quality
- .use-docker-in-docker
stage: test
needs: []
variables:
CODE_QUALITY_IMAGE: "registry.gitlab.com/gitlab-org/ci-cd/codequality:0.85.23"
script:
- |
if ! docker info &>/dev/null; then
if [ -z "$DOCKER_HOST" -a "$KUBERNETES_PORT" ]; then
export DOCKER_HOST='tcp://localhost:2375'
fi
fi
- docker pull --quiet "$CODE_QUALITY_IMAGE"
- docker run
--env SOURCE_CODE="$PWD"
--volume "$PWD":/code
--volume /var/run/docker.sock:/var/run/docker.sock
"$CODE_QUALITY_IMAGE" /code
artifacts:
reports:
codequality: gl-code-quality-report.json
paths:
- gl-code-quality-report.json # GitLab-specific
expire_in: 1 week # GitLab-specific
rules: !reference [".reports:rules:code_quality", rules]
# We need to duplicate this job's definition because the rules
# defined in the extended jobs rely on local YAML anchors
# (`*if-default-refs`)
.sast:
.sast-analyzer:
# We need to re-`extends` from `sast` as the `extends` here overrides the one from the template.
extends:
- .default-retry
- .reports:rules:sast
stage: test
# `needs: []` starts the job immediately in the pipeline
# https://docs.gitlab.com/ee/ci/yaml/README.html#needs
- sast
needs: []
artifacts:
paths:
- gl-sast-report.json # GitLab-specific
reports:
sast: gl-sast-report.json
expire_in: 1 week # GitLab-specific
variables:
DOCKER_TLS_CERTDIR: ""
SAST_ANALYZER_IMAGE_PREFIX: "registry.gitlab.com/gitlab-org/security-products/analyzers"
SAST_ANALYZER_IMAGE_TAG: 2
SAST_BRAKEMAN_LEVEL: 2 # GitLab-specific
SAST_EXCLUDED_PATHS: qa,spec,doc,ee/spec,config/gitlab.yml.example # GitLab-specific
SAST_EXCLUDED_PATHS: "qa, spec, doc, ee/spec, config/gitlab.yml.example, tmp" # GitLab-specific
SAST_DISABLE_BABEL: "true"
script:
- /analyzer run
brakeman-sast:
extends: .sast
image:
name: "$SAST_ANALYZER_IMAGE_PREFIX/brakeman:$SAST_ANALYZER_IMAGE_TAG"
rules: !reference [".reports:rules:sast", rules]
eslint-sast:
extends: .sast
image:
name: "$SAST_ANALYZER_IMAGE_PREFIX/eslint:$SAST_ANALYZER_IMAGE_TAG"
rules: !reference [".reports:rules:sast", rules]
nodejs-scan-sast:
extends: .sast
image:
name: "$SAST_ANALYZER_IMAGE_PREFIX/nodejs-scan:$SAST_ANALYZER_IMAGE_TAG"
rules: !reference [".reports:rules:sast", rules]
secrets-sast:
extends: .sast
image:
name: "$SAST_ANALYZER_IMAGE_PREFIX/secrets:3"
semgrep-sast:
rules: !reference [".reports:rules:sast", rules]
.secret-analyzer:
extends: .default-retry
needs: []
artifacts:
paths:
- gl-secret-detection-report.json # GitLab-specific
reports:
sast: gl-secret-detection-report.json
expire_in: 1 week # GitLab-specific
# We need to duplicate this job's definition because the rules
# defined in the extended jobs rely on local YAML anchors
# (`*if-default-refs`)
.dependency_scanning:
secret_detection:
rules: !reference [".reports:rules:secret_detection", rules]
.ds-analyzer:
# We need to re-`extends` from `dependency_scanning` as the `extends` here overrides the one from the template.
extends:
- .default-retry
- .reports:rules:dependency_scanning
stage: test
- dependency_scanning
needs: []
variables:
DS_MAJOR_VERSION: 2
DS_EXCLUDED_PATHS: "qa/qa/ee/fixtures/secure_premade_reports, spec, ee/spec" # GitLab-specific
SECURE_ANALYZERS_PREFIX: "registry.gitlab.com/gitlab-org/security-products/analyzers"
DS_EXCLUDED_PATHS: "qa/qa/ee/fixtures/secure_premade_reports, spec, ee/spec, tmp" # GitLab-specific
artifacts:
paths:
- gl-dependency-scanning-report.json # GitLab-specific
reports:
dependency_scanning: gl-dependency-scanning-report.json
expire_in: 1 week # GitLab-specific
script:
- /analyzer run
dependency_scanning gemnasium:
extends: .dependency_scanning
image:
name: "$SECURE_ANALYZERS_PREFIX/gemnasium:$DS_MAJOR_VERSION"
gemnasium-dependency_scanning:
before_script:
# git-lfs is needed for auto-remediation
- apk add git-lfs
......@@ -123,56 +74,43 @@ dependency_scanning gemnasium:
- apk add jq
# Lower execa severity based on https://gitlab.com/gitlab-org/gitlab/-/issues/223859#note_452922390
- jq '(.vulnerabilities[] | select (.cve == "yarn.lock:execa:gemnasium:05cfa2e8-2d0c-42c1-8894-638e2f12ff3d")).severity = "Medium"' gl-dependency-scanning-report.json > temp.json && mv temp.json gl-dependency-scanning-report.json
rules: !reference [".reports:rules:dependency_scanning", rules]
dependency_scanning bundler-audit:
extends: .dependency_scanning
image:
name: "$SECURE_ANALYZERS_PREFIX/bundler-audit:$DS_MAJOR_VERSION"
bundler-audit-dependency_scanning:
rules: !reference [".reports:rules:dependency_scanning", rules]
dependency_scanning retire-js:
extends: .dependency_scanning
image:
name: "$SECURE_ANALYZERS_PREFIX/retire.js:$DS_MAJOR_VERSION"
retire-js-dependency_scanning:
rules: !reference [".reports:rules:dependency_scanning", rules]
dependency_scanning gemnasium-python:
extends: .dependency_scanning
image:
name: "$SECURE_ANALYZERS_PREFIX/gemnasium-python:$DS_MAJOR_VERSION"
gemnasium-python-dependency_scanning:
rules: !reference [".reports:rules:dependency_scanning", rules]
# Analyze dependencies for malicious behavior
# See https://gitlab.com/gitlab-com/gl-security/security-research/package-hunter
package_hunter:
extends:
- .reports:schedule-dast
- .default-retry
- .reports:rules:package_hunter
stage: test
image:
name: registry.gitlab.com/gitlab-com/gl-security/security-research/package-hunter-cli:latest
entrypoint: [""]
needs: []
allow_failure: true
script:
- rm -r spec locale .git app/assets/images doc/
- cd .. && tar -I "gzip --best" -cf gitlab.tgz gitlab/
- DEBUG=* HTR_user=$PACKAGE_HUNTER_USER HTR_pass=$PACKAGE_HUNTER_PASS node /usr/src/app/cli.js analyze --format gitlab gitlab.tgz | tee $CI_PROJECT_DIR/gl-dependency-scanning-report.json
artifacts:
paths:
- gl-dependency-scanning-report.json # GitLab-specific
- gl-dependency-scanning-report.json
reports:
dependency_scanning: gl-dependency-scanning-report.json
expire_in: 1 week # GitLab-specific
expire_in: 1 week
license_scanning:
extends:
- .default-retry
- .reports:rules:license_scanning
stage: test
image:
name: "registry.gitlab.com/gitlab-org/security-products/analyzers/license-finder:3"
entrypoint: [""]
extends: .default-retry
needs: []
script:
- /run.sh analyze .
artifacts:
reports:
license_scanning: gl-license-scanning-report.json
expire_in: 1 week # GitLab-specific
dependencies: []
rules: !reference [".reports:rules:license_scanning", rules]
.gitlab/ci/review.gitlab-ci.yml
View file @ 4555e1b2
......@@ -34,10 +34,7 @@ review-build-cng:
- job: compile-production-assets
artifacts: false
script:
- BUILD_TRIGGER_TOKEN=$REVIEW_APPS_BUILD_TRIGGER_TOKEN ./scripts/trigger-build cng
# When the job is manual, review-deploy is also manual and we don't want people
# to have to manually start the jobs in sequence, so we do it for them.
- '[ -z $CI_JOB_MANUAL ] || scripts/api/play_job.rb --job-name "review-deploy"'
- ./scripts/trigger-build cng
.review-workflow-base:
extends:
......@@ -45,7 +42,6 @@ review-build-cng:
image: registry.gitlab.com/gitlab-org/gitlab-build-images:gitlab-helm3-kubectl1.14
variables:
HOST_SUFFIX: "${CI_ENVIRONMENT_SLUG}"
REVIEW_APPS_DOMAIN: "temp.gitlab-review.app" # FIXME: using temporary domain
DOMAIN: "-${CI_ENVIRONMENT_SLUG}.${REVIEW_APPS_DOMAIN}"
GITLAB_HELM_CHART_REF: "v4.6.3"
environment:
......@@ -59,7 +55,7 @@ review-deploy:
- .review-workflow-base
- .review:rules:review-deploy
stage: review
dependencies: []
needs: ["review-build-cng"]
resource_group: "review/${CI_COMMIT_REF_NAME}"
before_script:
- export GITLAB_SHELL_VERSION=$(<GITLAB_SHELL_VERSION)
......@@ -75,10 +71,6 @@ review-deploy:
- date
- deploy || (display_deployment_debug && exit 1)
- disable_sign_ups || (delete_release && exit 1)
# When the job is manual, review-qa-smoke is also manual and we don't want people
# to have to manually start the jobs in sequence, so we do it for them.
- '[ -z $CI_JOB_MANUAL ] || scripts/api/play_job.rb --job-name "review-qa-smoke"'
- '[ -z $CI_JOB_MANUAL ] || scripts/api/play_job.rb --job-name "review-performance"'
after_script:
# Run seed-dast-test-data.sh only when DAST_RUN is set to true. This is to pupulate review app with data for DAST scan.
# Set DAST_RUN to true when jobs are manually scheduled.
......@@ -123,9 +115,7 @@ review-stop:
- .use-docker-in-docker
image: registry.gitlab.com/gitlab-org/gitlab-build-images:gitlab-qa-alpine-ruby-2.7
stage: qa
# This is needed so that manual jobs with needs don't block the pipeline.
# See https://gitlab.com/gitlab-org/gitlab/-/issues/199979.
dependencies: ["review-deploy"]
needs: ["review-deploy"]
variables:
QA_ARTIFACTS_DIR: "${CI_PROJECT_DIR}/qa"
QA_CAN_TEST_GIT_PROTOCOL_V2: "false"
......@@ -175,9 +165,7 @@ review-performance:
name: sitespeedio/sitespeed.io
entrypoint: [""]
stage: qa
# This is needed so that manual jobs with needs don't block the pipeline.
# See https://gitlab.com/gitlab-org/gitlab/-/issues/199979.
dependencies: ["review-deploy"]
needs: ["review-deploy"]
before_script:
- export CI_ENVIRONMENT_URL="$(cat environment_url.txt)"
- echo "${CI_ENVIRONMENT_URL}"
......@@ -200,7 +188,7 @@ parallel-spec-reports:
- .review:rules:review-qa-all
image: ${GITLAB_DEPENDENCY_PROXY}ruby:2.7-alpine
stage: post-qa
dependencies: ["review-qa-all"]
needs: ["review-qa-all"]
variables:
NEW_PARALLEL_SPECS_REPORT: qa/report-new.html
BASE_ARTIFACT_URL: "${CI_PROJECT_URL}/-/jobs/${CI_JOB_ID}/artifacts/file/qa/"
......@@ -229,8 +217,8 @@ danger-review:
stage: test
needs: []
before_script:
- source ./scripts/utils.sh
- run_timed_command "bundle install --jobs=$(nproc) --path=vendor --retry=3 --quiet --with danger"
- source scripts/utils.sh
- bundle_install_script "--with danger"
- run_timed_command "retry yarn install --frozen-lockfile"
script:
- >
......@@ -242,12 +230,3 @@ danger-review:
else
run_timed_command "bundle exec danger --fail-on-errors=true --verbose"
fi
update-danger-review-cache:
extends:
- danger-review
- .shared:rules:update-cache
stage: prepare
script: echo 'Cache is fresh!'
cache:
policy: push # We want to rebuild the cache from scratch to ensure stale dependencies are cleaned up.
.gitlab/ci/rules.gitlab-ci.yml
View file @ 4555e1b2
......@@ -124,7 +124,7 @@
.docs-patterns: &docs-patterns
- ".gitlab/route-map.yml"
- "doc/**/*"
- ".markdownlint.json"
- ".markdownlint.yml"
- "scripts/lint-doc.sh"
.frontend-dependency-patterns: &frontend-dependency-patterns
......@@ -424,6 +424,13 @@
- <<: *if-default-refs
changes: *code-backstage-patterns
.frontend:rules:default-frontend-jobs-ee:
rules:
- <<: *if-not-ee
when: never
- <<: *if-default-refs
changes: *code-backstage-patterns
.frontend:rules:default-frontend-jobs-as-if-foss:
rules:
- <<: *if-not-ee
......@@ -518,6 +525,8 @@
.qa:rules:package-and-qa:
rules:
- <<: *if-not-ee
when: never
- <<: *if-dot-com-gitlab-org-and-security-merge-request
changes: *ci-qa-patterns
allow_failure: true
......@@ -929,6 +938,25 @@
- <<: *if-merge-request
changes: [".gitlab/ci/rails.gitlab-ci.yml"]
#########################
# Static analysis rules #
#########################
.static-analysis:rules:ee-and-foss:
rules:
- changes: *code-backstage-qa-patterns
.static-analysis:rules:as-if-foss:
rules:
- <<: *if-not-ee
when: never
- <<: *if-merge-request-title-as-if-foss
changes: *code-backstage-qa-patterns
- <<: *if-security-merge-request
changes: *code-backstage-qa-patterns
- <<: *if-merge-request
changes: *ci-patterns
#######################
# Vendored gems rules #
#######################
......@@ -975,6 +1003,16 @@
changes: *code-backstage-qa-patterns
allow_failure: true
.reports:rules:secret_detection:
rules:
- if: '$SECRET_DETECTION_DISABLED'
when: never
- if: '$CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH' # The Secret-Detection template already has a `secret_detection_default_branch` job
when: never
# - <<: *if-default-branch-refs # To be done in a later iteration: https://gitlab.com/gitlab-org/gitlab/issues/31160#note_278188255
- changes: *code-backstage-qa-patterns
allow_failure: true
.reports:rules:dependency_scanning:
rules:
- if: '$DEPENDENCY_SCANNING_DISABLED || $GITLAB_FEATURES !~ /\bdependency_scanning\b/'
......@@ -996,13 +1034,19 @@
when: manual
allow_failure: true
.reports:schedule-dast:
.reports:rules:schedule-dast:
rules:
- if: '$DAST_DISABLED || $GITLAB_FEATURES !~ /\bdast\b/'
when: never
- <<: *if-default-branch-schedule-nightly
allow_failure: true
.reports:rules:package_hunter:
rules:
- <<: *if-default-branch-schedule-2-hourly
- <<: *if-merge-request
changes: ["yarn.lock"]
.reports:rules:license_scanning:
rules:
- if: '$LICENSE_SCANNING_DISABLED || $GITLAB_FEATURES !~ /\blicense_scanning\b/'
......@@ -1042,7 +1086,6 @@
allow_failure: true
- <<: *if-dot-com-gitlab-org-merge-request
changes: *code-patterns
when: manual
allow_failure: true
- <<: *if-dot-com-gitlab-org-merge-request
changes: *qa-patterns
......@@ -1063,7 +1106,6 @@
allow_failure: true
- <<: *if-dot-com-gitlab-org-merge-request
changes: *code-qa-patterns
when: manual
allow_failure: true
- <<: *if-dot-com-gitlab-org-schedule
allow_failure: true
......@@ -1086,7 +1128,6 @@
allow_failure: true
- <<: *if-dot-com-gitlab-org-merge-request
changes: *code-qa-patterns
when: manual
allow_failure: true
.review:rules:review-qa-all:
......
.gitlab/ci/test-metadata.gitlab-ci.yml
View file @ 4555e1b2
......@@ -27,19 +27,19 @@ update-tests-metadata:
stage: post-test
dependencies:
- setup-test-env
- rspec migration pg11
- rspec migration pg12
- rspec frontend_fixture
- rspec-ee frontend_fixture
- rspec unit pg11
- rspec integration pg11
- rspec system pg11
- rspec-ee migration pg11
- rspec-ee unit pg11
- rspec-ee integration pg11
- rspec-ee system pg11
- rspec-ee unit pg11 geo
- rspec-ee integration pg11 geo
- rspec-ee system pg11 geo
- rspec unit pg12
- rspec integration pg12
- rspec system pg12
- rspec-ee migration pg12
- rspec-ee unit pg12
- rspec-ee integration pg12
- rspec-ee system pg12
- rspec-ee unit pg12 geo
- rspec-ee integration pg12 geo
- rspec-ee system pg12 geo
script:
- run_timed_command "retry gem install fog-aws mime-types activesupport rspec_profiling postgres-copy --no-document"
- source ./scripts/rspec_helpers.sh
......
.gitlab/issue_templates/Audit Event Proposal.md 0 → 100644
View file @ 4555e1b2
<!-- Audit Event documentation: See https://docs.gitlab.com/ee/administration/audit_events.html -->
## Audit need
<!-- Describe the real-world use case for the audit event you want to introduce, and explain the closest thing that GitLab already captures. -->
## Proposal
<!-- Describe the audit event you are proposing should be added, including any details of what should be captured, how, and why. -->
/label ~"Category:Audit Events"
/label ~"feature"
/label ~"group::compliance"
.gitlab/issue_templates/Basic Proposal.md deleted 100644 → 0
View file @ e570267f
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
/label ~"group::" ~"section::" ~"Category::" ~"GitLab Core"/~"GitLab Premium"/~"GitLab Ultimate"
-->
.gitlab/issue_templates/Experiment Idea.md 0 → 100644
View file @ 4555e1b2
## Experiment summary
We believe that... {describe your hypothesis in one sentence}
To verify that, we will... {describe your test in one sentence}
And we’ll measure the impact on... {metrics}
## Hypothesis
<!-- The hypothesis represents the high-level thought process in creating the experiment but does not need to be proven in one experiment. For example, you could have a hypothesis that “users would benefit from more easily being able to start a trial” and your first experiment could fail, that doesn’t void your hypothesis only indicates you may need to think of a new iterative experiment that would still align with your hypothesis. -->
## Business problem
<!-- Where the hypothesis is focused on the user/customer, the business problem represents why/how an experiment in this area could positively impact the business. For example, trials represent a significant way for GitLab to produce valuable leads for the sales team. -->
## Supporting data
<!-- Why should we run this experiment? What’s the potential impact? Show supporting data that’s both qualitative and quantitative. Quantitative example, we generate 30,000 sign ups a month and 900 trails within 90 days (3%) with a close rate of 10% and an IACV of $400. If we’re able to increase our trial volume by 10% percent (990 trials a month) we will generate an additional $3,600 IACV if our close rates remain constant. Qualitative example, in searching Zendesk I was able to find 10 support tickets in the last 30 days that referenced difficulties with starting a trial due to the user not being an admin. (all numbers are hypothetical and only listed for the purpose of having an example) -->
## Expected outcome
<!-- What is the expected outcome of this experiment, what metric are we trying to move? Are there any metrics we know we do not want to impact? For example, we want to impact IACV by increasing the rate at which users start trials within 30 days but we also want to ensure we don't increase the churn rate for users who've recently purchased. -->
## Experiment design & implementation
<!-- What is the experiment we’re going to run? How long do you believe it will need to run to reach significance? For example, our experiment would be to allow non-admins to request a trial through their admin, to detect a 10% change from our baseline conversion rate we’ll need a sample size of 57,000 (source Optimizely), with our current sign up rate of 30,000 a month this experiment will need to run for ~2 months. (all numbers are hypothetical and only listed for the purpose of having an example) -->
## ICE score
<!-- See https://about.gitlab.com/handbook/product/growth/#growth-ideation-and-prioritization -->
| Impact | Confidence | Ease | Score |
| ------ | ------ | ------ | ------ |
| value 1 | value 2 | value 3 | Average(1:3) |
## Known assumptions
<!-- This is an area to call out known assumptions in the experiment, this is especially helpful for any future colleagues that join the team so they understand other potential influences and how they were accounted for. This section is also helpful in framing possible scenarios and to keep the door open for the next steps. For example, we’re hoping our experiment will increase the number of people that start a trial but we’re assuming the conversion rate to paid and IACV will remain the same. This is a known assumption and depending on the results of the experiment could impact the direction we take on any future iterations. -->
## Results, lessons learned, next steps
<!-- What were the results of the experiment? Was the experiment a success or a failure? Based on the results should we remove the code or advocate that it become a permanent part of the experience for all users? Are there future experiments the team is going to run based off these results (include a link to new issue)? For example, our trial experiment was successful we increased the trial create rate by 10% but we saw a 1% drop in our close rate which means our net impact on IACV was negative $360 (990 * 0.09 * 400 compared tot he control of 900 * 0.1 * 400). Our next experiment (link) will focus on increasing the value once a user starts a trial. (all numbers are hypothetical and only listed for the purpose of having an example) -->
## Checklist
* [ ] Fill in the experiment summary and write more about the details of the experiment in the rest of the issue description. Some of these may be filled in through time (the "Result, learnings, next steps" section for example) but at least the experiment summary should be filled in right from the start.
* [ ] Add the label of the `group::` that will work on this experiment (if known).
* [ ] Mention the Product Manager, Engineering Manager, and at least one Product Designer from the group that owns the part of the product that the experiment will affect.
* [ ] Fill in the values in the [ICE score table](#ice-score) ping other team members for the values you aren’t confident about (i.e. engineering should almost always fill out the ease section). Add the ~"ICE Score Needed" label to indicate that the score is incomplete.
* [ ] Replace the ~"ICE Score Needed" with an ICE low/medium/high score label once all values in the ICE table have been added.
* [ ] Mention the [at]gitlab-core-team team and ask for their feedback.
/label ~"workflow::validation backlog" ~"experiment idea"
.gitlab/issue_templates/Feature Flag Removal.md 0 → 100644
View file @ 4555e1b2
<!-- Title suggestion: [Feature flag] Remove FEATURE_FLAG_NAME -->
## Feature
The `:feature_name` feature flag was previously [enabled by default](URL) and should be removed.
## Owners
- Group: ~"group::GROUP_NAME"
- Slack channel: `#g_GROUP_NAME`
- DRI: USERNAME
- PM: USERNAME
**Removal**
This is an __important__ phase, that should be either done in the next Milestone or as soon as possible. For the cleanup phase, please follow our documentation on how to [clean up the feature flag](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up).
- [ ] Remove `:feature_name` feature flag
- [ ] Remove all references to the feature flag from the codebase
- [ ] Remove the YAML definitions for the feature from the repository
- [ ] Create a Changelog Entry
- [ ] Clean up the feature flag from all environments by running this chatops command in `#production` channel `/chatops run feature delete some_feature`.
- [ ] Close this issue after the feature flag is removed from the codebase.
/label ~"feature flag" ~"technical debt"
/assign DRI
.gitlab/issue_templates/Feature Proposal - basic.md 0 → 100644
View file @ 4555e1b2
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
/label ~"group::" ~"section::" ~"Category::" ~"GitLab Core"/~"GitLab Premium"/~"GitLab Ultimate"
-->
.gitlab/issue_templates/Feature Proposal - lean.md 0 → 100644
View file @ 4555e1b2
<!-- This issue template can be used a great starting point for feature requests. The last section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. -->
### Release notes
<!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " -->
### Problem to solve
<!-- What is the user problem you are trying to solve with this issue? -->
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
/label ~"feature" ~"group::" ~"section::" ~"Category::" ~"GitLab Free"/~"GitLab Premium"/~"GitLab Ultimate"
<!--- Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
Other sections to consider adding:
### Intended users
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
* [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager)
* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
* [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager)
* [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer)
* [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test)
* [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops)
* [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer)
* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)
### User experience goal
What is the single user experience workflow this problem addresses?
For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>"
https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/
### Further details
Include use cases, benefits, goals, or any other details that will help us understand the problem better.
### Permissions and Security
<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html
* [ ] Add expected impact to members with no access (0)
* [ ] Add expected impact to Guest (10) members
* [ ] Add expected impact to Reporter (20) members
* [ ] Add expected impact to Developer (30) members
* [ ] Add expected impact to Maintainer (40) members
* [ ] Add expected impact to Owner (50) members
### Documentation
See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change
* Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/workflow.html
* If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html
### Availability & Testing
This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.
What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?
Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change
See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning
### What does success look like, and how can we measure that?
Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.
### What is the type of buyer?
What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/
In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#three-tiers
### Is this a cross-stage feature?
Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features -->
/label ~documentation
/label ~direction
.gitlab/issue_templates/Feature proposal - detailed.md 0 → 100644
View file @ 4555e1b2
<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. -->
### Release notes
<!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " -->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." -->
### Intended users
<!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
* [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager)
* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
* [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager)
* [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer)
* [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test)
* [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops)
* [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer)
* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)
* [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor)
-->
### User experience goal
<!-- What is the single user experience workflow this problem addresses?
For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>"
https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ -->
### Proposal
<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. -->
### Permissions and Security
<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html
* [ ] Add expected impact to members with no access (0)
* [ ] Add expected impact to Guest (10) members
* [ ] Add expected impact to Reporter (20) members
* [ ] Add expected impact to Developer (30) members
* [ ] Add expected impact to Maintainer (40) members
* [ ] Add expected impact to Owner (50) members -->
### Documentation
<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change
* Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/workflow.html
* If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html -->
### Availability & Testing
<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.
What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?
Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change
See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->
### Available Tier
<!-- This section should be used for setting the appropriate tier that this feature will belong to. Pricing can be found here: https://about.gitlab.com/pricing/
* Free
* Premium/Silver
* Ultimate/Gold
-->
### What does success look like, and how can we measure that?
<!--
Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.
Create tracking issue using the the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md
-->
### What is the type of buyer?
<!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/
In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#three-tiers -->
### Is this a cross-stage feature?
<!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features -->
### Links / references
<!-- Label reminders - you should have one of each of the following labels.
Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
/label ~devops:: ~group: ~Category:
/label ~"GitLab Free"/~"GitLab Premium"/~"GitLab Ultimate"
/label ~feature
/label ~documentation
/label ~direction
.gitlab/issue_templates/Feature proposal.md deleted 100644 → 0
View file @ e570267f
<!-- The first section "Release notes" is required if you want to have your release post blog MR auto generated. Currently in BETA, details on the **release post item generator** can be found in the handbook: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator and this video: https://www.youtube.com/watch?v=rfn9ebgTwKg. The next four sections: "Problem to solve", "Intended users", "User experience goal", and "Proposal", are strongly recommended in your first draft, while the rest of the sections can be filled out during the problem validation or breakdown phase. However, keep in mind that providing complete and relevant information early helps our product team validate the problem and start working on a solution. -->
### Release notes
<!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " -->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity as a user story. For example, "As a (who), I want (what), so I can (why/value)." -->
### Intended users
<!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
* [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager)
* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
* [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager)
* [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer)
* [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test)
* [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops)
* [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer)
* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)
* [Eddie (Content Editor)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#eddie-content-editor)
-->
### User experience goal
<!-- What is the single user experience workflow this problem addresses?
For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>"
https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/ -->
### Proposal
<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->
### Further details
<!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. -->
### Permissions and Security
<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html
* [ ] Add expected impact to members with no access (0)
* [ ] Add expected impact to Guest (10) members
* [ ] Add expected impact to Reporter (20) members
* [ ] Add expected impact to Developer (30) members
* [ ] Add expected impact to Maintainer (40) members
* [ ] Add expected impact to Owner (50) members -->
### Documentation
<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change
* Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/workflow.html
* If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html -->
### Availability & Testing
<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.
What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?
Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change
See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->
### Available Tier
<!-- This section should be used for setting the appropriate tier that this feature will belong to. Pricing can be found here: https://about.gitlab.com/pricing/
* Free
* Premium/Silver
* Ultimate/Gold
-->
### What does success look like, and how can we measure that?
<!--
Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.
Create tracking issue using the the Snowplow event tracking template. See https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Snowplow%20event%20tracking.md
-->
### What is the type of buyer?
<!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/
In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#three-tiers -->
### Is this a cross-stage feature?
<!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features -->
### Links / references
<!-- Label reminders - you should have one of each of the following labels.
Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
/label ~devops:: ~group: ~Category:
/label ~"GitLab Core"/~"GitLab Premium"/~"GitLab Ultimate"
/label ~feature
/label ~documentation
/label ~direction
.gitlab/issue_templates/Geo Replicate a new blob type.md 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
.gitlab/issue_templates/Lean Feature Proposal.md deleted 100644 → 0
View file @ e570267f
<!-- This issue template can be used a great starting point for feature requests. The last section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. -->
### Release notes
<!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " -->
### Problem to solve
<!-- What is the user problem you are trying to solve with this issue? -->
### Proposal
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
/label ~"feature" ~"group::" ~"section::" ~"Category::" ~"GitLab Core"/~"GitLab Premium"/~"GitLab Ultimate"
<!--- Use the following resources to find the appropriate labels:
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
Other sections to consider adding:
### Intended users
Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
Personas are described at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/
* [Cameron (Compliance Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#cameron-compliance-manager)
* [Parker (Product Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#parker-product-manager)
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Presley (Product Designer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#presley-product-designer)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Sidney (Systems Administrator)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sidney-systems-administrator)
* [Sam (Security Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sam-security-analyst)
* [Rachel (Release Manager)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#rachel-release-manager)
* [Alex (Security Operations Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#alex-security-operations-engineer)
* [Simone (Software Engineer in Test)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#simone-software-engineer-in-test)
* [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops)
* [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#priyanka-platform-engineer)
* [Dana (Data Analyst)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#dana-data-analyst)
### User experience goal
What is the single user experience workflow this problem addresses?
For example, "The user should be able to use the UI/API/.gitlab-ci.yml with GitLab to <perform a specific task>"
https://about.gitlab.com/handbook/engineering/ux/ux-research-training/user-story-mapping/
### Further details
Include use cases, benefits, goals, or any other details that will help us understand the problem better.
### Permissions and Security
<!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)?
Consider adding checkboxes and expectations of users with certain levels of membership https://docs.gitlab.com/ee/user/permissions.html
* [ ] Add expected impact to members with no access (0)
* [ ] Add expected impact to Guest (10) members
* [ ] Add expected impact to Reporter (20) members
* [ ] Add expected impact to Developer (30) members
* [ ] Add expected impact to Maintainer (40) members
* [ ] Add expected impact to Owner (50) members
### Documentation
See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change
* Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/workflow.html
* If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html
### Availability & Testing
This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.
What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?
Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change
See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning
### What does success look like, and how can we measure that?
Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this.
### What is the type of buyer?
What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/
In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#three-tiers
### Is this a cross-stage feature?
Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features -->
/label ~documentation
/label ~direction
.gitlab/merge_request_templates/Documentation.md
View file @ 4555e1b2
......@@ -23,7 +23,11 @@
- ~"development guidelines" when changing docs under `doc/development/*`, `CONTRIBUTING.md`, or `README.md`.
- ~"development guidelines" and ~"Documentation guidelines" when changing docs under `development/documentation/*`.
- ~"development guidelines" and ~"Description templates (.gitlab/\*)" when creating/updating issue and MR description templates.
- [ ] Assign the [designated Technical Writer](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments).
- [ ] [Request a review](https://docs.gitlab.com/ee/development/code_review.html#dogfooding-the-reviewers-feature)
from the [designated Technical Writer](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments).
/label ~documentation
/assign me
Do not add the ~"feature", ~"frontend", ~"backend", ~"bug", or ~"database" labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.
......@@ -68,5 +72,3 @@ For more information, see our documentation on [Merging a merge request](https:/
1. [ ] Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
1. [ ] Ensure a release milestone is set.
1. [ ] If there has not been a technical writer review, [create an issue for one using the Doc Review template](https://gitlab.com/gitlab-org/gitlab/issues/new?issuable_template=Doc%20Review).
/label ~documentation
.gitlab/merge_request_templates/New End To End Test.md
View file @ 4555e1b2
......@@ -14,7 +14,8 @@ Please link to the respective test case in the testcases project
- [ ] Ensure that no [transient bugs](https://about.gitlab.com/handbook/engineering/quality/issue-triage/#transient-bugs) are hidden accidentally due to the usage of `waits` and `reloads`.
- [ ] Verify the tags to ensure it runs on the desired test environments.
- [ ] If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged.
- [ ] (If applicable) Create a follow-up issue to document [the special setup](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/running_tests_that_require_special_setup.html) necessary to run the test: ISSUE_LINK
- [ ] (If applicable) Create a follow-up issue to document [the special setup](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/running_tests_that_require_special_setup.html) necessary to run the test: ISSUE_LINK
- [ ] If the test requires an admin's personal access token, ensure that the test passes on your local with and without the `GITLAB_QA_ADMIN_ACCESS_TOKEN` provided.
<!-- Base labels. -->
/label ~"Quality" ~"QA" ~test
......
.gitpod.yml
View file @ 4555e1b2
image: registry.gitlab.com/gitlab-org/gitlab-development-kit/gitpod-workspace:gitpod-workspace-image
image: registry.gitlab.com/gitlab-org/gitlab-development-kit/gitpod-workspace:stable
tasks:
......@@ -7,8 +7,6 @@ tasks:
- init: |
echo "$(date) – Copying GDK" | tee -a /workspace/startup.log
rm -r /workspace/.rvm
mv $HOME/.rvm-workspace /workspace/.rvm
cp -r $HOME/gitlab-development-kit /workspace/
(
set -e
......
.haml-lint.yml
View file @ 4555e1b2
......@@ -110,7 +110,6 @@ linters:
- Layout/EmptyLineAfterGuardClause
- Layout/LeadingCommentSpace
- Layout/SpaceAroundOperators
- Layout/SpaceBeforeBlockBraces
- Layout/SpaceBeforeComma
- Layout/SpaceBeforeFirstArg
- Layout/SpaceInsideHashLiteralBraces
......@@ -118,7 +117,6 @@ linters:
- Layout/TrailingEmptyLines
- Lint/LiteralInInterpolation
- Lint/ParenthesesAsGroupedExpression
- Lint/RedundantWithIndex
- Lint/SafeNavigationConsistency
- Metrics/BlockNesting
- Naming/VariableName
......@@ -133,7 +131,6 @@ linters:
- Style/IdenticalConditionalBranches
- Style/NegatedIf
- Style/NestedTernaryOperator
- Style/ParenthesesAroundCondition
- Style/SelfAssignment
- Style/TernaryParentheses
- Style/TrailingCommaInHashLiteral
......
.markdownlint.json deleted 100644 → 0
View file @ e570267f
{
"default": true,
"first-header-h1": true,
"header-style": {
"style": "atx"
},
"ul-style": {
"style": "dash"
},
"no-trailing-spaces": false,
"line-length": false,
"no-duplicate-header": {
"allow_different_nesting": true
},
"no-trailing-punctuation": {
"punctuation": ".,;:!。，；：！？"
},
"ol-prefix": {
"style": "one"
},
"no-inline-html": false,
"hr-style": {
"style": "---"
},
"no-emphasis-as-heading": false,
"first-line-h1": false,
"code-block-style": {
"style": "fenced"
},
"proper-names": {
"names": [
"Akismet",
"Alertmanager",
"API",
"Asana",
"Auth0",
"Authentiq",
"Azure",
"Bamboo",
"Bitbucket",
"Bugzilla",
"CAS",
"CentOS",
"Consul",
"Debian",
"DevOps",
"Docker",
"DockerSlim",
"Elasticsearch",
"Facebook",
"fastlane",
"fluent-plugin-redis-slowlog",
"GDK",
"Geo",
"Git LFS",
"git-annex",
"Git",
"Gitaly",
"GitHub",
"GitLab Geo",
"GitLab Monitor",
"GitLab Operator",
"GitLab Pages",
"GitLab Rails",
"GitLab Runner",
"GitLab Shell",
"GitLab Workhorse",
"GitLab",
"Gitleaks",
"Gmail",
"Google",
"Grafana",
"Gzip",
"Helm",
"HipChat",
"ID",
"Ingress",
"jasmine-jquery",
"JavaScript",
"Jaeger",
"Jenkins",
"Jira",
"Jira Cloud",
"Jira Server",
"jQuery",
"JSON",
"JupyterHub",
"Karma",
"Kerberos",
"Knative",
"Kubernetes",
"LDAP",
"Let's Encrypt",
"Markdown",
"markdownlint",
"Mattermost",
"Microsoft",
"Minikube",
"MinIO",
"ModSecurity",
"NGINX Ingress",
"NGINX",
"OAuth",
"OAuth 2",
"OmniAuth",
"Omnibus GitLab",
"OpenID",
"OpenShift",
"PgBouncer",
"PostgreSQL",
"Praefect",
"Prometheus",
"Puma",
"puma-worker-killer",
"Python",
"Rake",
"Redis",
"Redmine",
"reCAPTCHA",
"Ruby",
"runit",
"Salesforce",
"SAML",
"Sentry",
"Sidekiq",
"Shibboleth",
"Slack",
"SMTP",
"SpotBugs",
"SSH",
"Tiller",
"TOML",
"Trello",
"Trello Power-Ups",
"TypeScript",
"Twitter",
"Ubuntu",
"Ultra Auth",
"Unicorn",
"unicorn-worker-killer",
"URL",
"WebdriverIO",
"YAML",
"YouTrack"
],
"code_blocks": false
}
}
.markdownlint.yml 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
.overcommit.yml.example
View file @ 4555e1b2
......@@ -48,7 +48,7 @@ PreCommit:
enabled: true
description: 'Lint documentation for Markdown errors'
required_executable: 'node_modules/.bin/markdownlint'
flags: ['--config', '.markdownlint.json', 'doc/**/*.md']
flags: ['--config', '.markdownlint.yml', 'doc/**/*.md']
install_command: 'yarn install'
include:
- 'doc/**/*.md'
......
.rubocop.yml
View file @ 4555e1b2
......@@ -307,6 +307,9 @@ Cop/ActiveRecordAssociationReload:
- 'spec/**/*'
- 'ee/spec/**/*'
Cop/ActiveModelErrorsDirectManipulation:
Enabled: true
Gitlab/AvoidFeatureGet:
Enabled: true
......@@ -572,6 +575,9 @@ Rails/SaveBang:
- 'ee/spec/**/*.rb'
- 'qa/spec/**/*.rb'
- 'qa/qa/specs/**/*.rb'
Exclude:
- spec/models/wiki_page/**/*
- spec/models/wiki_page_spec.rb
Cop/PutProjectRoutesUnderScope:
Include:
......
.rubocop_manual_todo.yml
View file @ 4555e1b2
This diff is collapsed.
.rubocop_todo.yml
View file @ 4555e1b2
This diff is collapsed.
.solargraph.yml.example 0 → 100644
View file @ 4555e1b2
---
include:
- "**/*.rb"
exclude:
- "**/spec/**/*"
- qa/qa/specs/features/**/*
- vendor/**/*
- ".bundle/**/*"
require: []
domains: []
reporters:
- rubocop
- require_not_found
require_paths: []
plugins: []
max_files: 15000
CHANGELOG.md
View file @ 4555e1b2
This diff is collapsed.
Dangerfile
View file @ 4555e1b2
......@@ -2,11 +2,15 @@
require 'gitlab-dangerfiles'
Gitlab::Dangerfiles.import_plugins(danger)
danger.import_plugin('danger/plugins/*.rb')
gitlab_dangerfiles = Gitlab::Dangerfiles::Engine.new(self)
gitlab_dangerfiles.import_plugins
return if helper.release_automation?
danger.import_plugin('danger/plugins/*.rb')
gitlab_dangerfiles.import_dangerfiles
project_helper.rule_names.each do |rule|
danger.import_dangerfile(path: File.join('danger', rule))
end
......
GITALY_SERVER_VERSION
View file @ 4555e1b2
This diff is collapsed.
GITLAB_ELASTICSEARCH_INDEXER_VERSION
View file @ 4555e1b2
This diff is collapsed.
GITLAB_KAS_VERSION
View file @ 4555e1b2
This diff is collapsed.
GITLAB_PAGES_VERSION
View file @ 4555e1b2
This diff is collapsed.
GITLAB_SHELL_VERSION
View file @ 4555e1b2
This diff is collapsed.
Gemfile
View file @ 4555e1b2
This diff is collapsed.
Gemfile.lock
View file @ 4555e1b2
This diff is collapsed.
README.md
View file @ 4555e1b2
This diff is collapsed.
app/assets/images/learn_gitlab/get_started.svg 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/images/learn_gitlab/graduation_hat.svg 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/images/learn_gitlab/rectangle.svg 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/actioncable_link.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/admin/users/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/admin/users/tabs.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/analytics/devops_report/devops_score.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/awards_handler.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/behaviors/date_picker.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/behaviors/shortcuts/shortcut.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/blob/viewer/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/boards/constants.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/boards/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/code_quality_walkthrough/constants.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/code_quality_walkthrough/index.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/code_quality_walkthrough/utils.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/compare_autocomplete.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/content_editor/components/divider.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/blockquote.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/bold.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/code.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/document.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/dropcursor.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/gapcursor.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/hard_break.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/heading.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/history.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/image.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/italic.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/link.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/list_item.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/paragraph.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/content_editor/extensions/text.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/constants.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/store/actions.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/store/index.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/store/mutation_types.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/store/mutations.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/store/state.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/cycle_analytics/utils.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/diffs/constants.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/due_date_select.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ensure_data.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/flash.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/gfm_auto_complete.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/header.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/help/help.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/ide/components/file_alert.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/lib/alerts/environments.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/lib/alerts/index.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/messages.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/services/gql.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/stores/actions/alert.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/stores/getters/alert.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/stores/mutations/alert.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/ide/stores/state.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/invite_member/constants.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/invite_member/event_hub.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/issuable/components/status_box.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/issuable_form.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/issues_list/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/issues_list/utils.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/jobs/constants.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/jobs/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/learn_gitlab/track_learn_gitlab.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/lib/graphql.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/lib/utils/keys.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/lib/utils/recurrence.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/lib/utils/vuex_module_mappers.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/main.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/members/components/members_tabs.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/members/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/members/utils.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/merge_request/eventhub.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/monitoring/utils.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/nav/components/top_nav_app.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/nav/components/top_nav_menu_item.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/nav/index.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/nav/mount.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/nav/stores/index.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/notes.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/pages/help/show/index.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/pages/projects/compare/index.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/pages/projects/new/components/app.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/pipeline_new/utils/filter_variables.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/pipelines/utils.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/project_select.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/releases/stores/getters.js deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/javascripts/releases/util.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/repository/index.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/repository/router.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/runner/components/runner_type_badge.vue 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/runner/constants.js 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/runner/graphql/get_runner.query.graphql 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/sidebar/constants.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/sidebar/fragmentTypes.json 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/sidebar/graphql.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/task_list.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/javascripts/tracking.js
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/framework.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/framework/blank.scss deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/assets/stylesheets/framework/diffs.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/framework/kbd.scss 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/framework/lists.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/page_bundles/new_namespace.scss 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/pages/editor.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/pages/help.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/pages/issuable.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/pages/note_form.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/pages/notes.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/pages/projects.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/themes/_dark.scss
View file @ 4555e1b2
This diff is collapsed.
app/assets/stylesheets/utilities.scss
View file @ 4555e1b2
This diff is collapsed.
app/channels/graphql_channel.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/channels/issues_channel.rb deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/controllers/admin/cohorts_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/admin/groups_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/admin/labels_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/admin/runners_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/admin/users_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/application_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/autocomplete_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/boards/issues_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/boards/lists_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/boards_actions.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/floc_opt_out.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/integrations/params.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/lfs_request.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/page_limiter.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/renders_commits.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/concerns/service_params.rb deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/controllers/concerns/wiki_actions.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/confirmations_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/dashboard_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/graphql_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/groups/autocomplete_sources_controller.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/controllers/groups/boards_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/groups_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/import/base_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/import/github_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/invites_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/passwords_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/projects/blob_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/projects/logs_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/projects/tags_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/projects_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/registrations/invites_controller.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/controllers/registrations_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/root_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/search_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/sessions_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/terraform/services_controller.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/controllers/uploads_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/users_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/controllers/whats_new_controller.rb
View file @ 4555e1b2
This diff is collapsed.
app/experiments/application_experiment.rb
View file @ 4555e1b2
This diff is collapsed.
app/experiments/concerns/project_commit_count.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/experiments/empty_repo_upload_experiment.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/analytics/cycle_analytics/stage_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/autocomplete/users_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/ci/pipelines_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/ci/runners_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/deploy_tokens/tokens_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/deployments_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/environment_names_finder.rb deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/finders/environments/environment_names_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/environments/environments_by_deployments_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/environments/environments_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/environments_by_deployments_finder.rb deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/finders/environments_finder.rb deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/finders/fork_targets_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/group_members_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/group_projects_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/issuable_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/issuables/author_filter.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/issuables/base_filter.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/issues_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/issues_finder/params.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/license_template_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/merge_requests_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/namespaces/projects_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/notes_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/go/package_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/go/version_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/group_or_project_package_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/npm/package_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/package_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/packages_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/pypi/package_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/packages/pypi/packages_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/projects/groups_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/projects/members/effective_access_level_finder.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/finders/projects_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/snippets_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/template_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/todos_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/users_finder.rb
View file @ 4555e1b2
This diff is collapsed.
app/finders/users_with_pending_todos_finder.rb deleted 100644 → 0
View file @ e570267f
This diff is collapsed.
app/graphql/gitlab_schema.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/graphql_triggers.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/boards/create.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/boards/lists/base_update.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/boards/update.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/ci/job/base.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/ci/job/play.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/ci/job/retry.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/commits/create.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/issues/create.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/issues/move.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/issues/set_locked.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/issues/update.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/labels/create.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/mutations/merge_requests/set_draft.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/queries/burndown_chart/burnup.query.graphql 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/ci/runner_resolver.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/ci/runners_resolver.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/ci/template_resolver.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/issues_resolver.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/packages_base_resolver.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/release_resolver.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/resolvers/releases_resolver.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/subscriptions/base_subscription.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/subscriptions/issuable_updated.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/access_level_enum.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/base_argument.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/base_enum.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/base_field.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/blob_viewer_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/board_list_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/board_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/code_quality_degradation_severity_enum.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/job_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/pipeline_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/runner_access_level_enum.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/runner_sort_enum.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/runner_status_enum.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/runner_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/runner_type_enum.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/stage_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/ci/template_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/duration_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/group_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/issuable_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/issue_connection_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/issue_sort_enum.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/issue_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/label_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/merge_request_type.rb
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/merge_requests/assignee_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
app/graphql/types/metadata/kas_type.rb 0 → 100644
View file @ 4555e1b2
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7