gitlab-triage 1.7.1 → 1.11.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0c67fa47a534d7f13d781966693423d4916292ec9924e4913492e63eb00a5f5a
-  data.tar.gz: ecd0946de096e97fd73ca3b7aa243842b3bf2cdccff9b6746b4034893789d672
+  metadata.gz: e02cd169e252e4656441f6e9268314c2b968935957dbcb906ae3048ee7045da4
+  data.tar.gz: 3b58c8b37e3f82878272641ad848239c74623499f0e309ba0ac9aaaf6803cf0f
 SHA512:
-  metadata.gz: cc9bc7902d7e3e96186d2f2593c76ef64bd74005857548e6b8d5014a70e3be1d75447083b06de4e7bb923651b0d9696029dfdf64ef3011672fc8a1ffbb4d8ca4
-  data.tar.gz: aa02ac6fbefebc75589e4da546c52e48150408aebdacd34fc83f0cf24a373d19c3e63de52cbfba6847bcc778b285ba21e9c4ea037d886d36122998d2bebbf9d7
+  metadata.gz: 181a6a5055a61b5d8c78f36d047dfef269a92a7d0173598a490e5420ab04fb267c9c42be2ae9bef31a815eb7730a15b921dde2b1834e49dcc20d0969d4986f54
+  data.tar.gz: 621d6e208ad9dcdd034931ca0656778e5247c6aa3f3e6fa8edf53ed401795452f0d136eec259df8a377e36589de866fc7ee949a792cd1fa5b2c07257cab577ee

data/.gitignore

@@ -6,7 +6,6 @@
 /Gemfile.lock
 /_yardoc/
 /coverage/
-/doc/
 /pkg/
 /spec/reports/
 /tmp/

data/.gitlab-ci.yml

@@ -1,49 +1,68 @@
-image: ruby:2.6
-
 stages:
   - prepare
   - test
   - triage
+  - deploy
 
-.default-only:
-  only:
-    refs:
-      - master
-      - merge_requests
-      - tags
-
-.default-before_script:
+default:
+  image: ruby:2.7
+  tags:
+    - gitlab-org
+  cache:
+    key:
+      files:
+        - Gemfile
+        - gitlab-triage.gemspec
+    paths:
+      - vendor/ruby
+      - Gemfile.lock
+    policy: pull
   before_script:
+    - ruby --version
     - gem install bundler --no-document --version 2.0.2
-    - bundle install --jobs $(nproc) --retry 3 --quiet
+    - bundle --version
+    - bundle install --jobs $(nproc) --path=vendor --retry 3 --quiet
+    - bundle check
+
+workflow:
+  rules:
+    # For merge requests, create a pipeline.
+    - if: '$CI_MERGE_REQUEST_IID'
+    # For `master` branch, create a pipeline (this includes on schedules, pushes, merges, etc.).
+    - if: '$CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH'
+    # For tags, create a pipeline.
+    - if: '$CI_COMMIT_TAG'
+
+.use-docker-in-docker:
+  image: docker:${DOCKER_VERSION}
+  services:
+    - docker:${DOCKER_VERSION}-dind
+  variables:
+    DOCKER_VERSION: "19.03.0"
+    DOCKER_DRIVER: overlay2
+    DOCKER_HOST: tcp://docker:2375
+    DOCKER_TLS_CERTDIR: ""
+  tags:
+    # See https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/7019 for tag descriptions
+    - gitlab-org-docker
 
 ###################
 ## Prepare stage ##
 ###################
 setup-test-env:
-  extends: .default-only
   stage: prepare
   script:
-    - ruby --version
-    - gem install bundler --no-document
-    - bundle --version
-    - bundle install --clean --jobs $(nproc) --path=vendor --retry=3 --quiet
-    - bundle check
+    - echo "Setup done!"
   cache:
-    key: "$CI_JOB_NAME-ruby-2.6"
-    paths:
-      - vendor/ruby
-      - Gemfile.lock
+    policy: pull-push
   artifacts:
     paths:
-      - vendor/ruby
       - Gemfile.lock
 
 ################
 ## Test stage ##
 ################
 rubocop:
