lukaszlenart opened a new pull request, #1837: URL: https://github.com/apache/struts/pull/1837
Follow-up from the 6.11.0 vote drafting run. ## Problem Gmail's linkifier rewrites URLs server-side as the draft is stored. The four link lines in the 6.11.0 vote draft came out as: ``` * https://www.google.com/url?q=https://dist.apache.org/repos/dist/dev/struts/6.11.0/&source=gmail&ust=1786257641041000&sa=E ``` and the 72-column hard wrap was reflowed. The release manager had to hand-edit all four URLs. ## What was tested All three ways of passing the body through the Gmail tool are rewritten — there is no argument combination that avoids it: | Body passed as | Result | |---|---| | `body` only | Wrapped hrefs; plain rendering shows `bare-url <google.com/url?q=…>` | | `htmlBody` only | No plain-text part at all — HTML-only mail, wrong for an ASF list | | both | Worst: the plain part's *visible* text becomes the wrapped URL | `body` only — what the skill already produced — is the least-bad of the three. ## Change Since the mangling can't be prevented, the fix is made structural rather than left as advice: - The skill now produces the draft **and** a file containing the exact body, so the correction is one select-all-paste in the compose window instead of four hand-edited URLs. Pasting plain text restores both the bare URLs and the wrap. - Added to the `Draft it, do not send it` instruction, the pre-draft checklist, and the template's hard-wrap note, so it sits in the steps already being followed rather than only in prose. - Added a red flag for re-running the draft-update tool on a draft whose links were already fixed by hand — that re-mangles them. Docs/process only; no ticket, consistent with #1826, #1828 and #1836. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
