You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 20, 2024. It is now read-only.
in bot help page the following can be read for merge conditions on community maintained modules:
If you are maintainer of the module or maintainer of a module in the same namespace, only one shipit is required.
It seems that the behavior is not applied on callback plugins.
Here are 2 PR where I am maintainer of the callback, and my shipit comment was not enough to trigger the bot shipit labeling: ansible/ansible#57629 ansible/ansible#57575
I had to ask for help on IRC.
Is there a reason for not applying the same merge conditions on callbacks ?
The text was updated successfully, but these errors were encountered:
Hi,
in bot help page the following can be read for merge conditions on community maintained modules:
It seems that the behavior is not applied on callback plugins.
Here are 2 PR where I am maintainer of the callback, and my
shipit
comment was not enough to trigger the botshipit
labeling:ansible/ansible#57629
ansible/ansible#57575
I had to ask for help on IRC.
Is there a reason for not applying the same merge conditions on callbacks ?
The text was updated successfully, but these errors were encountered: