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
Describe the bug
The README.md mentions a 'legacy' branch. There's no such branch currently on this repo.
Expected behavior
Either the mention of the 'legacy' branch be removed from the README.md, or the legacy branch be added to this repo for folks not yet using Collections.
Actual behavior
less README.md
User cries when checking branch list.
OS / Environment
The environment turns very sad for everyone when they see this discrepancy in the README.md. ;)
Additional context
Thank you for all the work on this code! :) I would love to see non-Collections support, but I do understand that this is where Ansible core development is moving, for better or worse. Cheers.
The text was updated successfully, but these errors were encountered:
I am very sorry we made you sad. After taking a look into our code I think we should be linking to an old tag in our Repo and not to a specific branch. Would this make you happy, or is your happiness entirely dependent on a special branch in this Repo? ;)
Describe the bug
The README.md mentions a 'legacy' branch. There's no such branch currently on this repo.
Expected behavior
Either the mention of the 'legacy' branch be removed from the README.md, or the legacy branch be added to this repo for folks not yet using Collections.
Actual behavior
less README.md
User cries when checking branch list.
OS / Environment
The environment turns very sad for everyone when they see this discrepancy in the README.md. ;)
Additional context
Thank you for all the work on this code! :) I would love to see non-Collections support, but I do understand that this is where Ansible core development is moving, for better or worse. Cheers.
The text was updated successfully, but these errors were encountered: