Use “GitLab merge request review brief” in Recued. It provides a read-only review brief for one provider record merge request.

How it works 19 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (19 steps)

■ project_id trim

Trim whitespace from setting project id

■ merge_request_iid trim

Trim whitespace from setting merge request iid

■ project ?

■ merge_request ?

■ notes_raw ?

■ commits_raw ?

■ pipelines_raw ?

skip: config.include_pipelines not_equal true

■ defaults defaults

Apply defaults

■ note_rows slice

Take a subset of

■ commit_rows slice

Take a subset of

■ pipeline_rows slice

Take a subset of

■ note_count count

Count items in notes

■ commit_count count

Count items in commits

■ pipeline_count count

Count items in pipelines

■ summarize ?

■ note_table to_table

Format results as a data table

■ commit_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 7 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize merge request scope, reviewer and assignee state, discussion-note themes, source-branch commit activity, pipeline status, merge risks, and concrete next actions. Do not invent facts outside the GitLab records.

gitlab setting =

row limit setting = 25

max length setting = 900

project id setting =

include pipelines setting = true

merge request iid setting =