-  extends: [".default-only", ".default-before_script"]
   stage: test
   needs: ["setup-test-env"]
   dependencies: ["setup-test-env"]
@@ -55,20 +74,15 @@ rubocop:
       - .cache/rubocop_cache/
 
 # We need to copy this job's definition from the Code-Quality.gitlab-ci.yml
-# template because `only` is set without `refs`, so it takes precedence over `.default-only`.
+# template because `only` is set without `refs`, so it takes precedence over default workflow rules.
 # See https://gitlab.com/gitlab-org/gitlab-ce/issues/66767.
 code_quality:
-  extends: .default-only
-  needs: ["setup-test-env"]
-  dependencies: ["setup-test-env"]
+  extends: .use-docker-in-docker
   stage: test
-  image: docker:stable
   allow_failure: true
-  services:
-    - docker:stable-dind
   variables:
-    DOCKER_DRIVER: overlay2
     DOCKER_TLS_CERTDIR: ""
+  before_script: []
   script:
     - |
       if ! docker info &>/dev/null; then
@@ -85,14 +99,9 @@ code_quality:
     reports:
       codequality: gl-code-quality-report.json
     expire_in: 1 week
-  except:
-    variables:
-      - $CODE_QUALITY_DISABLED
 
 specs:
-  extends: [".default-only", ".default-before_script"]
   needs: ["setup-test-env"]
-  dependencies: ["setup-test-env"]
   stage: test
   script:
     - bundle exec rake spec
@@ -101,17 +110,24 @@ specs:
 ## Triage stage ##
 ##################
 dry-run:gitlab-triage:
-  extends: [".default-only", ".default-before_script"]
   needs: ["setup-test-env"]
-  dependencies: ["setup-test-env"]
   stage: triage
   script:
