---
title: "Comment by Mathieu Lemaire on \"How To Use GitHub Actions for Deployments When Following Trunk-Based Development\" | Hashnode"
description: "Hello there - thank you very much for the detailed steps 💯. Applied this on my repo (the manual steps with draft releases) but now I am facing a purist issue:"
url: "https://hashnode.com/posts/github-actions-trunk-based-development/639969d1eddf26a61b5cba36/comment/659ea2c231706e5871c3842a"
---

[Discussion](https://hashnode.com/posts/github-actions-trunk-based-development/639969d1eddf26a61b5cba36)

Comment [How To Use GitHub Actions for Deployments When Following Trunk-Based Development](https://hashnode.com/posts/github-actions-trunk-based-development/639969d1eddf26a61b5cba36)

[Mathieu Lemaire](https://hashnode.com/@maz514)

[Jan 10, 2024](https://hashnode.com/posts/github-actions-trunk-based-development/639969d1eddf26a61b5cba36/comment/659ea2c231706e5871c3842a)

Hello there - thank you very much for the detailed steps 💯. Applied this on my repo (the manual steps with draft releases) but now I am facing a purist issue: how do you deal with draft releases that never get published?

[Jannik Wempe](https://hashnode.com/@JannikWempe)

[Jan 10, 2024](https://hashnode.com/posts/github-actions-trunk-based-development/639969d1eddf26a61b5cba36/comment/659ea2c231706e5871c3842a#reply-659ea357eae515b2608f56c1)

Hey, happy that it was helpful.

I don't care and let them sit there, to be honest. I imagine you could create another action running on a CRON that cleans them up. But the cost-benefit-ratio isn't there for me.