yeah, you are right. > for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be o

yeah, you are right. > for example, don't use Actions as a content delivery network or as part of a serverless application, but a low benefit Action could be ok if it’s also low burden Just as the wesql article states, Use Cases is Not Recommended For: - Long-term database hosting or production workloads. - Maintaining an always-on public database endpoint. - Circumventing GitHub Actions usage policies.