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

Improving Ansible score #236

Merged
merged 4 commits into from
Dec 23, 2019
Merged

Improving Ansible score #236

merged 4 commits into from
Dec 23, 2019

Conversation

kbogtob
Copy link
Contributor

@kbogtob kbogtob commented Dec 9, 2019

What does this PR do?

Improving the project score on Ansible-galaxy by following best practises here and there.

Motivation

We are loosing a lot of points because of linting errors. This impacts the company's image thus this effort to improve the notation. There's also metadata errors that we will fix at a later time.

Copy link
Contributor

@KSerrania KSerrania left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

Could you rebase master and fix a new warning that got added in ansible-galaxy with the recent merges (YAML_ERROR: too many blank lines (1 > 0) (empty-lines))? I think that's because of the extra blank line that got added to tasks/main.yml, as ansible-galaxy doesn't allow extra blank lines in the main file.

@kbogtob
Copy link
Contributor Author

kbogtob commented Dec 23, 2019

Sure! I'll do that.

@kbogtob kbogtob force-pushed the kbogtob/improve-ansible-score branch from b8cb242 to 5964896 Compare December 23, 2019 13:21
@kbogtob kbogtob merged commit e81d5c9 into master Dec 23, 2019
@kbogtob kbogtob deleted the kbogtob/improve-ansible-score branch December 23, 2019 13:47
KSerrania pushed a commit that referenced this pull request Dec 23, 2019
Improving Ansible score by removing bad practises
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