CLDR-15176 ansible-lint: workaround for version problem #1683
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@btangmu does fix it. The vagant issue is another issue which i deal with in the staging PR. |
- ansible-lint issue ansible/ansible-lint#1795 - vagrant pin macos version per actions/runner-images#4060
srl295
force-pushed
the
cldr-15176/ansible-lint-fix
branch
from
524c28e
to
9ef01fc
Compare
|
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
|
I pulled in the vagrant fix here too (noted in commit msg) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix the ansible-lint job which was failing due to two (2) issues:
ansible-lint issue: ansible/ansible-lint#1795
vagrant issue: pin macos per actions/runner-images#4060
CLDR-15176