GitHub Actions' `required` properties aren't always required

The blog post discusses a quirk in GitHub Actions where the 'required' property does not enforce that inputs are non-empty, leading to deployment issues. It illustrates this with an example of a composite action setup, highlights an experience with failing builds due to empty input, and suggests using actionlint for future checks.