-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update ansible-lint GHA #707
Conversation
There seems to be a bug in older versions of ansible-lint where pinning to a version for the GHA still installs the main branch.
Build succeeded. ✔️ ansible-galaxy-importer SUCCESS in 4m 11s |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 4m 35s |
Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry. |
regate |
Build succeeded (gate pipeline). ✔️ ansible-galaxy-importer SUCCESS in 4m 38s |
Pull request merge failed: Resource not accessible by integration, You may need to manually rebase your PR and retry. |
Backport to stable-3: 💚 backport PR created✅ Backport PR branch: Backported as #708 🤖 @patchback |
Update ansible-lint GHA (cherry picked from commit 874fbfe)
Backport to stable-2: 💔 cherry-picking failed — target branch does not exist❌ Failed to find branch stable-2 🤖 @patchback |
[PR #707/874fbfed backport][stable-3] Update ansible-lint GHA This is a backport of PR #707 as merged into main (874fbfe). SUMMARY There seems to be a bug in older versions of ansible-lint where pinning to a version for the GHA still installs the main branch. See ansible/ansible-lint#3762 for more info. ISSUE TYPE Bugfix Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mike Graves <[email protected]>
SUMMARY
There seems to be a bug in older versions of ansible-lint where pinning to a version for the GHA still installs the main branch.
See ansible/ansible-lint#3762 for more info.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION