Skip to main content
Video tutorial · 1:28

My work

My work is one person's view of change: the merge requests they wrote that are stuck on something they can fix, the change approvals that wait for their decision, their open merge requests, and what they merged recently. Merge requests you authored or are expected to approve.

Opening it​

My work in the side menu, under Dashboard. Every role has it. It shows the signed-in person's work in their company; platform admins see their work in the company selected in the header (without a selected company and without a company of their own, the page cannot load).

Whose merge requests are yours​

A merge request is yours when you are its author on the VCS:

  • with VCS accounts linked to your Merge Pilot account (My profile → Linked VCS accounts), the merge requests written by those accounts, each on its own VCS connection (a username is only unique on its own VCS);
  • with none linked, the merge requests whose author has the same name as your Merge Pilot user name.

A change approval is waiting for you when it is open and its assignee is you under any of the names a change approval may name you by: your Merge Pilot user name, your email, your tracker account, or the username of one of your linked VCS accounts (as written, or in lower case). Which name the company's change approvals use is set on the company's People tab (see People).

Figures​

Figure (label in the UI)Counts
Need your actionThe items of Needs your action
Open, yoursThe items of In progress
Recently merged or closedThe items of Recently completed: your merge requests merged or closed without merging in the last 14 days

The figures count what the sections list, so they stop at the sections' limits (below).

Needs your action​

Two kinds of items, your own merge requests first:

Your open merge requests that something holds. Merge Pilot looks at your 200 most recently updated open merge requests, leaving out those of watched repositories, and lists those with at least one of the reasons below, at most 50.

Reason (label in the UI)When
Secrets foundThe secret scan is done and found at least one possible secret
SCA blockedThe enforced dependency scan failed
License check failedThe enforced license check failed
Package health failedThe enforced package health check failed
Dependency sources failedThe enforced dependency sources check failed
Container image scan failedThe enforced container image scan failed
Infrastructure check failedThe enforced infrastructure check failed
CI configuration check failedThe enforced CI configuration check failed
Unsigned commitsThe enforced signed commit check failed
CI failedThe enforced CI check failed
Code review neededThe enforced code review check failed
Work items missingThe enforced work item check failed
Risk holdThe risk check holds the merge request
Held by a change freezeA change freeze holds the merge
Change approval rejectedThe merge request's change approval was rejected

A check counts only when its policy enforces it (it blocks the merge) and it failed; a check that only warns, or is still running, is not a reason.

Change approvals waiting for your decision. Open merge requests of other people whose change approval is open and assigned to you, at most 50, most recently updated first. Their reason is Waiting for your approval. Your own merge requests are never listed here.

Each item shows its main reason as a badge (the most serious, in the order of the table, with Waiting for your approval last), +N when there are more (point at the badge to see them all), the merge request's number and title (a link to its page), its source and target branches, its author and when it was created. An icon that opens it on GitLab or GitHub appears when you point at the item.

Without any item: Nothing needs your action right now.

In progress​

Your open merge requests, at most 50, most recently updated first, with their state, branches, author and when they were last updated. Without any: No open merge requests.

Recently completed​

Your merge requests merged or closed without merging in the last 14 days, at most 20, the most recently merged or closed first, with when they merged or closed. Without any: No recently completed merge requests.

See all​

When a section has more than it shows, See all opens the merge request list: filtered to Needs attention for Needs your action, to open merge requests for In progress, and unfiltered for Recently completed (it holds merged and closed ones). The list holds every merge request of the company, not only yours: use its search to narrow it (see Merge requests).

Refreshing​

The page is read when it opens, every minute while the browser tab is visible, and with Refresh. The server keeps a person's page for up to 12 seconds. When it cannot be read, the page says Your work could not be loaded with a retry button.

Watched repositories​

Merge requests of watched repositories are yours like any other: they are listed under In progress and Recently completed. They are never under Needs your action: their checks are recorded as change management would decide them, but nothing holds their merge.

API​

GET /api/v1/my-work. Platform admins send the company as company_id (or the X-Company-ID header); without one and without a company of their own they get 400 (select a company).

The answer holds:

  • needs_attention: items[] (merge requests with reasons[] and primary_reason) and has_more;
  • in_progress and recently_completed: items[] (merge requests) and has_more;
  • summary: attention_count, in_progress_count, completed_count.

The reasons are secrets_found, sca_blocked, licenses_blocked, package_health_blocked, sources_blocked, images_blocked, iac_blocked, workflows_blocked, signatures_blocked, ci_failed, code_review_blocked, work_items_blocked, risk_blocked, freeze_held, change_approval_rejected and approval_requested.

has_more of needs_attention is also set when 200 open merge requests were looked at, as there may be more beyond them.

Reading the page is not recorded in the audit log.

  • Dashboard: Needs attention for the whole company.
  • Voting: deciding a change approval in Merge Pilot.
  • People: how a person is recognised in the VCS and the tracker.
  • Roles and users: linking VCS accounts on My profile.

Video tutorial

Short videos of this feature working on real GitLab and Jira projects. English audio, English and Turkish subtitles. All video tutorials →