testing github workflow

[Howard-nolan]

Summary

Set up the initial GitHub automation for this repository — including a default pull request template and a workflow that appends “What I Learned” notes to LEARNINGS.md whenever a PR is merged.

What I Learned

• Why: Keeping a running record of lessons learned makes progress visible and reinforces key concepts from each phase of the project.
• How: Used a GitHub Action triggered on merged pull requests to extract the “What I Learned” section and append it to LEARNINGS.md.
• Gotcha: Initially forgot that Actions only trigger from the default branch; ensured the workflow YAML lives on main.
• Next time: Test new workflows with a small dummy PR like this one before relying on them in production.

Demo / Evidence

• Verified that the PR template auto-populates new pull requests.
• After merge, expect the Action log under the Actions tab to show “Append Learnings” → ✅ Success.
• LEARNINGS.md should have a new entry titled with today’s date and this PR number.

Follow-ups

• Add the same automation to future Go-based projects.