Skip to content
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

Add ansible linter action #11

Merged
merged 4 commits into from
Jan 8, 2024
Merged

Add ansible linter action #11

merged 4 commits into from
Jan 8, 2024

Conversation

LuisDuarte1
Copy link
Member

No description provided.

@LuisDuarte1 LuisDuarte1 force-pushed the ansible-linter branch 3 times, most recently from b08d398 to 264d483 Compare January 4, 2024 10:31
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

test-playbook.yaml Fixed Show fixed Hide fixed
for ansible-lint since it doesn't support glob or regex
.ansible-lint Outdated Show resolved Hide resolved
.ansible-lint Fixed Show fixed Hide fixed
.ansible-lint Fixed Show fixed Hide fixed
Co-authored-by: Nuno Pereira <nunoafonso2002@gmail.com>
@LuisDuarte1 LuisDuarte1 merged commit 95a4371 into main Jan 8, 2024
3 checks passed
@LuisDuarte1 LuisDuarte1 deleted the ansible-linter branch April 8, 2024 17:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants