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

feat(ci): added yamllint check #17

Merged
merged 1 commit into from
Jun 8, 2020
Merged

feat(ci): added yamllint check #17

merged 1 commit into from
Jun 8, 2020

Conversation

serge1peshcoff
Copy link
Member

same way as in oms-docker

@codecov-commenter
Copy link

Codecov Report

Merging #17 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##            master       #17   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           42        42           
  Lines         1262      1262           
  Branches       186       186           
=========================================
  Hits          1262      1262           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1d434ea...c86e6cf. Read the comment docs.

@serge1peshcoff serge1peshcoff merged commit cd632b8 into master Jun 8, 2020
@serge1peshcoff serge1peshcoff deleted the add-yamllint branch June 8, 2020 13:20
serge1peshcoff pushed a commit that referenced this pull request Jun 8, 2020
# [1.21.0](1.20.1...1.21.0) (2020-06-08)

### Features

* **ci:** added yamllint check ([#17](#17)) ([cd632b8](cd632b8))
@serge1peshcoff
Copy link
Member Author

🎉 This PR is included in version 1.21.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants