Documentation for proj-frontiers

• Source Repo: https://github.com/ucsb-cs156/proj-frontiers
• Github Actions: https://github.com/ucsb-cs156/proj-frontiers/actions

Documentation

Backend	Frontend (Storybook/Chromatic)
javadoc	storybook	build info

Test Coverage

Backend		Frontend
Jacoco	Pitest	Coverage	Stryker
jacoco	pitest	coverage	stryker

Open Pull Requests

Documentation for PRs

Pull Request			Backend	Frontend (Storybook/Chromatic)
PR	Branch	Author	Javadoc	storybook	build info
PR 483	copilot/fix-2489e1c3-4fef-48bb-8f84-80f8aea4283e	app/copilot-swe-agent	javadoc	chromatic sb	build info
PR 476	copilot/fix-409	app/copilot-swe-agent	javadoc	chromatic sb	build info
PR 475	copilot/fix-406	app/copilot-swe-agent	javadoc	chromatic sb	build info

Test Coverage for PRs

Pull Request			Backend		Frontend
PR	Branch	Author	Jacoco	Pitest	Coverage	Stryker
PR 483	copilot/fix-2489e1c3-4fef-48bb-8f84-80f8aea4283e	app/copilot-swe-agent	jacoco	pitest	coverage	stryker
PR 476	copilot/fix-409	app/copilot-swe-agent	jacoco	pitest	coverage	stryker
PR 475	copilot/fix-406	app/copilot-swe-agent	jacoco	pitest	coverage	stryker

Notes

If links in the PR tables don’t work, note the following:

• Backend links may not be updated for PRs that do not touch the backend code.
• Frontend links may not be updated for PRs that do not touch the frontend code.
• If a link doesn’t work when you expect that it should, check that the appropriate Github Actions workflow completed successfully.
• You can also check the contents of the gh-pages branch of this repo to see if they were updated with the appropriate directory.
• Note that the pitest runs that are triggered by PRs and by workflow 2 compute incremental pitest results based on stored history. It is rare, but this may occasionally be different from the results when doing a full pitest run from scratch, which is done every time a push is made to the main branch (for example, when merging a PR).