Diffy documentation
  • Features
    • 👋Welcome
    • Mask & Exclude
    • JavaScript snippets
    • HTTP headers
    • Cookies
    • CSS overrides
    • Mock content
    • Dealing with Dynamic Elements
      • Freeze Carousels / Sliders
      • Cookies Policy Popups
    • Configure project from YAML file
    • Zapier integration (JIRA, Trello, Basecamp integrations)
    • Bypass protection Cloudfront, Akamai, Incapsula
      • Bypass Akamai protection
      • Bypass Imperva Incapsula protection
    • Tags
    • Local development
      • DDEV add-on
      • Lando integration
      • Standalone docker container
      • Ngrok
  • Automation
    • 💡Overview
    • GitHub Pantheon CircleCI
    • GitHub Pantheon GitHub Actions
    • GitHub Tugboat
  • Tutorials
    • Comparison review
Powered by GitBook
On this page
  1. Automation

GitHub Tugboat

PreviousGitHub Pantheon GitHub ActionsNextComparison review

Last updated 3 months ago

Once you configured Tugboat to build your environments it is really easy to add Diffy visual testing to check those environments.

We have an example at

Once you have your environment ready (after all cache rebuild, config import) you need to trigger:

- wget -O /usr/local/bin/diffy https://github.com/diffywebsite/diffy-cli/releases/latest/download/diffy.phar
- chmod +x /usr/local/bin/diffy
- diffy auth:login ${DIFFY_API_KEY}
- diffy project:compare ${DIFFY_PROJECT_ID} prod custom --env2Url="${TUGBOAT_SERVICE_URL}" --commit-sha=${TUGBOAT_PREVIEW_SHA}

For this you need to configure two Tugboat variables:

DIFFY_API_KEY to be generated from

DIFFY_PROJECT_ID it is your project id. You can find it under project settings, General tab

Diffy configuration

In order for Diffy to post results back to GitHub as a check you need to add github repo to Diffy's Project settings under Notifications / GitHub and authenticate Diffy's GitHub check by visiting

https://github.com/DiffyWebsite/diffy-tugboat/tree/master/.tugboat
https://app.diffy.website/#/keys
https://github.com/apps/diffy-testing