Kyℓe Hensel

> I would rather make sure we only push to the main branch when CI is passing I'm not familiar with ELI's CI system, but just a general comment: This...

hi, i'd like to fix this in iD, can anyone share an example feature which still has this issue? or alternatively, do we remember which NSI version had this issue?...

@valerio-bozzolan I think your query only considers wikidata items which have an [image`P18`](http://wikidata.org/wiki/Property:P18) property? but we want every photo from commons, even the ones with no linked wikidata item. For...

@ritiksingh3202 we don't assign issues, anyone is welcome is submit a PR. However: We already have a PR for this issue (#8914) which was rejected. The only alternative solution is...

I think a nicer solution would be to make the popup appear instead of this error, so that splitting a line is a more streamlined process. But I thought I'd...

all the conflicts from 4dc4e7d and e25af7c should be fixed now

for anyone who wants to solve this issue, widths [for TW](https://github.com/openstreetmap/iD/blob/490c86fa3985deee78cc541c7c1e3c3afd56b108/data/address_formats.json#L121-L128) can be defined in [data/address_formats.json](https://github.com/openstreetmap/iD/blob/develop/data/address_formats.json) like this example: https://github.com/openstreetmap/iD/blob/490c86fa3985deee78cc541c7c1e3c3afd56b108/data/address_formats.json#L137-L147

to me, it seems like a good idea to unify the style for _all_ crossing values. because `crossing=*` is slowly becoming less relevant, and the emerging tagging schema (`crossing:markings`) has...

> Line breaks on the values and keys (break all) would be great too. I tried this, but unfortunately it's non-straightforward, because the text is rendered in an `` element,...

this sounds like a candidate for #11189