Work History

The record of every request and its lifecycle.

Work History is the running record of one documentation request from the first trigger to the final result. It gives you a live view of the request as it opens, as Doc Holiday works, and as the entry settles into a result. The request can begin in a git comment, a trigger event, the app, or the API, but it still lands in the same list. That makes Work History the place to check what Doc Holiday is doing right now, not only what already finished. The list shows the current stage beside each entry, so you can scan a Publication's activity. See Concepts.

Work History does not turn the request into a step list. It shows the stage that matters now, and the visible label always follows the request's current condition; the status reference below covers every label.

One Work History entry can include more than one pass. A new comment or reply can send Doc Holiday back to the same request with fresh context, and each new message can trigger another pass. Each pass can propose changes to one file or several files. That is why the detail view includes Details, Files, Messages, and Reasoning. Details brings together the trigger, timestamps, status, and result, so the entry reads as one continuous record instead of several disconnected events. Files shows the proposed file changes and file actions. Messages is where the requester responds when Doc Holiday asks for something, and it is the right place to answer whenever Needs Attention appears. Each pass stays attached to the same Work History entry.

The Work History page includes a Publication filter, a status filter (All Statuses shows every entry), and a summary search box that filters entries by their summary text. Use them to focus on one Publication, compare only active requests, or jump straight to entries that need a reply.

Organizations with no remaining Publications can still load the Work History rows. People who lack the required permission have no access to Work History.

If work completes without opening a pull request or merge request, the Work History entry remains staged for review or Needs Attention.

Status reference

App label	What it means	What moves it forward
Running	Doc Holiday is still working on the request.	More work completes, or the request moves to review.
Ready for Review	The draft is ready for a person to check.	A review, reply, or approval moves the request on.
Open	The request is active and collecting work before it reaches review.	New comments, replies, or updates keep the work moving.
Needs Attention	Doc Holiday asked for input and is waiting on a reply.	A response in Messages lets the next pass continue.
Merged	The changes reached the Publication's docs repository.	The merge completes and the result is recorded.
Closed	The request ended without a merge.	No further work moves it on.
Cancelled	The request stopped before completion.	A new request starts a fresh Work History entry.

For a fuller status reference, see Work History States. When an entry reaches Ready for Review, Review and Revise explains the next step.

---

Docs authored by Doc Holiday