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

Remove tag info from playbook summary #3061

Merged

Conversation

lgalis
Copy link
Contributor

@lgalis lgalis commented Dec 14, 2017

Remove tag info from playbook summary

Links

https://bugzilla.redhat.com/show_bug.cgi?id=1525127

screenshot from 2017-12-14 09-21-51

@lgalis
Copy link
Contributor Author

lgalis commented Dec 14, 2017

@miq-bot add_label bug, gaprindashvili/yes

@lgalis lgalis force-pushed the remove_tag_info_from_playbook_summary branch from 6f5e91b to a1147db Compare December 14, 2017 21:16
@miq-bot
Copy link
Member

miq-bot commented Dec 14, 2017

Checked commits lgalis/manageiq-ui-classic@1ec7ec8~...a1147db with ruby 2.3.3, rubocop 0.47.1, haml-lint 0.20.0, and yamllint 1.10.0
2 files checked, 0 offenses detected
Everything looks fine. 🍰

@mzazrivec mzazrivec added this to the Sprint 76 Ending Jan 1, 2018 milestone Dec 18, 2017
@mzazrivec mzazrivec self-assigned this Dec 18, 2017
@mzazrivec mzazrivec merged commit 85aceb6 into ManageIQ:master Dec 18, 2017
simaishi pushed a commit that referenced this pull request Dec 18, 2017
@simaishi
Copy link
Contributor

Gaprindashvili backport details:

$ git log -1
commit 2704b64459ccfc6537860ed4c396a044850a1ddd
Author: Milan Zázrivec <mzazrivec@redhat.com>
Date:   Mon Dec 18 12:43:39 2017 +0100

    Merge pull request #3061 from lgalis/remove_tag_info_from_playbook_summary
    
    Remove tag info from playbook summary
    (cherry picked from commit 85aceb6188e16638c96b8b90e5b13830d6a21040)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1527108

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

Successfully merging this pull request may close these issues.

4 participants