GitLab project triage digest
Use “GitLab project triage digest” in Recued. It provides a scheduled, read-only digest for one provider record project.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (25 steps)
project_id
trim
Trim whitespace from setting project id
viewer
?
project
?
issues_raw
?
merge_requests_raw
?
pipelines_raw
?
releases_raw
?
defaults
defaults
Apply defaults
issue_rows
slice
Take a subset of
merge_request_rows
slice
Take a subset of
pipeline_rows
slice
Take a subset of
issue_count
count
Count items in issues
merge_request_count
count
Count items in merge requests
pipeline_count
count
Count items in pipelines
release_count
count
Count items in releases
has_issues
compare
Check if issue count is greater than 0
has_merge_requests
compare
Check if merge request count is greater than 0
has_items
any
Check if any of the conditions are true
notify_enabled
compare
Check if setting notify when items equals true
should_notify
all
Check if all conditions are true
notify
?
skip: step.should_notify not_equal true
issue_table
to_table
Format results as a data table
merge_request_table
to_table
Format results as a data table
pipeline_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
gitlab
setting
=
channels
setting
=
in_app
end hour
setting
=
10
weekdays
setting
=
1,2,3,4,5
row limit
setting
=
25
project id
setting
=
start hour
setting
=
8
issue labels
setting
=
updated after
setting
=
notify when items
setting
=
true
merge request labels
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.