-    - bundle exec rake install:local
+    - bundle exec rake build
+    - gem install pkg/*.gem
+    - which gitlab-triage
+    - gitlab-triage --version
     - gitlab-triage --help
     - gitlab-triage --init
-    - gitlab-triage --dry-run --debug --token $API_TOKEN --source-id $CI_PROJECT_PATH
+    - gitlab-triage --dry-run --debug --token $GITLAB_API_TOKEN --source-id $CI_PROJECT_PATH
 
 # This job requires allows to override the `CI_PROJECT_PATH` variable when triggered.
 dry-run:custom:
   extends: dry-run:gitlab-triage
-  when: manual
+  rules:
+    - when: manual
+      allow_failure: true
+
+include:
+  - project: 'gitlab-org/quality/pipeline-common'
+    file: '/ci/gem-release.yml'

data/.gitlab/merge_request_templates/Release.md

@@ -0,0 +1,35 @@
+<!-- Replace `v4.5.0` with the previous release here, and `e18d76b309e42888759c1effe96767f13e34ae55`
+with the latest commit from https://gitlab.com/gitlab-org/gitlab-triage/commits/master that will be included in the release. -->
+- Diff: https://gitlab.com/gitlab-org/gitlab-triage/compare/v4.5.0...e18d76b309e42888759c1effe96767f13e34ae55
+
+- Release notes:
+
+<!-- Keep the sections order but remove the empty sections -->
+
+```markdown
+### New features and features updates
+
+- !aaa <Title of the aaa MR>.
+
+### Fixes
+
+- !bbb <Title of the bbb MR>.
+
+### Doc changes
+
+- !ccc <Title of the ccc MR>.
+
+### Other changes (tooling, technical debt)
+
+- !ddd <Title of the ddd MR>.
+```
+
+- Checklist before merging:
+  - [ ] Diff link is up-to-date.
+  - [ ] Based on the diff, `lib/gitlab/triage/version.rb` is updated, according to [SemVer](https://semver.org).
+  - [ ] Release notes are accurate.
+
+- Checklist after merging:
+  - [ ] [Update the release notes for the newly created tag](docs/release_process.md#how-to).
+
+/label ~"Engineering Productivity" ~"ep::triage" ~"tooling::workflow"

data/.rubocop.yml

@@ -11,3 +11,6 @@ AllCops:
 
 Rails/Output:
   Enabled: false
+
+Metrics/LineLength:
+  Max: 152

data/Gemfile

@@ -4,5 +4,5 @@ source 'https://rubygems.org'
 gemspec
 
 group :test do
-  gem 'gitlab-styles', '~> 3.0'
+  gem 'gitlab-styles', '~> 3.3.0'
 end

data/Guardfile

@@ -24,7 +24,7 @@
 #  * zeus: 'zeus rspec' (requires the server to be started separately)
 #  * 'just' rspec: 'rspec'
 
-guard :rspec, cmd: "bundle exec rspec" do
+guard :rspec, cmd: "bundle exec rspec -f doc" do
   require "guard/rspec/dsl"
   dsl = Guard::RSpec::Dsl.new(self)
 

data/README.md

@@ -58,7 +58,7 @@ resource_rules:
             interval: 5
           state: opened
           labels:
-            - No Label
+            - None
         limits:
           most_recent: 50
         actions:
@@ -66,6 +66,7 @@ resource_rules:
             - needs attention
           mention:
             - markglenfletcher
+          move: gitlab-org/backlog
           comment: |
             {{author}} This issue is unlabelled after 5 days. It needs attention. Please take care of this before the end of #{2.days.from_now.strftime('%Y-%m-%d')}
           summarize:
@@ -85,9 +86,27 @@ resource_rules:
               /label ~"needs attention"
   merge_requests:
     rules:
-      []
+      - name: My policy
+        conditions:
+          state: opened
+          labels:
+            - None
+        limits:
+          most_recent: 50
+        actions:
+          labels:
+            - needs attention
+          comment_type: thread
+          comment: |
+            {{author}} This issue is unlabelled. Please add one or more labels.
 ```
 
+### Real world example
+
+We're enforcing multiple polices with pipeline schedules at [triage-ops](
+https://gitlab.com/gitlab-org/quality/triage-ops), where we're also
+extensively utilizing the [plugins system](#can-i-customize).
+
 ### Fields
 
 A policy consists of the following fields:
@@ -210,6 +229,22 @@ conditions:
     - feature proposal
 ```
 
+###### Predefined special label names
+
+Basing on the [issues API](https://docs.gitlab.com/ee/api/issues.html), there
+are two special predefined label names we can use here:
+
+* `None`: This indicates that no labels were present
+* `Any`: This indicates that any labels were presented
+
+Example:
+
+```yml
+conditions:
+  labels:
+    - None
+```
+
 ###### Labels brace expansion
 
 We could expand the labels by using brace expansion, which is a pattern
@@ -506,7 +541,9 @@ Available action types:
 - [`remove_labels` action](#remove-labels-action)
 - [`status` action](#status-action)
 - [`mention` action](#mention-action)
+- [`move` action](#move-action)
 - [`comment` action](#comment-action)
+- [`comment_type` action option](#comment-type-action-option)
 - [`summarize` action](#summarize-action)
 
 ##### Labels action
@@ -515,6 +552,10 @@ Adds a number of labels to the resource.
 
 Accepts an array of strings. Each element is the name of a label to add.
 
+If any of the labels doesn't exist, the automation will stop immediately so
+that if a label is renamed or deleted, you'll have to explicitly update or remove
+it in your policy file.
+
 Example:
 
 ```yml
@@ -530,6 +571,10 @@ Removes a number of labels from the resource.
 
 Accepts an array of strings. Each element is the name of a label to remove.
 
+If any of the labels doesn't exist, the automation will stop immediately so
+that if a label is renamed or deleted, you'll have to explicitly update or remove
+it in your policy file.
+
 Example:
 
 ```yml
@@ -572,6 +617,19 @@ actions:
     - markglenfletcher
 ```
 
+##### Move action
+
+Moves an issue (merge request is not supported yet) to the specified project.
+
+Accepts a string containing the target project path.
+
+Example:
+
+```yml
+actions:
+  move: target/project_path
+```
+
 ##### Comment action
 
 Adds a comment to the resource.
@@ -619,6 +677,26 @@ actions:
     {{author}} Are you still interested in finishing this merge request?
 ```
 
+##### Comment type action option
+
+Determines the type of comment to be added to the resource.
+
+The following comment types are supported:
+
+- `comment` (default): creates a regular comment on the resource
+- `thread`: starts a resolvable thread (discussion) on the resource
+
+For merge requests, if `comment_type` is set to `thread`, we can also configure that [all threads should be resolved before merging](https://docs.gitlab.com/ee/user/discussions/#only-allow-merge-requests-to-be-merged-if-all-threads-are-resolved), therefore this comment can prevent it from merging.
+
+Example:
+
+```yml
+actions:
+  comment_type: thread
+  comment: |
+    {{author}} Are you still interested in finishing this merge request?
+```
+
 ###### Harnessing Quick Actions
 
 [GitLab's quick actions feature](https://docs.gitlab.com/ce/user/project/quick_actions.html) is available in Core.
@@ -839,7 +917,7 @@ Which could generate an issue like:
 
 Here's a list of currently available Ruby expression API:
 
-##### API
+##### Methods for `Issue` and `MergeRequest` (the context)
 
 | Name                    | Return type     | Description |
 | ----                    | ----            | ----        |
@@ -854,6 +932,12 @@ Here's a list of currently available Ruby expression API:
 | project_path            | String          | The path with namespace to the issues or merge requests project |
 | full_resource_reference | String          | A full reference incuding project path to the issue or merge request |
 
+##### Methods for `MergeRequest` (merge request context)
+
+| Method              | Return type | Description |
+| ----                | ----        | ----        |
+| first_contribution? | Boolean     | `true` if it's the author's first contribution to the project; `false` otherwise. This API requires an additional API request for the merge request, thus would be slower. |
+
 ##### Methods for `Milestone`
 
 | Method      | Return type | Description |
@@ -930,6 +1014,7 @@ Usage: gitlab-triage [options]
     -r, --require [string]           Require a file before performing
     -d, --debug                      Print debug information
     -h, --help                       Print help message
+        --all-projects               Process all projects visible to `--token`
         --init                       Initialize the project with a policy file
         --init-ci                    Initialize the project with a .gitlab-ci.yml file
 ```
@@ -939,15 +1024,23 @@ Usage: gitlab-triage [options]
 Triaging against a specific project:
 
 ```
-gitlab-triage --dry-run --token $API_TOKEN --source-id gitlab-org/triage
+gitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org/triage
 ```
 
 Triaging against a whole group:
 
 ```
-gitlab-triage --dry-run --token $API_TOKEN --source-id gitlab-org --source groups
+gitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org --source groups
 ```
 
+Triaging against an entire instance:
+
+```
+gitlab-triage --dry-run --token $GITLAB_API_TOKEN --all-projects
+```
+
+> **Note:** The `--all-projects` option will process all resources for all projects visible to the specified `$GITLAB_API_TOKEN`
+
 #### Running on GitLab CI pipeline
 
 You can enforce policies using a scheduled pipeline:
@@ -957,7 +1050,7 @@ run:triage:triage:
   stage: triage
   script:
     - gem install gitlab-triage
-    - gitlab-triage --token $API_TOKEN --source-id $CI_PROJECT_PATH
+    - gitlab-triage --token $GITLAB_API_TOKEN --source-id $CI_PROJECT_PATH
   only:
     - schedules
 ```
@@ -971,7 +1064,7 @@ Yes, you can override the host url using the following options:
 ##### CLI
 
 ```
-gitlab-triage --dry-run --token $API_TOKEN --source-id gitlab-org/triage --host-url https://gitlab.host.com
+gitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org/triage --host-url https://gitlab.host.com
 ```
 
 ##### Policy file
@@ -1008,7 +1101,7 @@ Gitlab::Triage::Resource::Context.include MyPlugin
 And then run it with:
 
 ```shell
-gitlab-triage -r ./my_plugin.rb --token $API_TOKEN --source-id gitlab-org/triage
+gitlab-triage -r ./my_plugin.rb --token $GITLAB_API_TOKEN --source-id gitlab-org/triage
 ```
 
 This allows you to use `has_severity_label?` in the Ruby condition:
@@ -1030,3 +1123,7 @@ resource_rules:
 ### Contributing
 
 Please refer to the [Contributing Guide](CONTRIBUTING.md).
+
+## Release Process
+
+Please refer to the [Release Process](docs/release_process.md).