-
Notifications
You must be signed in to change notification settings - Fork 0
Home
GitHub Pages website:
Week-by-week tracking of issues, pull requests, branches, and notes for the MVP of garden-tracking app FirstFrost hosted at givecoffee/firstfrostmvp.
For expanded week-by-week journey updates, see the included Devlog page for each section.
- Focus - the main thing the week was about, in one line
- Devlog link - goes to an expanded, more comprehensive breakdown of that week's phase in development
- GitHub Issues - every issue opened or worked on that week
- Pull Requests - every PR opened, merged, or reviewed
- Branches - branches created for the week's work
- Notes - anything worth remembering (decisions made, things that broke, what carried over to the next week)
- Devlog link - goes to an expanded, more comprehensive breakdown of that week's phase in development
- Demos - Walkthroughs of changes and demonstrations of features
Links go to GitHub directly. If a link 404s, the branch was probably deleted after merge.
Focus: Stand up the Postgres instance on Supabase and confirm the local dev environment matches the assignment requirements.
Week 1 Devlog: https://github.com/givecoffee/firstfrostmvp/wiki/Week-1-%E2%80%90-Devlog
GitHub Issues
Pull Requests
- https://github.com/givecoffee/firstfrostmvp/pull/17
- https://github.com/givecoffee/firstfrostmvp/pull/18
Branches
- https://github.com/givecoffee/firstfrostmvp/tree/1-provision-status-check
- https://github.com/givecoffee/firstfrostmvp/tree/schema%2F2-enums
Notes
- Provisioned the Supabase Postgres instance and confirmed connection from local tooling.
- Locked in version check workflow so later weeks don't drift on Postgres or psql versions.
Time Spent: 1 Hour
Issue titles follow the format used in Week 1: a verb-led description that maps cleanly onto a branch name. Example: Provision Supabase PostgreSQL instance → branch 1-provision-supabase-postgresql-instance.
Branch naming uses one of two patterns depending on the work:
-
<issue-number>-<short-description>for issue-driven work (e.g.,1-provision-supabase-postgresql-instance) -
<type>/<week>-<short-description>for setup or recurring work (e.g.,setup/week1-version-check,feature/jsonb-movie-details)
Pull requests reference the issue they close with Closes #N in the description so the issue auto-closes on merge.
Wiki updates happen at the end of each week as part of the dev update. If a week's section is still showing placeholder text, that week hasn't been wrapped up yet.