Skip to content

Conversation

@SaqAsh
Copy link

@SaqAsh SaqAsh commented Jul 30, 2025

Summary

There was a previous pr made that was merged into this "feature branch" that was not actually merged into main. This component is a component needed in stage and was written as an independent component for this repository.

Readiness Checklist

  • Self Review
    • I have performed a self review of code
    • I have run the application locally and manually tested the feature
    • I have checked all updates to correct typos and misspellings
  • Formatting
    • Code follows the project style guide
    • Autmated code formatters (ie. Prettier) have been run
  • Local Testing
    • Successfully built all packages locally
    • Successfully ran all test suites, all unit and integration tests pass
  • Updated Tests
    • Unit and integration tests have been added that describe the bug that was fixed or the features that were added
  • Documentation
    • All new environment variables added to .env.schema file and documented in the README
    • All changes to server HTTP endpoints have open-api documentation
    • All new functions exported from their module have TSDoc comment documentation

@SaqAsh SaqAsh requested a review from ciaranschutte July 30, 2025 18:20
@SaqAsh SaqAsh changed the title Feature/banner component Banner component implementation un-merged into main Jul 30, 2025
@SaqAsh SaqAsh marked this pull request as ready for review July 30, 2025 18:51
@SaqAsh SaqAsh changed the title Banner component implementation un-merged into main Banner component implementation not merged into main Jul 30, 2025
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.

2 participants