You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some Slack update messages from GitHub employ a red highlight colour which indicates a problem (eg. tests have failed), and others use the same (or similar) red highlight colour to indicate deletion (eg. a branch deletion). Because of the colour coding, both appear negative - but one is an intentional part of the development process and occurs regularly.
Branch deletion
Workflow failure
Describe the solution you'd like
The ideal (for my needs) would be a more neutral colour for branch deletions and closure of pull requests - but I appreciate these are just the opinions of 1 developer. Please consider reviewing the colours associated with these messages to help distinguish the error indicators from more neutral messages, or consider some finer configuration control of message styles and associated colours.
Describe alternatives you've considered
Options I've considered:
Review the style / colours with a view to selecting a more neutral colour for non-error messages (described above)
Allow more fine-grained configuration of message colours and styles (described above)
Ignore it - this is also acceptable, it's just a styling suggestion after all
Additional context
This is particularly relevant in cases where we would like to grant visibility of our development processes to less technical members of staff, who may interpret a number of our messages as errors.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some Slack update messages from GitHub employ a red highlight colour which indicates a problem (eg. tests have failed), and others use the same (or similar) red highlight colour to indicate deletion (eg. a branch deletion). Because of the colour coding, both appear negative - but one is an intentional part of the development process and occurs regularly.
Describe the solution you'd like
The ideal (for my needs) would be a more neutral colour for branch deletions and closure of pull requests - but I appreciate these are just the opinions of 1 developer. Please consider reviewing the colours associated with these messages to help distinguish the error indicators from more neutral messages, or consider some finer configuration control of message styles and associated colours.
Describe alternatives you've considered
Options I've considered:
Additional context
This is particularly relevant in cases where we would like to grant visibility of our development processes to less technical members of staff, who may interpret a number of our messages as errors.
The text was updated successfully, but these errors were encountered: