potiuk opened a new issue, #315: URL: https://github.com/apache/tooling-trusted-releases/issues/315
I copy pasted Airflows release checklist to the confifguration (markdown as expected) and the email sent contained just the markdown, not formatted content: <img width="831" height="459" alt="Image" src="https://github.com/user-attachments/assets/78380f75-ae86-4689-b5b8-a8a5f0d9772c"; /> That's quite suboptimal I'd say. I think also the release checklist will be generally in all cases faaaaar to long to be added the mail (ours is more than 400 lines - containing separate instructions for PMC / legal / Apache Way verification and instructions for contributors to tests the packages themselves). Maybe a better option will be - like we usually do in our emails - to simply ask users to paste link to the checklist? I imagine, if thisis a markdown then usually it is stored somewhere in GitHub and you can paste such link easily. For example in Airflow it is (in my recent PR where I updated it a bit) https://github.com/potiuk/airflow/blob/ce2b1a77778e51bfd8149ae01f1dea5a078f4fc0/dev/README_RELEASE_PROVIDERS.md#release-verification or possibly have a way to pastes several of those. Maybe it's fine to keep it as it is and allow markdown as it is but just suggest in the description that you should copy there **links** to the release verification checklist (this is what I am going to do actually). -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
