Last Updated: December 2, 2025
Current Version: v1.0.2
Audience: Anyone deploying code changes
| I want to… | Command |
|---|---|
| Save my work locally | git add . && git commit -m "description" |
| Deploy to staging | git push origin main |
| Deploy to production | Create a version tag (see below) |
Edit files in VS Code as usual.
git add .
git commit -m "Brief description of what changed"
Good commit messages:
git push origin main
What happens automatically:
Check status: https://github.com/chayner/alumni_lookup/actions
Test your changes: https://lookup-staging.bualum.co
Once you’ve verified staging works, create a release tag:
git tag v1.2.0 -m "Brief description of release"
git push origin v1.2.0
What happens automatically:
Check status: https://github.com/chayner/alumni_lookup/actions
Use semantic versioning: vMAJOR.MINOR.PATCH
| Change Type | Example | When to Use |
|---|---|---|
| PATCH | v1.0.1 → v1.0.2 | Bug fixes, small tweaks |
| MINOR | v1.0.2 → v1.1.0 | New features (backward compatible) |
| MAJOR | v1.1.0 → v2.0.0 | Breaking changes (rare) |
See current version:
git tag --list 'v*' | sort -V | tail -1
Check if tests failed: https://github.com/chayner/alumni_lookup/actions
If tests failed, fix the issue and push again.
If not yet deployed to production:
git revert HEAD
git push origin main
This creates a new commit that undoes the previous one.
Quick rollback to previous version:
heroku rollback --app alumni-lookup
This instantly reverts to the previous deploy while you fix the issue.
Don’t. Always test on staging first. The few minutes it takes can save hours of fixing production issues.
| Environment | Lookup Portal | Champions Portal |
|---|---|---|
| Staging | https://lookup-staging.bualum.co | https://champions-staging.bualum.co |
| Production | https://lookup.bualum.co | https://champions.bualum.co |
https://github.com/chayner/alumni_lookup/actions
If something goes wrong and you need help:
heroku logs --tail --app alumni-lookupheroku rollback --app alumni-lookup