---
title: "Comment by krystalemily82 on \"GitHub Actions I Set Up on Every Project\" | Hashnode"
description: "The reusable workflows section is a great addition. One thing I’ve found useful is treating the workflow interface almost like an API: keep inputs and outputs e"
url: "https://hashnode.com/posts/github-actions-i-set-up-on-every-project/6ab0a2db5130721a4750d43a/comment/6ab312418a8d2afe41db0b2f"
---

[Discussion](https://hashnode.com/posts/github-actions-i-set-up-on-every-project/6ab0a2db5130721a4750d43a)

Comment [GitHub Actions I Set Up on Every Project](https://hashnode.com/posts/github-actions-i-set-up-on-every-project/6ab0a2db5130721a4750d43a)

[krystalemily82](https://hashnode.com/@krystal12)

[Sep 22](https://hashnode.com/posts/github-actions-i-set-up-on-every-project/6ab0a2db5130721a4750d43a/comment/6ab312418a8d2afe41db0b2f)

The reusable workflows section is a great addition. One thing I’ve found useful is treating the workflow interface almost like an API: keep inputs and outputs explicit, document the expected permissions, and avoid making the reusable workflow depend on repository-specific assumptions. That makes it much easier to reuse the same workflow across projects without creating hidden coupling. The combination of reusable workflows, caching, and concurrency can make a surprisingly big difference as a project grows.

[Madhav Bhasin](https://hashnode.com/@madhavbhasin)

[Oct 7](https://hashnode.com/posts/github-actions-i-set-up-on-every-project/6ab0a2db5130721a4750d43a/comment/6ab312418a8d2afe41db0b2f#reply-6ac624b550c9f923d1942c91)

"Treat the workflow interface like an API" is the right mental model and the post doesn't say it that clearly. Explicit inputs and outputs, documented permissions, no repository-specific assumptions baked in — those are the constraints that make a reusable workflow actually reusable rather than just shared. The hidden coupling problem is real and usually shows up the second time you try to use the workflow somewhere new.
