activate ack/push shared workflows on all devtools repositories
ssbarnea opened this issue · comments
As ack workflows already proved to be working correctly, we can now adopt it to all out devtools repositories, so we will ensure all pull-requests have correct labels configured.
- ansible-compat
- ansible-language-server
- ansible-lint
- ansible-navigator
- molecule
- molecule-containers
- molecule-docker
- molecule-podman
- vscode-ansible
As part of enablement we can safely remove the labels.yml workflow from those repos as that is now covered by it.
I think we need a better explanation of what is push and what is ack. Because I don't know off the top of my head and others would probably be confused by these references too.
Yep. In fact I was aware that they are were not documented yet but I decided to delay documenting them because we did not know exactly what we will effectively run on each of them.
That is why I named push based on when is triggered and not on what it does. Basically it acts as a post-merge which currently refreshes the draft release notes. Still, we may want to add other (optional?) features in the future, like publishing a nightly artifact or slack notifications.
Naming ack was harder because it is triggered on any change made to a pull request (not only a new change, like its title, body or labels are updated.
Be sure that I will not close this ticket until I add a documentation about their purposes.