Since the introduction of validation actions, as part of the process of publishing to HACS, any forks that merge in the changes in .github/workflows will pick up those actions to run in their own local fork. It is natural that the HACS Validation action fails, as the fork is NOT registered, but it can result in annoying notifications and unnecessary errors.
For example see: https://github.com/artmg/warmup/actions
Need to investigate the cleanest, simplest way for 'forkers' to silence these actions or notifications, without disrupting their OWN workflows.
Since the introduction of validation actions, as part of the process of publishing to HACS, any forks that merge in the changes in
.github/workflowswill pick up those actions to run in their own local fork. It is natural that the HACS Validation action fails, as the fork is NOT registered, but it can result in annoying notifications and unnecessary errors.For example see: https://github.com/artmg/warmup/actions
Need to investigate the cleanest, simplest way for 'forkers' to silence these actions or notifications, without disrupting their OWN workflows.