When you subscribe to Supercasper, we can plug directly into your existing workflows. This means we’ll collaborate with you inside your codebase, using GitHub for version control, Trello for task management, and secure methods for handling assets, credentials, and API keys.
Here’s how it works step by step:
You’ll receive a request to add our service account to your GitHub Organization.
We’ll only request write access to the repositories we actually need.
Your main branches (like main or production) stay protected:
All changes go through pull requests (PRs).
Direct pushes to production branches are blocked.
Code reviews and automated checks (tests, linting, builds) must pass before merging.
We create feature branches for each request (e.g. feature/login-form).
Every update comes as a PR, linked to the Trello card for visibility.
Pull requests are kept small and easy to review.
Once approved, we merge into your protected branch and let your CI/CD pipeline handle deployment.
Sometimes we need more than just code. Depending on your project, you may grant us access to:
Design files (Figma, Google Drive, Notion, etc.)
CMS platforms (WordPress, Webflow, or headless CMSes)
Cloud storage (S3, GCS, or Azure)
We’ll always request the least amount of access needed to complete your tasks.
Security is critical. Here’s how we handle credentials:
Never share secrets via Trello or email.
Store them in your own secure vault (1Password, AWS Secrets Manager, GCP Secret Manager, etc.).
Provide us with the appropriate role-based access or environment keys.
We work with .env files and version-controlled .env.example templates — but real keys never go into Git.
Secrets are injected via your CI/CD pipeline or local environment only.
Your private Trello board makes it easy to follow along:
Requests → In Progress → Review (PR) → Ready to Merge → Deployed → Done
Each Trello card links directly to its GitHub issue/PR.
If you need changes, leave comments on the Trello card — we’ll update the code and PR until you’re happy.
All our activity is tracked in GitHub Issues and PRs.
On offboarding, you can easily remove our GitHub access.
We recommend rotating API keys or credentials when pausing or ending a subscription.
What You Need To DoTo get us set up quickly, please:
Invite us to your GitHub org and relevant repos.
Share any design files or assets we’ll need.
Provide environment access (via your vault or CI/CD).
Confirm your Trello invite and start submitting requests.
With this setup, you stay in full control of your codebase, while we handle the heavy lifting on design, development, and delivery.
