Daniel Schep

not sure, I don't have time really and am thinking of migrating to SSM Parameter Store for secrets anyway. @marcy-terui might tho.

This got fixed after I posted about it in the `#mapbox` shared channel in the OSM US Slack.

I'm not the maintainer, I believe @DavideViolante is currently maintaining this project.

Agreed. Or just archive it.

@ac360, tagging you so someone at serverless is aware this gh action exists without maintainers(afaik)

IMO that's too little information. You certainly couldn't implement the example rendering tree linked.

> I think two attributes are the best method of doing this. One for access with three possible values - yes (including plain highway=footway with no other tags), sort of,...

Which, thinking about it, could be implemented similarly to the `surface` tag. `access` currently only exists with a value of `false`. It could be updated to also include `true` when...

This feels like an oversimplification to me. For example, in [OpenTrailStash](https://gitlab.com/trailstash/openstyle) I rely on `class=wilderness`, `class=national_wildlife_refuge`, and `class=wildlife_management_area` to style wilderness areas, Wildlife Refuges, & WMAs differently from parks: 

I currently use the three values I mentioned, but I could see wanting more. What about retaining the original values as `subclass`?