This script saves GitHub issues in TSV format
The script has two software dependancies:
- GitHub CLI for querying GitHub API
jq
for transforming the output of the above to TSV format
This script saves GitHub issues in TSV format
The script has two software dependancies:
jq
for transforming the output of the above to TSV formatname: Post release to Jekyll Blog | |
on: | |
release: | |
types: [published] | |
# The GitHub Actions workflow Spincord uses to create and publish a new blog post for every published git tag release. | |
# This workflow is set up to publish a new blog post to the Spincord gh-pages/jekyll | |
# site every time a new release is published. The blog post uses the corresponding tag | |
# name in the title along with the release's body and the current date. |
Geojson.net will be a replacement for geojson.io, the simple editor for map data. In most ways, it has the same intent, goals, limitations, and ideas of geojson.io - they're both projects of mine.
I created geojson.io as a side project in 2013, and it thrived for a few years, as it simply solved the problem of previewing, modifying, and creating map data. I think it benefited from simplicity and unity of thought: it wasn't a product, it didn't have overarching design goals or any sort of leadership. There was the core functionality, and a bunch of functionality that pretty neatly layered on top of that without making the whole thing too intimidating. I'm pretty happy with how it went.
Over the last two or so years, though, geojson.io hasn't changed much, and the web has. Which means that, in a few ways, it's just straight-up broken: GitHub integration is broken, it was never updated to accommodate for the deprecation of anonymous gists, and
Install svg-inline-loader for webpack :
npm install svg-inline-loader --save-dev
Add it to your loaders in module.loaders
section of webpack.config.js
:
{
test: /\.svg$/,
loader: 'svg-inline-loader'
The Quick, Draw! dataset uses ndjson as one of the formats to store its millions of drawings.
We can use the ndjons-cli utility to quickly create interesting subsets of this dataset.
The drawings (stroke data and associated metadata) are stored as one JSON object per line. e.g.:
{
Making a bot? Making a bot in Python? Making a bot in Python that uses the Mastodon API? If so, chances are you need to get some credentials. Here's how I did it!
(The following tutorial uses Python 2.7, but if you're using Python 3+ everything should work substantially the same.)
I just started using it, but it looks like Mastodon.py is a pretty great library for working with the Mastodon API! However, all of the authentication examples use static files to store credentials, which I don't like—I'm afraid I'll accidentally push them to Github. I like to keep my authentication as close to the actual command that runs the program as possible, so usually I pass them on the command line to the script running my bot. To do this, I need to get the appropriate credentials on their own, as separate strings that I can cut and paste.
// Load the SDK | |
const AWS = require('aws-sdk') | |
const Fs = require('fs') | |
// Create an Polly client | |
const Polly = new AWS.Polly({ | |
signatureVersion: 'v4', | |
region: 'us-east-1' | |
}) |