Staticman is the middle man who pushes comments on a GH site as commits from an account (let’s call it Staticman-account) to the site’s repo. The Staticman-account and repo’s account can be the same but are suggested to be different. A token or a GitHub app is required to make a commit from the Staticman-account and to read a config file in the site’s repo, the staticman.yml file.

  • app.json: describes Staticman so Heroku knows how to install and deploy it,
  • config.js: manages configs of Staticman,
  • config.{ENV}.yml: contains config values for Staticman, env vars can be used instead,
  • *ocker*: for installing and deploying Staticman using Docker,
  • siteConfig.js: manages configs of Staticman for the site,
  • staticman.sample.yml: a sample to create staticman.yml which is the site config file and must be put in the site’s repo.
  • key to encrypt sensitive fields in the site config file staticman.yml.

For v2

  • Scope of the token: public_repo is enough if the site repo is public, otherwise repo is needed for accessing a private repo.
    • Travis Downs in his blog post wrote that user is necessary: so far I don’t see the reason for that.
    • Ujjwal Verma noted to use admin:repo_hook: the returned error code would be GITHUB_CREATING_PR which means that GitHub could not create a PR with this scope (when moderation is on). Or maybe he used a GitHub app instead of a token?

Other notes

  • Webhook payload URL is /v1/webhook. This function still works, even though the test request sent by GH after the webhook is added seems to fail.
  • The site URL set up on Akismet and the config should both be the URL of where you host Staticman. The comment form sends form data to Staticman at this URL, Akismet also tries to catch spams at this URL, those akismet fields in staticman.yml are for Akismet to know what data it receives.