Skip to content

docs: update readme with current tech stack and github actions badge#66

Merged
chrisjwalk-bot merged 8 commits into
mainfrom
docs/update-readme
Mar 15, 2026
Merged

docs: update readme with current tech stack and github actions badge#66
chrisjwalk-bot merged 8 commits into
mainfrom
docs/update-readme

Conversation

@chrisjwalk-bot
Copy link
Copy Markdown
Collaborator

@chrisjwalk-bot chrisjwalk-bot commented Mar 15, 2026

Closes #67

Changes

  • Replace stale Azure DevOps CI badge with GitHub Actions CI badge
  • Rewrite description to accurately reflect the current stack
  • Add Tech Stack section covering frontend, backend, and tooling
  • Simplify Getting Started section (remove VS2022/VS Code sections, use fenced code blocks)
  • Remove references to Azure DevOps, SpaServices, and outdated commands

The README.md is generated by pnpm nx run web-app:update-readme from docs/github-readme.md + apps/web-app/src/assets/home.md.

@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Comment thread README.md
@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

Copy link
Copy Markdown
Collaborator Author

@chrisjwalk-bot chrisjwalk-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch! The postinstall script runs update-readme, so pnpm install auto-regenerates README.md from two source files:

  • docs/github-readme.md — just the CI badge (GitHub-only)
  • apps/web-app/src/assets/home.md — the shared content (also rendered on the app home page)

Nothing was lost — the new content is intentional. The old README had an Azure DevOps badge that no longer works, VS2022/VS Code sections, and no mention of the actual stack.

That said, the two-file setup is confusing. A simpler approach: make README.md the single source of truth and have the postinstall script derive home.md from it (stripping the badge). That way there's only one file to edit and the app home page stays in sync.

Should I flip the direction — edit README.md directly, generate home.md from it?

- README.md is now the single source of truth (edit this directly)
- update-readme target now generates home.md by stripping the badge line
- Remove docs/github-readme.md (no longer needed)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@chrisjwalk
Copy link
Copy Markdown
Owner

If you flip it, the problem still remains that we have to remember to do a pnpm i before committing any changes to the file. We'd really just like this all to be automated.

@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

Copy link
Copy Markdown
Owner

@chrisjwalk chrisjwalk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we also add some info about the built in features for the app? Like the DX stuff, notification center, auth flow, etc.

It's also still not clear here how README.md is the single source of truth and how/when home.md get's generated from that

- Add .lintstagedrc.cjs with function syntax to run update-readme
  whenever README.md is committed, then auto-stage home.md
- Move lint-staged config out of package.json (functions require .cjs)
- Remove update-readme from postinstall (no longer needed there)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@chrisjwalk-bot
Copy link
Copy Markdown
Collaborator Author

Good point! Fixed in the latest commit. Added a .lintstagedrc.cjs that runs update-readme automatically whenever README.md is staged for commit, then auto-stages home.md too. No more manual pnpm install needed — just edit README.md and commit as normal.

Also removed update-readme from postinstall since it's no longer needed there.

@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

chrisjwalk
chrisjwalk previously approved these changes Mar 15, 2026
Uses irongut/CodeCoverageSummary to parse cobertura XMLs and:
- Write a coverage table + badge to the GitHub Actions job summary
- Post a sticky PR comment with the coverage report

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

@chrisjwalk
Copy link
Copy Markdown
Owner

The code coverage report is only showing the app, we need all of the tests (and should fix the missing coverage on the app).

- Add debug.spec.ts covering all 6 add methods, clearAll, and markAllRead
- Change CI test step to always run test:all so coverage report
  includes all libs, not just affected projects

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

…sts in CI

- Revert CI test step to nx affected (only test:all on main push)
- Add annotation to coverage PR comment noting it's affected-only
- Add vitest perFile coverage thresholds (80% all metrics) to catch
  new code added without tests
- Exclude *.routes.ts, *.config.ts, main.ts, environments from coverage
- Fix coverage gaps to meet thresholds:
  - notification.store: add markRead multi-notification test (covers
    ternary else branch)
  - notification-list: add read-state and iconFor fallback tests
  - notification-bell: add singular aria-label, handset branch,
    overlay toggle-close, and re-open tests
  - counter.store: add inputCount and event dispatch tests (covers
    reducer callbacks via withCounterReducer)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown

Azure Static Web Apps: Your stage site is ready! Visit it here: https://green-water-08792290f-66.eastus2.2.azurestaticapps.net

@github-actions
Copy link
Copy Markdown

Note

Coverage shown for affected projects only. Per-file thresholds (80%) are enforced by vitest.

Code Coverage

Package Line Rate Branch Rate Complexity Health
src 100% 100% 0
src.lib.home 100% 100% 0
src 100% 100% 0
src.lib.services 100% 100% 0
src.lib.state 99% 100% 0
src 100% 100% 0
src.lib.components.forecast-table 100% 100% 0
src.lib.components.weather-forecast 100% 100% 0
src.lib.models 100% 100% 0
src.lib.services 100% 100% 0
src.lib.state 100% 100% 0
src 100% 100% 0
src.lib.components.counter 100% 100% 0
src.lib.components.counter-container 100% 100% 0
src.lib.state 100% 100% 0
src 100% 100% 0
src.lib.login 100% 100% 0
src.lib.state 100% 100% 0
src 100% 100% 0
src.lib.components 97% 83% 0
src.lib.state 100% 100% 0
src.lib.testing 100% 100% 0
app 100% 100% 0
app.debug 83% 100% 0
Summary 98% (329 / 334) 99% (88 / 92) 0

@chrisjwalk-bot chrisjwalk-bot merged commit b7b5b9e into main Mar 15, 2026
3 checks passed
@chrisjwalk-bot chrisjwalk-bot deleted the docs/update-readme branch March 15, 2026 19:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update README to reflect current tech stack

2 participants