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

Review the style of posted updates in Slack, or allow more fine grained configuration of their appearance #2004

Open
instantiator opened this issue Jan 31, 2025 · 0 comments

Comments

@instantiator
Copy link

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
Image Image

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.

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

No branches or pull requests

1 participant