docs: describe worklog posting on Jira, Linear, and GitHub#4
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: describe worklog posting on Jira, Linear, and GitHub#4mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Document the new multi-provider worklog posting flow so users understand what "posting a worklog" means on each supported issue tracker and how to set up the required credentials.
Changes
⏱ Worklogcomment on the matched issue (Linear viacommentCreate, GitHub via the issue-comments REST endpoint). Added provider-specific "What posting a worklog means" sections showing the comment format, the machine marker, and where the entry shows up in each UI.repo, fine-grained tokens need Issues: Read and write (read-only is no longer sufficient because the daemon now writes comments after approval). Clarified thatGITHUB_ORGaccepts an org slug or a personal username.Authorizationheader (noBearerprefix) and thatLINEAR_TEAM_IDSaccepts team keys likeENG,DESIGN.Context
Source PR: Meridiona/meridian#102 — feat(worklog): Linear & GitHub worklog providers alongside Jira. Worklog posting now branches on a per-row provider snapshot taken at draft time, so the same approval gate and idempotency guarantees apply across Jira, Linear, and GitHub.