🚀 ServiceTap Setup Wizard
Sets up your own copy of GoMining ServiceTap — signs you into GitHub, forks the repo, and configures your account(s) automatically.
Step 1 — Sign in with GitHub
Before you start: you need a free GitHub account (sign up here if you don't have one) and your GoMining login. The whole setup takes about 10 minutes.
Click the button below and GitHub will show you a short code. You type that code on GitHub's own website to approve this wizard, so your GitHub password is never entered here. The wizard asks for two permissions: to make your own copy of the project (called a "fork") and store your settings in it, and to edit the schedule file in that copy. Nothing is kept after you close this tab.
Step 2 — Fork the repo
Creates your own copy at .
Step 3 — Your GoMining account(s)
You'll grab your GoMining login with a one-click bookmark. No DevTools, no copying values by hand.
- One time only: drag this button up to your bookmarks bar → 📋 Capture GoMining Cookies
- Open a private / incognito window and log into app.gomining.com. Why private? GoMining changes your login every time it's used, so if the automation and your everyday browser share one login they can knock each other out. Afterwards just close the window — don't click "Log out".
- Click the bookmark. A green Copied! note appears on the GoMining page.
- Come back to this tab. Your login fills in below by itself — or press Paste from clipboard (the first time, your browser asks permission to read the clipboard; allow it).
No GitHub token needed. The wizard makes a random encryption key for you and stores it in your repo's Secrets; your automation uses it to keep each refreshed login safely in GitHub's cache.
Step 4 — Configuring your repo
Step 5 — Test run
Runs your automation once, right now, so you know it works before trusting the schedule.
🎉 You're set up
Optional next step: Sentry error monitoring, covered in your new repo's README ("Optional: Sentry error monitoring") — catches the rare case where the schedule itself fails to fire, which GitHub's own emails can't.