Skip to content

Conversation

@arlobelshee
Copy link
Contributor

We want to maximize the ability to glance at a git summary and instantly see the right things to pay attention to. Do emoji help?

@JayBazuzi
Copy link
Collaborator

We can decouple the notion of 4 levels of risk from the actual annotation used, and let teams choose the style that suits their context.

Risk levels

  • Safe...
  • Validated...
  • Risky...
  • (Probably) Broken...

Notation suggestions

  • ., ^, !, @
  • ., o, O, @
  • 💚, ✅, 💣, 💥

@arlobelshee
Copy link
Contributor Author

We can decouple the notion of 4 levels of risk from the actual annotation used, and let teams choose the style that suits their context.

Risk levels

  • Safe...
  • Validated...
  • Risky...
  • (Probably) Broken...

Notation suggestions

  • ., ^, !, @
  • ., o, O, @
  • 💚, ✅, 💣, 💥

That's an interesting suggestion. Do you have the space to push a commit to this PR branch with a concrete approach to apply it? I tried, but struggled.

In particular, I wanted to keep the table that introduces the risk levels very concrete. I felt removing the codes from that table raises the level of abstraction. It requires people to tie a concept to a name, then a name to the encoding. That's harder than tying a name, a concept, and an encoding all together as one thing. So perhaps the table gives the primary encoding, then we state alternate notation suggestions? Or something like that?

Anyway, I could use some help in finding the most clear way to describe this.

@JayBazuzi
Copy link
Collaborator

I'll see what I can do

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants