wait-action VS balena-push

I host my blog on Vercel, which is pre-rendered into static HTML via a webhook in Contentful — each time I publish a new post. To ensure that the blog and RSS feed finish building before the blog post list is generated, I am using jakejarvis/wait-action to wait for an arbitrary length of five minutes. This is a completely optional step for you. It might seem a bit hacky — but if it works, it works!

Balena push is an open-source package that was born out of both need and opportunity with the introduction of Github Actions. At the time, I was using the IoT platform Balena.io to manage a fleet of Digital Signage (TVs with Raspberry Pis) within my company's office. The Github action enables you to continuously deliver your project to Balena by pushing changes to the platform.

Not only can you provide a template for issues, but you can provide a contextual template based on the type of issue filed. So far for my projects, I've kept this configuration relatively simple with Two types of issues: Bug and Feature Request. The Bug template asks evidence-gathering questions to help troubleshoot issues, while the Feature Request template will have questions related to scoping a User Story.