github-workflow job is too aggresive #72
Description
While we know that gerrit would not be able to merge canges made to .github/workflows folders their existence should not be a reason block a job that does not touch these files.
With molecule projects we have important github specific integrations what are using workflows and migrating them could prove a real challend, still these integrations are not related to project code itself.
Example:
- https://github.com/pycontribs/pytest-molecule/blob/master/.github/workflows/release-drafter.yml which updates github release notes based on github data
- https://github.com/pycontribs/pytest-molecule/blob/master/.github/workflows/labels.yml which configures labels used
At least for start this job should fail only if current change is touching these files instead of failing if these files exist.
While we can live without the label automator, the release-note updater became a critical part of the development process as it removed the need to update https://github.com/pycontribs/pytest-molecule/releases ourselves (or to include these notes in CR)