zachleat’s avatarzachleat’s Twitter Archive—№ 42,340

        1. What’s the best way to automate this workflow (using GitHub as a cheap database)? 1. User opens GitHub issue (using an issue template form) 2. Tool parses GitHub issue text and commits it as a data file (JSON/YML/whatever) in the GitHub repository 3. Tool closes GitHub issue
          Permalink On twitter.com Twitter logo zachleat’s avatar ♻️ 2 Retweets ❤️ 15 Favorites Mood +4 🙂
      1. …in reply to @zachleat
        Correction: is there a tool that exists that already automates this workflow or something similar?
        Permalink On twitter.com Twitter logo zachleat’s avatar ❤️ 4 Favorites Mood 0
    1. …in reply to @zachleat
      I think we have a winner from @katydecorah—thanks @andeersg! @andeersg/1504826441325854725
      Permalink On twitter.com Twitter logo zachleat’s avatar ♻️ 1 Retweets ❤️ 8 Favorites Mood +4 🙂
  1. …in reply to @zachleat
    @katydecorah @andeersg Got an MVP going here: github.com/zachleat/github-issue-to-json-file Uses a GitHub issue form to generate a JSON data file in the repo (and closes the issue) See it in action on: github.com/11ty/11ty-community/issues/new/choose
    On twitter.com Twitter logo zachleat’s avatar ❤️ 13 Favorites Mood 0