From: Felix Lechner via Bug-mumi via "Bug reports for GNU Guix Mumi." <bug-mumi@gnu.org>
To: 70903@debbugs.gnu.org
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: bug#70903: [PATCH] Reverse colors for open and done; open is now red, and done is green.
Date: Sun, 12 May 2024 21:17:36 -0700 [thread overview]
Message-ID: <20240513041736.4499-1-felix.lechner@lease-up.com> (raw)
The previous color scheme was not consistent with the idea that red
signifies the need for corrective action, while green stands for all
clear.
This inconsistency was especially apparent when red CI badges appear
next to a red item that said "done."
---
assets/css/screen.css | 4 ++--
assets/mumi.scss | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/assets/css/screen.css b/assets/css/screen.css
index e4dcc10..4ef5a28 100644
--- a/assets/css/screen.css
+++ b/assets/css/screen.css
@@ -447,10 +447,10 @@ div.line pre {
}
.status-tag.done {
- background: #cb2431;
+ background: #2cbe4e;
}
.status-tag.open {
- background: #2cbe4e;
+ background: #cb2431;
}
.error.parse {
diff --git a/assets/mumi.scss b/assets/mumi.scss
index e605630..571a811 100644
--- a/assets/mumi.scss
+++ b/assets/mumi.scss
@@ -650,10 +650,10 @@ div.line pre {
}
.status-tag.done {
- background: #cb2431;
+ background: #2cbe4e;
}
.status-tag.open {
- background: #2cbe4e;
+ background: #cb2431;
}
.error.parse {
base-commit: 99416ed5c7d950eaf54d52023a2efd975bccac92
--
2.41.0
next reply other threads:[~2024-05-13 4:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 4:17 Felix Lechner via Bug-mumi via Bug reports for GNU Guix Mumi. [this message]
2024-05-13 4:45 ` bug#70903: Preview available Felix Lechner via Bug-mumi via Bug reports for GNU Guix Mumi.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://issues.guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240513041736.4499-1-felix.lechner@lease-up.com \
--to=bug-mumi@gnu.org \
--cc=70903@debbugs.gnu.org \
--cc=felix.lechner@lease-up.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).