You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is inspired by the #feed-nsi-github channel on the OSM-US Slack (slack.openstreetmap.us for those unfamiliar). I'm not sure how it works (RSS? Webhooks? Buzzword-of-the-month?) but it is very useful to see what issues are being updated with questions or new information. I desire the same for the errorlist that various of the npm run commands produce. Here's the comment I queried@bhousel on the Slack with:
would it be possible to have a feed like #feed-nsi-github but for the errors instead of the issue comments? I don't know how that would work but it would be nice to know which problems are newly-arisen and which have been kicking around awhile.
In particular I am interested in the build_wikidata.js errors, but I imagine putting all errors and warnings in the same feed if possible would be most fruitful.
edit:this time in the right repo
The text was updated successfully, but these errors were encountered:
The #feed-nsi-github channel works by setting up Slack’s RSS application to read the RSS feed produced by this repository. So the build script could produce the same output but in RSS format. That would be pretty straightforward in a static GitHub Pages setup, but I’m not sure how it would interact with the single-page application here.
This issue is inspired by the
#feed-nsi-github
channel on the OSM-US Slack (slack.openstreetmap.us for those unfamiliar). I'm not sure how it works (RSS? Webhooks? Buzzword-of-the-month?) but it is very useful to see what issues are being updated with questions or new information. I desire the same for the errorlist that various of thenpm run
commands produce. Here's the comment I queried @bhousel on the Slack with:In particular I am interested in the
build_wikidata.js
errors, but I imagine putting all errors and warnings in the same feed if possible would be most fruitful.edit:this time in the right repo
The text was updated successfully, but these errors were encountered: