# WorkLog

Promote a robust, continuous delivery workflow by ensuring the active participation of every engineer in the development process.&#x20;

Legends are as follows -&#x20;

<div align="left"><figure><img src="/files/6ani2Y5t7taRwddIqPEn" alt=""><figcaption></figcaption></figure></div>

### **View by Author**

Get a complete overview of your team's Git activity at a glance. Hover over any activity dot for quick details, and click on a Pull Request (PR) dot to open a full summary drawer.

<figure><img src="/files/PhEsK96bNJFtf8x8r64y" alt=""><figcaption></figcaption></figure>

### **View by Issues**

Instantly see the development progress on your issues through linked PR activities. Hover over any dot for a quick summary, and click on a Pull Request (PR) to open its detailed drawer

<figure><img src="/files/oFY5nhXOMoSa2yLCScqm" alt=""><figcaption></figcaption></figure>

### **View by Repository**

Focus on what matters by tracking daily changes for any selected repository. Get a complete, centralized view of all development activities in one place.

<figure><img src="/files/dQ7z2tgzvj4eAUvJgZLg" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://typo.gitbook.io/typo-help-docs/platform/worklog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
