{"id":10244064,"url":"https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage","last_synced_at":"2025-09-05T04:30:59.695Z","repository":{"id":50110471,"uuid":"3430480","full_name":"gitlab-org/ruby/gems/gitlab-triage","owner":"gitlab-org","description":"This gem allows to triage issues, merge requests, epics in an automated way with policies defined as YAML. Documentation: https://www.rubydoc.info/gems/gitlab-triage","archived":false,"fork":false,"pushed_at":null,"size":null,"stargazers_count":195,"open_issues_count":131,"forks_count":80,"subscribers_count":null,"default_branch":"master","last_synced_at":"2024-04-13T13:05:18.713Z","etag":null,"topics":["hacktoberfest"],"latest_commit_sha":null,"homepage":null,"language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":null,"metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE.md","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":".gitlab/CODEOWNERS","security":null,"support":null}},"created_at":"2017-06-03T04:10:44.539Z","updated_at":"2024-04-12T15:43:32.811Z","dependencies_parsed_at":"2022-08-22T06:50:32.037Z","dependency_job_id":null,"html_url":"https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage","commit_stats":null,"previous_names":[],"tags_count":64,"template":null,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repositories/gitlab-org%2Fruby%2Fgems%2Fgitlab-triage","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repositories/gitlab-org%2Fruby%2Fgems%2Fgitlab-triage/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repositories/gitlab-org%2Fruby%2Fgems%2Fgitlab-triage/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repositories/gitlab-org%2Fruby%2Fgems%2Fgitlab-triage/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/owners/gitlab-org","download_url":"https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage/-/archive/master/gitlab-triage-master.zip","host":{"name":"gitlab.com","url":"https://gitlab.com","kind":"gitlab","repositories_count":4514979,"owners_count":6376,"icon_url":"https://github.com/gitlab.png","version":null,"created_at":"2022-05-30T11:31:42.605Z","updated_at":"2024-07-18T11:24:13.055Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/gitlab.com/owners"}},"keywords":["hacktoberfest"],"created_at":"2024-05-24T21:03:11.343Z","updated_at":"2024-09-08T06:31:06.365Z","avatar_url":null,"language":null,"funding_links":[],"categories":["Communication and Coordination","Coordination and Communication"],"sub_categories":[],"readme":"[![pipeline status](https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage/badges/master/pipeline.svg)](https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage/-/commits/master)\n\n# GitLab Triage Project\n\n[[_TOC_]]\n\nThis project allows to automate triaging of issues and merge requests for GitLab projects or groups.\n\n## Note this Gem is not supported by the GitLab Support team\n\nIf you are a customer who has a GitLab License, **support for this gem is not covered by that license agreement as this is not part of the GitLab Product**. Feel free to open an issue in this project and the maintainers may be able to help.\n\n## gitlab-triage gem\n\n### Abstract\n\nThe `gitlab-triage` gem aims to enable project managers and maintainers to\nautomatically triage Issues and Merge Requests in GitLab projects or groups\nbased on defined policies.\n\nSee [Running with the installed gem](#running-with-the-installed-gem) for how to specify a project or a\ngroup.\n\n### What is a triage policy?\n\nTriage policies are defined on a resource level basis, resources being:\n- Epics\n- Issues\n- Merge Requests\n- Branches\n\nEach policy can declare a number of conditions that must all be satisfied before\na number of actions are carried out.\n\nSummary policies are special policies that join multiple policies together to\ncreate a summary issue with all the sub-policies' summaries, see\n[Summary policies](#summary-policies).\n\n### Defining a policy\n\nPolicies are defined in a policy file (by default `./.triage-policies.yml`).\nThe format of the file is [YAML](https://en.wikipedia.org/wiki/YAML).\n\n\u003e **Note:** You can use the [`--init`](#usage) option to add an example\n[`.triage-policies.yml` file](support/.triage-policies.example.yml) to your\nproject.\n\nSelect which resource to add the policy to:\n- `epics`\n- `issues`\n- `merge_requests`\n- `branches`\n\nAnd create an array of `rules` to define your policies:\n\nFor example:\n\n```yml\nresource_rules:\n  epics:\n    rules:\n      - name: My epic policy\n        conditions:\n          date:\n            attribute: updated_at\n            condition: older_than\n            interval_type: days\n            interval: 5\n          state: opened\n          labels:\n            - None\n        actions:\n          labels:\n            - needs attention\n          mention:\n            - markglenfletcher\n          comment: |\n            {{author}} This epic 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')}\n  issues:\n    rules:\n      - name: My issue policy\n        conditions:\n          date:\n            attribute: updated_at\n            condition: older_than\n            interval_type: days\n            interval: 5\n          state: opened\n          labels:\n            - None\n        limits:\n          most_recent: 50\n        actions:\n          labels:\n            - needs attention\n          mention:\n            - markglenfletcher\n          move: gitlab-org/backlog\n          comment: |\n            {{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')}\n          summarize:\n            destination: gitlab-org/ruby/gems/gitlab-triage\n            title: |\n              #{resource[:type].capitalize} require labels\n            item: |\n              - [ ] [{{title}}]({{web_url}}) {{labels}}\n            redact_confidential_resources: false\n            summary: |\n              The following issues require labels:\n\n              {{items}}\n\n              Please take care of them before the end of #{7.days.from_now.strftime('%Y-%m-%d')}\n\n              /label ~\"needs attention\"\n  merge_requests:\n    rules:\n      - name: My merge request policy\n        conditions:\n          state: opened\n          labels:\n            - None\n        limits:\n          most_recent: 50\n        actions:\n          labels:\n            - needs attention\n          comment_type: thread\n          comment: |\n            {{author}} This issue is unlabelled. Please add one or more labels.\n  branches:\n    rules:\n      - name: My branch policy\n        conditions:\n          date:\n            attribute: committed_date\n            condition: older_than\n            interval_type: months\n            interval: 6\n          name: ^feature\n        actions:\n          delete: true\n```\n\n### Real world example\n\nWe're enforcing multiple polices with pipeline schedules at [triage-ops](\nhttps://gitlab.com/gitlab-org/quality/triage-ops), where we're also\nextensively utilizing the [plugins system](#can-i-customize).\n\n### Fields\n\nA policy consists of the following fields:\n- [Name field](#name-field)\n- [Conditions field](#conditions-field)\n- [Limits field](#limits-field)\n- [Actions field](#actions-field)\n\n#### Name field\n\nThe name field is used to describe the purpose of the individual policy.\n\nExample:\n\n```yml\nname: Policy name\n```\n\n#### Conditions field\n\nUsed to declare a condition that must be satisfied by a resource before actions will be taken.\n\nAvailable condition types:\n- [`date` condition](#date-condition)\n- [`milestone` condition](#milestone-condition)\n- [`iteration` condition](#iteration-condition)\n- [`state` condition](#state-condition)\n- [`votes` condition](#votes-condition)\n- [`labels` condition](#labels-condition)\n- [`forbidden_labels` condition](#forbidden-labels-condition)\n- [`no_additional_labels` condition](#no-additional-labels-condition)\n- [`author_username` condition](#author-username-condition)\n- [`author_member` condition](#author-member-condition)\n- [`assignee_member` condition](#assignee-member-condition)\n- [`draft` condition](#draft-condition)\n- [`source_branch` condition](#source-branch-condition)\n- [`target_branch` condition](#target-branch-condition)\n- [`health_status` condition](#health-status-condition)\n- [`weight` condition](#weight-condition)\n- [`issue_type` condition](#issue-type-condition)\n- [`discussions` condition](#discussions-condition)\n- [`protected` condition](#protected-condition)\n- [`ruby` condition](#ruby-condition)\n- [`reviewer_id` condition](#reviewer-id-condition)\n\n##### Date condition\n\nAccepts a hash of fields.\n\n| Field           | Type    | Values                                                                     | Required  |\n| ---------       | ----    |----------------------------------------------------------------------------| --------  |\n| `attribute`     | string  | `created_at`, `updated_at`, `merged_at`, `authored_date`, `committed_date` | yes       |\n| `condition`     | string  | `older_than`, `newer_than`                                                 | yes       |\n| `interval_type` | string  | `minutes`, `hours`, `days`, `weeks`, `months`, `years`                     | yes       |\n| `interval`      | integer | integer                                                                    | yes       |\n\u003e **Note:**\n\u003e   - `merged_at` only works on merge requests.\n\u003e   - `closed_at` is not supported in the GitLab API, but can be used in a [`ruby` condition](#ruby-condition).\n\u003e   - `committed_date` and `authored_date` only works for branches.\n\nExample:\n\n```yml\nconditions:\n  date:\n    attribute: updated_at\n    condition: older_than\n    interval_type: months\n    interval: 12\n```\n\n\u003e **Note:** If the GitLab server is giving 500 error with this option, it\n\u003e can mean that it's taking too much time to query this, and it's timing out.\n\u003e A workaround for this is that we can filter in Ruby. If you need this\n\u003e workaround, specify this with `filter_in_ruby: true`\n\u003e\n\u003e ```yaml\n\u003e conditions:\n\u003e date:\n\u003e   attribute: updated_at\n\u003e   condition: older_than\n\u003e   interval_type: months\n\u003e   interval: 12\n\u003e   filter_in_ruby: true\n\u003e ```\n\n##### Milestone condition\n\nAccepts the name of a milestone to filter upon. Also accepts the following timebox values:\n\n- `none`\n- `any`\n- `upcoming`\n- `started`\n\nSee the [`milestone_id` API field documentation](https://docs.gitlab.com/ee/api/issues.html) for their meaning.\n\nExample:\n\n```yml\nconditions:\n  milestone: v1\n```\n\n##### Iteration condition\n\nAccepts the name of an iteration to filter upon. Also accepts the following\ntimebox values:\n\n- `none`\n- `any`\n\nSee the [`iteration_id` API field documentation](https://docs.gitlab.com/ee/api/issues.html) for their meaning.\n\nExample:\n\n```yml\nconditions:\n  iteration: none\n```\n\n\u003e **Note:** This query is not supported using GraphQL yet.\n\n##### State condition\n\nAccepts a string.\n\n| State             | Type    | Value    |\n| ---------         | ----    | ------   |\n| Closed issues/MRs | string  | `closed` |\n| Open issues/MRs   | string  | `opened` |\n| Locked issues     | string  | `locked` |\n| Merged merge requests | string  | `merged` |\n\nExample:\n\n```yml\nconditions:\n  state: opened\n```\n\n##### Votes condition\n\nAccepts a hash of fields.\n\n| Field           | Type    | Values                              | Required  |\n| ---------       | ----    | ----                                | --------  |\n| `attribute`     | string  | `upvotes`, `downvotes`              | yes       |\n| `condition`     | string  | `less_than`, `greater_than`         | yes       |\n| `threshold`     | integer | integer                             | yes       |\n\nExample:\n\n```yml\nconditions:\n  votes:\n    attribute: upvotes\n    condition: less_than\n    threshold: 10\n```\n\n##### Labels condition\n\nAccepts an array of strings. Each element in the array represents the name of a label to filter on.\n\n\u003e **Note:** **All** specified labels must be present on the resource for the condition to be satisfied\n\nExample:\n\n```yml\nconditions:\n  labels:\n    - feature proposal\n```\n\n###### Predefined special label names\n\nBasing on the [issues API](https://docs.gitlab.com/ee/api/issues.html), there\nare two special predefined label names we can use here:\n\n* `None`: This indicates that no labels were present\n* `Any`: This indicates that any labels were presented\n\nExample:\n\n```yml\nconditions:\n  labels:\n    - None\n```\n\n###### Labels brace expansion\n\nWe could expand the labels by using brace expansion, which is a pattern\nsurrounded by using braces: `{}`. For now, we support 2 kinds of brace\nexpansion:\n\n1. List: `{ apple, orange }`\n2. Sequence: `{1..4}`\n\n\u003e **Note:**\n\u003e   - Spaces around the items are ignored.\n\u003e   - Do not rely on the expansion ordering. This is subject to change.\n\n###### List\n\nThe name of a label can contain a list of items, written like\n`{ apple, orange }`. For each item, the rule will be duplicated with the new\nlabel name.\n\nExample:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Add missing ~Quality label\n        conditions:\n          labels:\n            - Quality:test-{ gap, infra }\n        actions:\n          labels:\n            - Quality\n```\n\nWhich will be expanded into:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Add missing ~Quality label\n        conditions:\n          labels:\n            - Quality:test-gap\n        actions:\n          labels:\n            - Quality\n\n      - name: Add missing ~Quality label\n        conditions:\n          labels:\n            - Quality:test-infra\n        actions:\n          labels:\n            - Quality\n```\n\n\u003e **Note:**\n\u003e   If you want to define a full label expansion, you'll need to [force string](https://yaml.org/YAML_for_ruby.html#forcing_strings) or [quote string](https://yaml.org/YAML_for_ruby.html#single-quoted_strings) because otherwise it won't be considered a string due to the YAML parser.\n\u003e   For example, we can quote the expression like `'{ apple, orange }'`, which will create 2 rules, for the two specified labels.\n\n###### Sequence\n\nThe name of a label can contain one or more sequence conditions, written\nlike `{0..9}`, which means `0`, `1`, `2`, and so on up to `9`. For each\nnumber, the rule will be duplicated with the new label name.\n\nExample:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Add missing ~\"missed\\-deliverable\" label\n        conditions:\n          labels:\n            - missed:{10..11}.{0..1}\n            - deliverable\n        actions:\n          labels:\n            - missed deliverable\n```\n\nWhich will be expanded into:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Add missing ~\"missed\\-deliverable\" label\n        conditions:\n          labels:\n            - missed:10.0\n            - deliverable\n        actions:\n          labels:\n            - missed deliverable\n\n      - name: Add missing ~\"missed\\-deliverable\" label\n        conditions:\n          labels:\n            - missed:10.1\n            - deliverable\n        actions:\n          labels:\n            - missed deliverable\n\n      - name: Add missing ~\"missed\\-deliverable\" label\n        conditions:\n          labels:\n            - missed:11.0\n            - deliverable\n        actions:\n          labels:\n            - missed deliverable\n\n      - name: Add missing ~\"missed\\-deliverable\" label\n        conditions:\n          labels:\n            - missed:11.1\n            - deliverable\n        actions:\n          labels:\n            - missed deliverable\n```\n\n##### Forbidden labels condition\n\nAccepts an array of strings. Each element in the array represents the name of a label to filter on.\n\n\u003e **Note:** **All** specified labels must be absent on the resource for the condition to be satisfied\n\nExample:\n\n```yml\nconditions:\n  forbidden_labels:\n    - awaiting feedback\n```\n\n##### No additional labels condition\n\nAccepts a boolean. If `true` the resource cannot have more labels than those specified by the `labels` condition.\n\nExample:\n\n```yml\nconditions:\n  labels:\n    - feature proposal\n  no_additional_labels: true\n```\n\n##### Author username condition\n\nAccepts the username to filter on.\n\nExample:\n\n```yml\nconditions:\n  author_username: gitlab-bot\n```\n\n##### Author Member condition\n\nThis condition determines whether the author of a resource is a member of the specified group or project.\n\nThis is useful for determining whether Issues or Merge Requests have been raised by a Community Contributor.\n\nAccepts a hash of fields.\n\n| Field           | Type    | Values                              | Required  |\n| ---------       | ----    | ----                                | --------  |\n| `source`        | string  | `group`, `project`                  | yes       |\n| `condition`     | string  | `member_of`, `not_member_of`        | yes       |\n| `source_id`     | integer or string | gitlab-org/gitlab      | yes       |\n\nExample:\n\n```yml\nconditions:\n  author_member:\n    source: group\n    condition: not_member_of\n    source_id: 9970\n```\n\n##### Assignee member condition\n\nThis condition determines whether the assignee of a resource is a member of the specified group or project.\n\nAccepts a hash of fields.\n\n| Field           | Type    | Values                              | Required  |\n| ---------       | ----    | ----                                | --------  |\n| `source`        | string  | `group`, `project`                  | yes       |\n| `condition`     | string  | `member_of`, `not_member_of`        | yes       |\n| `source_id`     | integer or string | gitlab-org/gitlab      | yes       |\n\nExample:\n\n```yml\nconditions:\n  assignee_member:\n    source: group\n    condition: not_member_of\n    source_id: 9970\n```\n\n##### Draft condition\n\n**This condition is only applicable for merge requests.**\n\nAccepts a boolean. If `true`, only draft MRs are returned. If `false`, only non-draft MRs are returned.\n\nExample:\n\n```yml\nconditions:\n  draft: true\n```\n\n##### Source branch condition\n\n**This condition is only applicable for merge requests.**\n\nAccepts the name of a source branch to filter upon.\n\nExample:\n\n```yml\nconditions:\n  source_branch: 'feature-branch'\n```\n\n##### Target branch condition\n\n**This condition is only applicable for merge requests.**\n\nAccepts the name of a target branch to filter upon.\n\nExample:\n\n```yml\nconditions:\n  target_branch: 'master'\n```\n\n##### Health Status condition\n\n**This condition is only applicable for issues.**\n\nAccepts a string per the [API documentation](https://docs.gitlab.com/ee/api/issues.html#list-issues).\n\n| State                  | Type    | Value     |\n| ---------              | ----    | ------    |\n| Any health status      | string  | `Any`  |\n| No health status       | string  | `None`  |\n| Specific health status | string  | One of `on_track`, `needs_attention` or `at_risk` |\n\nExample:\n\n```yml\nconditions:\n  health_status: Any\n```\n\n\u003e **Note:** This query is not supported using GraphQL yet.\n\n##### Weight condition\n\n**This condition is only applicable for issues.**\n\nAccepts a string per the [API documentation](https://docs.gitlab.com/ee/api/issues.html#list-issues).\n\n| State           | Type    | Value     |\n| ---------       | ----    | ------    |\n| Any weight      | string  | `Any`  |\n| No weight       | string  | `None`  |\n| Specific weight | integer  | integer |\n\nExample:\n\n```yml\nconditions:\n  weight: Any\n```\n\n##### Issue type condition\n\n**This condition is only applicable for issues.**\n\nAccepts a string per the [API documentation](https://docs.gitlab.com/ee/api/issues.html#list-issues). This condition can only filter by one issue type.\n\n| Issue type      | Type    | Value       |\n| ---------       | ----    | ------      |\n| Regular issue   | string  | `issue`     |\n| Incident        | string  | `incident`  |\n| Test case       | string  | `test_case` |\n\nExample:\n\n```yml\nconditions:\n  issue_type: issue\n```\n\n##### Discussions condition\n\nAccepts a hash of fields.\n\n| Field           | Type    | Values                              | Required  |\n| ---------       | ----    | ----                                | --------  |\n| `attribute`     | string  | `threads`, `notes`                  | yes       |\n| `condition`     | string  | `less_than`, `greater_than`         | yes       |\n| `threshold`     | integer | integer                             | yes       |\n\nExample:\n\n```yml\nconditions:\n  discussions:\n    attribute: threads\n    condition: greater_than\n    threshold: 15\n```\n\n##### Protected condition\n\n**This condition is only applicable for branches**\n\nAccept a boolean.\nIf not specified, default to `false` to filter out protected branches.\n\n##### Ruby condition\n\nThis condition allows users to write a Ruby expression to be evaluated for\neach resource. If it evaluates to a truthy value, it satisfies the condition.\nIf it evaluates to a falsey value, it does not satisfy the condition.\n\nAccepts a string as the Ruby expression.\n\nExample:\n\n```yml\nconditions:\n  ruby: Date.today \u003e milestone.succ.start_date\n```\n\nIn the above example, this describes that we want to act on the resources\nwhich passed the next active milestone's starting date.\n\nHere `milestone` will return a `Gitlab::Triage::Resource::Milestone` object,\nrepresenting the milestone of the questioning resource. `Milestone#succ` would\nreturn the next active milestone, based on the `start_date` of all milestones\nalong with the representing milestone. If the milestone was coming from a\nproject, then it's based on all active milestones in that project. If the\nmilestone was coming from a group, then it's based on all active milestones\nin the group.\n\nIf we also want to handle some edge cases, for example, a resource might not\nhave a milestone, and a milestone might not be active, and there might not\nhave a next milestone. We could instead write something like:\n\n```yml\nconditions:\n  ruby: milestone\u0026.active? \u0026\u0026 milestone\u0026.succ \u0026\u0026 Date.today \u003e milestone.succ.start_date\n```\n\nThis will make it only act on resources which have active milestones and\nthere exists next milestone which has already started.\n\nSince `closed_at` is not a queryable attribute in the GitLab API, we can use a Ruby expression to filter resources like:\n\n```yml\nconditions:\n  ruby: resource[:closed_at] \u003e 7.days.ago.strftime('%Y-%m-%dT00:00:00.000Z')\n```\n\nSee [Ruby expression API](#ruby-expression-api) for the list of currently\navailable API.\n\n#### Limits field\n\nLimits restrict the number of resources on which an action is carried out. They\ncan be useful when combined with conditions that return a large number of\nresources. For example, if the conditions are satisfied by thousands of issues a\nlimit can be configured to process only fifty of them to avoid making an\noverwhelming number of changes at once.\n\nAccepts a key and value pair where the key is `most_recent` or `oldest` and the\nvalue is the number of resources to act on. The following table outlines how\neach key affects the sorting and order of resources that it limits.\n\n| Name / Key    | Sorted by    | Order      |\n| ---------     | ----         | ------     |\n| `most_recent` | `created_at` | descending |\n| `oldest`      | `created_at` | ascending  |\n\nExample:\n\n```yml\nlimits:\n  most_recent: 50\n```\n\n##### Reviewer id condition\n\n**This condition is only applicable for merge requests.**\n\nAccepts the id of a user to filter on. Also accepts `none` or `any`.\n\nExample:\n\n```yml\nconditions:\n  reviewer_id: any\n```\n\n#### Actions field\n\nUsed to declare an action to be carried out on a resource if **all** conditions are satisfied.\n\nAvailable action types:\n- [`labels` action](#labels-action)\n- [`remove_labels` action](#remove-labels-action)\n- [`status` action](#status-action)\n- [`mention` action](#mention-action)\n- [`move` action](#move-action)\n- [`comment` action](#comment-action)\n  - [`redact_confidential_resources` option](#redact-confidential-resources-option)\n- [`comment_type` action option](#comment-type-action-option)\n- [`summarize` action](#summarize-action)\n- [`comment_on_summary` action](#comment-on-summary-action)\n- [`issue` action](#create-a-new-issue-from-each-resource)\n- [`delete` action](#delete-action)\n\n##### Labels action\n\nAdds a number of labels to the resource.\n\nAccepts an array of strings. Each element is the name of a label to add.\n\nIf any of the labels doesn't exist, the automation will stop immediately so\nthat if a label is renamed or deleted, you'll have to explicitly update or remove\nit in your policy file.\n\nExample:\n\n```yml\nactions:\n  labels:\n    - feature proposal\n    - awaiting feedback\n```\n\n##### Remove labels action\n\nRemoves a number of labels from the resource.\n\nAccepts an array of strings. Each element is the name of a label to remove.\n\nIf any of the labels doesn't exist, the automation will stop immediately so\nthat if a label is renamed or deleted, you'll have to explicitly update or remove\nit in your policy file.\n\nExample:\n\n```yml\nactions:\n  remove_labels:\n    - feature proposal\n    - awaiting feedback\n```\n\n##### Status action\n\nChanges the status of the resource.\n\nAccepts a string.\n\n| State transition    | Type    | Value     |\n| ---------           | ----    | ------    |\n| Close the resource  | string  | `close`   |\n| Reopen the resource | string  | `reopen`  |\n\nExample:\n\n```yml\nactions:\n  status: close\n```\n\n##### Mention action\n\nMentions a number of users.\n\nAccepts an array of strings. Each element is the username of a user to mention.\n\nExample:\n\n```yml\nactions:\n  mention:\n    - rymai\n    - markglenfletcher\n```\n\n##### Move action\n\nMoves an issue (merge request is not supported yet) to the specified project.\n\nAccepts a string containing the target project path.\n\nExample:\n\n```yml\nactions:\n  move: target/project_path\n```\n\n##### Comment action\n\nAdds a comment to the resource.\n\nAccepts a string, and placeholders. Placeholders should be wrapped in double\ncurly braces, e.g. `{{author}}`.\n\nThe following placeholders are supported:\n\n- `created_at`: the resource's creation date\n- `updated_at`: the resource's last update date\n- `closed_at`: the resource's closed date (if applicable)\n- `merged_at`: the resource's merged date (if applicable)\n- `state`: the resources's current state: `opened`, `closed`, `merged`\n- `author`: the username of the resource's author as `@user1`\n- `assignee`: the username of the resource's assignee as `@user1`\n- `assignees`: the usernames of the resource's assignees as `@user1, @user2`\n- `reviewers`: the usernames ot the resource's reviewers as `@user1, @user2` (if applicable)\n- `closed_by`: the user that closed the resource as `@user1` (if applicable) \n- `merged_by`: the user that merged the resource as `@user1` (if applicable)\n- `milestone`: the resource's current milestone\n- `labels`: the resource's labels as `~label1, ~label2`\n- `upvotes`: the resources's upvotes count\n- `downvotes`: the resources's downvotes count\n- `title`: the resource's title\n- `web_url`: the web URL pointing to the resource\n- `full_reference`: the full reference of the resource as `namespace/project#12`, `namespace/project!42`, `namespace/project\u002672`\n- `type`: the type of the resources. For now, only `issues`, `merge_requests`, and `epics` are supported.\n\nIf the resource doesn't respond to the placeholder, or if the field is `nil`,\nthe placeholder is not replaced.\n\nExample without placeholders:\n\n```yml\nactions:\n  comment: |\n    Closing this issue automatically\n```\n\nExample with placeholders:\n\n```yml\nactions:\n  comment: |\n    {{author}} Are you still interested in finishing this merge request?\n```\n\n###### Redact confidential resources option\n\nDetermines if the data of confidential resources is redacted.\n\nIf the option is set to `true` or not set, data from confidential will appear as `(confidential)`. \\\nWhen it is set to `false`, everything will be revealed and visible.\n\nExample:\n\n```yml\nactions:\n  redact_confidential_resources: false\n  comment: |\n    {{author}} Are you still interested in finishing this merge request?\n```\n\n##### Comment type action option\n\nDetermines the type of comment to be added to the resource.\n\nThe following comment types are supported:\n\n- `comment` (default): creates a regular comment on the resource\n- `thread`: starts a resolvable thread (discussion) on the resource\n\nFor 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.\n\nExample:\n\n```yml\nactions:\n  comment_type: thread\n  comment: |\n    {{author}} Are you still interested in finishing this merge request?\n```\n\n###### Comment internal action option\n\nDetermines whether the note is added as an internal comment to the resource.\n\nIf the option is set to `false` or not set, the comment will not be internal. \\\nWhen it is set to `true`, the comment will be internal.\n\nExample:\n\n```yml\nactions:\n  comment_internal: true\n  comment: |\n    This issue has breached SLA, please take a look @team!\n```\n\n###### Harnessing Quick Actions\n\n[GitLab's quick actions feature](https://docs.gitlab.com/ce/user/project/quick_actions.html) is available in Core.\nAll of the operations supported by executing a quick action can be carried out via the comment action.\n\nIf GitLab triage does not support an operation natively, it may be possible via a quick action in a comment.\n\nFor example:\n- Flagging an issue as [confidential](https://docs.gitlab.com/ce/user/project/issues/confidential_issues.html)\n- [Locking issue discussion](https://docs.gitlab.com/ce/user/discussions/#lock-discussions)\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Mark bugs as confidential\n        conditions:\n          state: opened\n          ruby: !resource[:confidential]\n          labels:\n            - bug\n        actions:\n          comment: |\n            /confidential\n```\n\n###### Ruby expression\n\nThe comment can also contain Ruby expression, using Ruby's own string\ninterpolation syntax: `#{ expression }`. This gives you the most flexibility.\nSuppose you want to mention the next active milestone relative to the one\nassociated with the resource, you can write:\n\n```yml\nactions:\n  comment: |\n    Please move this to %\"#{milestone.succ.title}\".\n```\n\nSee [Ruby expression API](#ruby-expression-api) for the list of currently\navailable API.\n\n\u003e **Note:** If you get a syntax error due to stray braces (`{` or `}`), use `\\`\nto escape it. For example:\n\u003e\n\u003e ```yml\n\u003e actions:\n\u003e  comment: |\n\u003e    If \\} comes first and/or following \\{, you'll need to escape them. If it's just { wrapping something } then you don't need to, but it's also fine to escape them like \\{ this \\} if you prefer.\n\u003e ```\n\n##### Summarize action\n\nGenerates an issue summarizing what was triaged.\n\nAccepts a hash of fields.\n\n| Field         | Type   | Description                                     | Required | Placeholders | Ruby expression | Default        |\n| ----          | ----   | ----                                            | ----     | ----         | ----            | ----           |\n| `title`       | string | The title of the generated issue                | yes      | yes          | yes             |                |\n| `destination` | integer or string | The project ID or path to create the generated issue in | no   | no              | no             | source project |\n| `item`        | string | Template representing each triaged resource     | no       | yes          | yes             |                |\n| `summary`     | string | The description of the generated issue          | no       | Only `{{title}}`, `{{items}}`, `{{type}}` | yes | |\n| `redact_confidential_resources` | boolean | Whether redact fields for confidential resources | no | no | no | true |\n\nThe following placeholders are supported for `summary`:\n\n- `title`: The title of the generated issue\n- `items`: Concatenated markdown separated by a newline for each `item`\n- `type`: The resource type for the summary. For now `issues`, `merge_requests`, or `epics`,\n\n\u003e **Note:**\n\u003e - Both `item` and `summary` fields act like a [comment action](#comment-action),\n\u003e   therefore [Ruby expression](#ruby-expression) is supported.\n\u003e - Placeholders work regularly for `item`, but for `summary` only `{{title}}`,\n\u003e   `{{items}}`, `{{type}}` are supported because it's not tied to a particular\n\u003e   resource like the comment action.\n\u003e - No issues will be created if:\n\u003e    - the specific policy doesn't yield any resources; or\n\u003e    - the source type is a group and `destination` is not set.\n\u003e - `redact_confidential_resources` defaults to `true`, so fields on\n\u003e confidential resources will be converted to `(confidential)` except for\n\u003e `{{web_url}}`. Setting it to `false` will reveal the confidential fields.\n\u003e This will be useful if the summary is confidential itself (not implemented\n\u003e yet), or if we're posting to another private project (not implemented yet).\n\nExample:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Issues require labels\n        limits:\n          most_recent: 15\n        actions:\n          summarize:\n            title: |\n              #{resource[:type].capitalize} require labels\n            item: |\n              - [ ] [{{title}}]({{web_url}}) {{labels}}\n            summary: |\n              The following {{type}} require labels:\n\n              {{items}}\n\n              Please take care of them before the end of #{7.days.from_now.strftime('%Y-%m-%d')}\n\n              /label ~\"needs attention\"\n```\n\nWhich could generate an issue like:\n\nTitle:\n\n```\nIssues require labels\n```\n\nDescription:\n\n```markdown\nThe following issues require labels:\n\n- [ ] [An example issue](http://example.com/group/project/issues/1) ~\"label A\", ~\"label B\"\n- [ ] [Another issue](http://example.com/group/project/issues/2) ~\"label B\", ~\"label C\"\n\nPlease take care of them before the end of 2000-01-01\n\n/label ~\"needs attention\"\n```\n\n##### Comment on summary action\n\nGenerates one comment for each resource, attaching these comments to the summary\ncreated by the [`summarize` action](#summarize-action).\n\nThe use case for this is wanting to create a summary with an overview, and then\na threaded discussion for each resource, with a header comment starting each\ndiscussion.\n\nAccepts a single string value: the template used to generate the comments. For\ndetails of the syntax of this template, see the [comment action](#comment-action).\n\nSince this action depends on the summary, it is invalid to supply a\n`comment_on_summary` action without an accompanying `summarize` sibling action.\nThe `summarize` action will always be completed first.\n\nJust like for [comment action](#comment-action), setting `comment_type` in the\n`actions` set controls whether the comment must be resolved for merge requests.\nSee: [`comment_type` action option](#comment-type-action-option).\n\nExample:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: List of issues to discuss\n        limits:\n          most_recent: 15\n        actions:\n          comment_type: thread\n          comment_on_summary: |\n            # {{title}}\n\n            author: {{author}}\n          summarize:\n            title: |\n              #{resource[:type].capitalize} require labels\n            item: |\n              - [ ] [{{title}}]({{web_url}}) {{labels}}\n            summary: |\n              The following {{type}} require labels:\n\n              {{items}}\n\n              Please take care of them before the end of #{7.days.from_now.strftime('%Y-%m-%d')}\n\n              /label ~\"needs attention\"\n```\n\n##### Create a new issue from each resource\n\nGenerates one issue for each resource, by default in the same project as the resource.\n\nThe use case for this is, for example, creating test issues in the same (or different)\nproject for issues labeled \"extended-testing\"; or automatically splitting one issue with a\ncertain label into multiple ones.\n\nAccepts a hash of fields.\n\n| Field         | Type   | Description                                     | Required | Placeholders | Ruby expression | Default        |\n| ----          | ----   | ----                                            | ----     | ----         | ----            | ----           |\n| `title`       | string | The title of the generated issue                | yes      | yes          | yes             |                |\n| `destination` | integer or string | The project ID or path to create the generated issue in | no   | no              | no             | source project |\n| `description`     | string | The description of the generated issue          | no       | yes | yes | |\n| `redact_confidential_resources` | boolean | Whether redact fields for confidential resources | no | no | no | true |\n\nThe placeholders available in `title` and `destination` are the properties of the resource being used to generate the issue.\n\nExample\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Issues requiring extra testing\n        labels:\n          - needs-testing\n        actions:\n          issue:\n            title: |\n              Testing: {{ title }}\n            description: |\n              The issue {{ full_reference }} needs testing.\n\n              Please take care of them before the end of #{7.days.from_now.strftime('%Y-%m-%d')}\n\n              /label ~\"needs attention\"\n```\n\n##### Delete action\n\n**This action is only applicable for branches.**\n\nDelete the resource.\n\nAccept a boolean. Set to `true` to enable.\n\nExample :\n```yaml\nresource_rules:\n  branches:\n    rules:\n      - name: My branch policy\n        conditions:\n          date:\n            attribute: committed_date\n            condition: older_than\n            interval_type: months\n            interval: 30\n        actions:\n          delete: true\n```\n\n### Summary policies\n\nSummary policies are special policies that join multiple rule policies together\nto create a summary issue with all the sub-policies' summaries.\nThey have the same structure as Rule policies that define `actions.summarize`.\n\nOne key difference is that the `{{items}}` placeholder represents the array of\nsub-policies' summary.\n\nNote that only the `summarize` keys in the sub-policies' `actions` is used. Any\nother keys (e.g. `mention`, `comment`, `labels` etc.) are ignored.\n\nYou can define such policy as follows:\n\n```yml\nresource_rules:\n  issues:\n    summaries:\n      - name: Newest and oldest issues summary\n        rules:\n          - name: New issues\n            conditions:\n              state: opened\n            limits:\n              most_recent: 2\n            actions:\n              summarize:\n                item: \"- [ ] [{{title}}]({{web_url}}) {{labels}}\"\n                summary: |\n                  Please triage the following new {{type}}:\n\n                  {{items}}\n          - name: Old issues\n            conditions:\n              state: opened\n            limits:\n              oldest: 2\n            actions:\n              summarize:\n                item: \"- [ ] [{{title}}]({{web_url}}) {{labels}}\"\n                summary: |\n                  Please triage the following old {{type}}:\n\n                  {{items}}\n        actions:\n          summarize:\n            title: \"Newest and oldest {{type}} summary\"\n            summary: |\n              Please triage the following {{type}}:\n\n              {{items}}\n\n              Please take care of them before the end of #{7.days.from_now.strftime('%Y-%m-%d')}\n\n              /label ~\"needs attention\"\n```\n\nWhich could generate an issue like:\n\nTitle:\n\n```\nNewest and oldest issues summary\n```\n\nDescription:\n\n```markdown\nPlease triage the following issues:\n\nPlease triage the following new issues:\n\n- [ ] [A new issue](http://example.com/group/project/issues/4)\n- [ ] [Another new issue](http://example.com/group/project/issues/3) ~\"label B\", ~\"label C\"\n\nPlease triage the following old issues:\n\n- [ ] [An old issue](http://example.com/group/project/issues/1) ~\"label A\", ~\"label B\"\n- [ ] [Another old issue](http://example.com/group/project/issues/2) ~\"label C\"\n\nPlease take care of them before the end of 2000-01-01\n\n/label ~\"needs attention\"\n```\n\n\u003e **Note:** If a specific policy doesn't yield any resources, it will not\n\u003e generate the corresponding description. If all policies yield no resources,\n\u003e then no issues will be created.\n\n### Ruby expression API\n\nHere's a list of currently available Ruby expression API:\n\n##### Methods for `Issue` and `MergeRequest` (the context)\n\n| Name                    | Return type     | Description |\n| ----                    | ----            | ----        |\n| resource                | Hash            | The hash containing the raw data of the resource. Note that `resource[:type]` is the type of the policy (`issues`, `merge_requests`, or `epics`), not the API `type` field. |\n| author                  | String          | The username of the resource author |\n| state                   | String          | The state of the resource |\n| milestone               | Milestone       | The milestone attached to the resource |\n| labels                  | [Label]         | A list of labels, having only names |\n| labels_with_details     | [Label]         | A list of labels which has more information loaded from another API request |\n| labels_chronologically  | [Label]         | Same as `labels_with_details` but sorted chronologically |\n| label_events            | [LabelEvent]    | A list of label events on the resource |\n| instance_version        | InstanceVersion | The version for the GitLab instance we're triaging with |\n| project_path            | String          | The path with namespace to the issues or merge requests project |\n| full_resource_reference | String          | A full reference including project path to the issue or merge request |\n\n##### Methods for `Issue` and `LinkedIssue` (issue context)\n\n| Name                   | Return type    | Description |\n| ----                   | ----           | ----        |\n| merge_requests_count   | Integer        | The number of merge requests related to the issue |\n| related_merge_requests | [MergeRequest] | The list of merge requests related to the issue |\n| closed_by              | [MergeRequest] | The list of merge requests that close the issue |\n| linked_issues          | [LinkedIssue]  | The list of issues that are linked to the issue |\n| due_date               | Date           | The due date of the issue. Could be `nil` |\n\n##### Methods for `LinkedIssue`\n\n| Method    | Return type | Description |\n| ----      | ----        | ----        |\n| link_type | String      | The link type of the linked issue (`blocks`, `is_blocked_by`, or `relates_to`) |\n\n##### Methods for `MergeRequest` (merge request context)\n\n| Method              | Return type | Description |\n| ----                | ----        | ----        |\n| 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. |\n| closes_issues       | [Issue]     | The list of issues that would be closed by merging the provided merge request |\n\n##### Methods for `Milestone`\n\n| Method      | Return type | Description |\n| ----        | ----        | ----        |\n| id          | Integer     | The id of the milestone |\n| iid         | Integer     | The iid of the milestone |\n| project_id  | Integer     | The project id of the milestone if available |\n| group_id    | Integer     | The group id of the milestone if available |\n| title       | String      | The title of the milestone |\n| description | String      | The description of the milestone |\n| state       | String      | The state of the milestone. Could be `active` or `closed` |\n| due_date    | Date        | The due date of the milestone. Could be `nil` |\n| start_date  | Date        | The start date of the milestone. Could be `nil` |\n| updated_at  | Time        | The updated timestamp of the milestone |\n| created_at  | Time        | The created timestamp of the milestone |\n| succ        | Milestone   | The next active milestone beside this milestone |\n| active?     | Boolean     | `true` if `state` is `active`; `false` otherwise |\n| closed?     | Boolean     | `true` if `state` is `closed`; `false` otherwise |\n| started?    | Boolean     | `true` if `start_date` exists and in the past; `false` otherwise |\n| expired?    | Boolean     | `true` if `due_date` exists and in the past; `false` otherwise |\n| in_progress?| Boolean     | `true` if `started?` and `!expired`; `false` otherwise |\n\n##### Methods for `Label`\n\n| Method      | Return type | Description |\n| ----        | ----        | ----        |\n| id          | Integer     | The id of the label |\n| project_id  | Integer     | The project id of the label if available |\n| group_id    | Integer     | The group id of the label if available |\n| name        | String      | The name of the label |\n| description | String      | The description of the label |\n| color       | String      | The color of the label in RGB |\n| priority    | Integer     | The priority of the label |\n| added_at    | Time        | When the label was added to the resource |\n\n##### Methods for `LabelEvent`\n\n| Method        | Return type | Description |\n| ----          | ----        | ----        |\n| id            | Integer     | The id of the label event |\n| resource_type | String      | The resource type of the event. Could be `Issue` or `MergeRequest` |\n| resource_id   | Integer     | The id of the resource |\n| action        | String      | The action of the event. Could be `add` or `remove` |\n| created_at    | Time        | When the event happened |\n\n##### Methods for `InstanceVersion`\n\n| Method        | Return type | Description |\n| ----          | ----        | ----        |\n| version       | String      | The full string of version. e.g. `11.3.0-rc11-ee` |\n| version_short | String      | The short string of version. e.g. `11.3` |\n| revision      | String      | The revision of GitLab. e.g. `231b0c7` |\n\n### Installation\n\n    gem install gitlab-triage\n\n### Usage\n\n    gitlab-triage --help\n\nWill show:\n\n```\nUsage: gitlab-triage [options]\n\n    -n, --dry-run                    Don't actually update anything, just print\n    -f, --policies-file [string]     A valid policies YML file\n        --all-projects               Process all projects the token has access to\n    -s, --source [type]              The source type between [ projects or groups ], default value: projects\n    -i, --source-id [string]         Source ID or path\n    -p, --project-id [string]        [Deprecated] A project ID or path, please use `--source-id`\n        --resource-reference [string]\n                                     Resource short-reference, e.g. #42, !33, or \u002699\n    -t, --token [string]             A valid API token\n    -H, --host-url [string]          A valid host url\n    -r, --require [string]           Require a file before performing\n    -d, --debug                      Print debug information\n    -h, --help                       Print help message\n    -v, --version                    Print version\n        --init                       Initialize the project with a policy file\n        --init-ci                    Initialize the project with a .gitlab-ci.yml file\n```\n\n#### Running with the installed gem\n\nTriaging against a specific project:\n\n```\ngitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org/triage\n```\n\nTriaging against a whole group:\n\n```\ngitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org --source groups\n```\n\nTriaging against an entire instance:\n\n```\ngitlab-triage --dry-run --token $GITLAB_API_TOKEN --all-projects\n```\n\n\u003e **Note:** The `--all-projects` option will process all resources for all projects visible to the specified `$GITLAB_API_TOKEN`\n\n#### Running from source\n\nExecute the `gitlab-triage` script from the `./bin` directory.\n\nFor example- after cloning this project, from the root `gitlab-triage` directory:\n\n```\nbundle exec bin/gitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org/triage\n```\n\nTriaging against specific resource:\n\n```\ngitlab-triage --dry-run --token $API_TOKEN --source-id gitlab-org/triage --resource-reference '#42'\ngitlab-triage --dry-run --token $API_TOKEN --source-id gitlab-org/triage --resource-reference '!33'\ngitlab-triage --dry-run --token $API_TOKEN --source groups --source-id gitlab-org --resource-reference '\u002699'\n```\n\n#### Running on GitLab CI pipeline\n\nYou can enforce policies using a scheduled pipeline:\n\n```yml\nrun:triage:triage:\n  stage: triage\n  script:\n    - gem install gitlab-triage\n    - gitlab-triage --token $GITLAB_API_TOKEN --source-id $CI_PROJECT_PATH\n  rules:\n    - if: $CI_PIPELINE_SOURCE == \"schedule\"\n```\n\n\u003e **Note:** You can use the [`--init-ci`](#usage) option to add an example [`.gitlab-ci.yml` file](support/.gitlab-ci.example.yml) to your project\n\n#### Can I use gitlab-triage for my self-hosted GitLab instance?\n\nYes, you can override the host url using the following options:\n\n##### CLI\n\n```\ngitlab-triage --dry-run --token $GITLAB_API_TOKEN --source-id gitlab-org/triage --host-url https://gitlab.host.com\n```\n\n##### Policy file\n\n```yml\nhost_url: https://gitlab.host.com\nresource_rules:\n```\n\n#### Can I customize?\n\nYou can take the advantage of command line option `-r` or `--require` to\nload a Ruby file before performing the actions. This allows you to do\nwhatever you want. For example, you can put this in a file like `my_plugin.rb`:\n\n```ruby\nmodule MyPlugin\n  def has_severity_label?\n    labels.grep(/^S\\d+$/).any?\n  end\n\n  def has_priority_label?\n    labels.grep(/^P\\d+$/).any?\n  end\n\n  def labels\n    resource[:labels]\n  end\nend\n\nGitlab::Triage::Resource::Context.include MyPlugin\n```\n\nAnd then run it with:\n\n```shell\ngitlab-triage -r ./my_plugin.rb --token $GITLAB_API_TOKEN --source-id gitlab-org/triage\n```\n\nThis allows you to use `has_severity_label?` in the Ruby condition:\n\n```yml\nresource_rules:\n  issues:\n    rules:\n      - name: Apply default severity or priority labels\n        conditions:\n          ruby: |\n            !has_severity_label? || !has_priority_label?\n        actions:\n          comment: |\n            #{'/label ~S3' unless has_severity_label?}\n            #{'/label ~P3' unless has_priority_label?}\n```\n\n### Contributing\n\nPlease refer to the [Contributing Guide](CONTRIBUTING.md).\n\n## Release Process\n\nWe release `gitlab-triage` on an ad-hoc basis. There is no regularity to when\nwe release, we just release when we make a change - no matter the size of the\nchange.\n\nTo release a new version:\n\n1. Create a Merge Request.\n1. Use Merge Request template [Release.md](https://gitlab.com/gitlab-org/ruby/gems/gitlab-triage/-/blob/master/.gitlab/merge_request_templates/Release.md).\n1. Follow the instructions.\n1. After the Merge Request has been merged, a new gem version is [published automatically](https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/master/ci/gem-release.yml)\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/gitlab.com%2Fgitlab-org%2Fruby%2Fgems%2Fgitlab-triage","html_url":"https://awesome.ecosyste.ms/projects/gitlab.com%2Fgitlab-org%2Fruby%2Fgems%2Fgitlab-triage","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/gitlab.com%2Fgitlab-org%2Fruby%2Fgems%2Fgitlab-triage/lists"}