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

Theme alert-* css classes and add alert-success #4842

Merged
merged 6 commits into from
Jul 18, 2020

Conversation

timja
Copy link
Member

@timja timja commented Jul 10, 2020

image

Proposed changelog entries

  • Entry 1: JENKINS-62747: Add alert-success banner
  • Entry 2: Developer: Add theming support for alert-* classes
  • ...

Proposed upgrade guidelines

N/A

Submitter checklist

  • (If applicable) Jira issue is well described
  • Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
    • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
  • Appropriate autotests or explanation to why this change has no tests
  • For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

  • There are at least 2 approvals for the pull request and no outstanding requests for change
  • Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
  • Changelog entries in the PR title and/or Proposed changelog entries are correct
  • Proper changelog labels are set so that the changelog can be generated automatically
  • If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
  • If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

@timja timja requested review from fqueiruga and a team July 10, 2020 19:31
@timja timja added web-ui The PR includes WebUI changes which may need special expertise rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted developer Changes which impact plugin developers labels Jul 10, 2020
@oleg-nenashev oleg-nenashev self-requested a review July 10, 2020 19:32
Copy link
Contributor

@fqueiruga fqueiruga left a comment

Choose a reason for hiding this comment

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

Approving without testing. Looks right.
Can this be the time to add a .alert-success class? We're missing that one.

Comment on lines 92 to 101
--notification-warn-icon-color: #ff9800;
--notification-warn-bg-color: #fff3cd;
--notification-warn-border-color: #ffeeba;
--notification-warn-color: #856404;

// Error
--alert-err-icon-color: #f44336;
--alert-err-bg-color: #f8d7da;
--alert-err-border-color: #f5c6cb;
--alert-err-color: #721c24;
--notification-err-icon-color: #f44336;
--notification-err-bg-color: #f8d7da;
--notification-err-border-color: #f5c6cb;
--notification-err-color: #721c24;
Copy link
Contributor

Choose a reason for hiding this comment

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

Nitpicking but shouldn't we use the same naming scheme as on the other ones? Either warn & err or warning & danger.

Copy link
Member Author

@timja timja Jul 10, 2020

Choose a reason for hiding this comment

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

I'll adjust these ones, (but they were already inconsistent)

Copy link
Contributor

Choose a reason for hiding this comment

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

Whatever you consider best!

@timja timja changed the title Theme alert-* css classes Theme alert-* css classes and add alert-success Jul 10, 2020
Copy link
Member

@oleg-nenashev oleg-nenashev left a comment

Choose a reason for hiding this comment

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

I do not see anything wrong in this pull request. Less colors makes total sense. +1 for merging

@oleg-nenashev
Copy link
Member

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

@oleg-nenashev oleg-nenashev added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Jul 17, 2020
@timja timja merged commit 29ff7c1 into jenkinsci:master Jul 18, 2020
@timja timja deleted the theme-alerts branch July 18, 2020 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer Changes which impact plugin developers ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted web-ui The PR includes WebUI changes which may need special expertise
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants