Sven

I am not sure if I understood this correctly, but I am trying to replace the following: ```java private void call(int i) { switch (i) { case 65: System.out.println(65); }...

Any resources on how to get started contributing? I have no experience with bytecode manipulation but would happily try to implement this. Maybe like a short todo overview/list or something...

> EDIT2: Alternately, defaulting to automatically display the variation glyphs like github is doing would also be acceptable (to me) This wouldn’t solve the problem but just shift it. Now...

> > Isn't that by design? That fonts and fallbacks are a user (and system) setting, not an application setting? > > Probably. It would also make polybar's job _a...

I guess is just a perspective way. I would create a release candidate that sticks longer around to gather feedback. You would introduce the new feature in a minor bump...

Are multiple signing keys still on the list? :thinking:

Now that you mention it, version control aware actually sounds super good. Like comparing the current build time to your last published tag maybe? So you could actually see the...

> I was picturing that this would work, but the `BREAKING CHANGE` would actually be parsed out of the body rather than from the footers. Strictly speaking, yes. A lot...

As you said, by convention. Nothing holds me back from adding it to the body. It makes sense to include metadata about commits inside of footers. It's a separation of...

The specification sounds more like `BREAKING CHANGE` is a special footer: > If included as a footer, a breaking change MUST consist of the uppercase text BREAKING CHANGE, followed by...