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.
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
Upgrade base image to Python 3.12 #14
Upgrade base image to Python 3.12 #14
Changes from all commits
aa10a5b
6dc95bf
b2ad5d2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 21 in Dockerfile
GitHub Actions / build (ansible-core)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 21 in Dockerfile
GitHub Actions / build (ansible-core, 2.16)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 21 in Dockerfile
GitHub Actions / build (ansible-core, 2.17)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 21 in Dockerfile
GitHub Actions / build (ansible)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 21 in Dockerfile
GitHub Actions / build (ansible, 9)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 21 in Dockerfile
GitHub Actions / build (ansible, 10)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 32 in Dockerfile
GitHub Actions / build (ansible-core)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 32 in Dockerfile
GitHub Actions / build (ansible-core, 2.16)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 32 in Dockerfile
GitHub Actions / build (ansible-core, 2.17)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 32 in Dockerfile
GitHub Actions / build (ansible)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 32 in Dockerfile
GitHub Actions / build (ansible, 9)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 32 in Dockerfile
GitHub Actions / build (ansible, 10)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 42 in Dockerfile
GitHub Actions / build (ansible-core)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 42 in Dockerfile
GitHub Actions / build (ansible-core, 2.16)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 42 in Dockerfile
GitHub Actions / build (ansible-core, 2.17)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 42 in Dockerfile
GitHub Actions / build (ansible)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 42 in Dockerfile
GitHub Actions / build (ansible, 9)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 42 in Dockerfile
GitHub Actions / build (ansible, 10)
The 'as' keyword should match the case of the 'from' keyword
Check warning on line 45 in Dockerfile
GitHub Actions / build (ansible-core)
Legacy key/value format with whitespace separator should not be used
Check warning on line 45 in Dockerfile
GitHub Actions / build (ansible-core, 2.16)
Legacy key/value format with whitespace separator should not be used
Check warning on line 45 in Dockerfile
GitHub Actions / build (ansible-core, 2.17)
Legacy key/value format with whitespace separator should not be used
Check warning on line 45 in Dockerfile
GitHub Actions / build (ansible)
Legacy key/value format with whitespace separator should not be used
Check warning on line 45 in Dockerfile
GitHub Actions / build (ansible, 9)
Legacy key/value format with whitespace separator should not be used
Check warning on line 45 in Dockerfile
GitHub Actions / build (ansible, 10)
Legacy key/value format with whitespace separator should not be used