change

[robbie3183]

Description

Motivation and Context

How has this been tested?

Screenshots (if appropriate)

Types of changes

Changes visible to users:

• [ ] Bug fix (prefix: fix - non-breaking change which fixes an issue)
• [ ] New feature (prefix: feat - non-breaking change which adds functionality)
• [ ] Breaking change (prefix: feat!! or fix!! - fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation (prefix: docs - improvements to any documentation content for users)
• [ ] Homepage (prefix: page - improvements to the Homepage #{HOMEPAGE} should lead to the place where one could actually change the homepage
• [ ] Contributing Guidelines (prefix: contrib - any improvements to documentation content for contributors - see Contributing

Internal changes:

• [ ] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
• [ ] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)
• [ ] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Checklist

• [ ] My code follows the code style of this project and passes npm run lint.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly. # {DOCUMENTATION} <------- this should lead to the doc that could be changed/ didnt find it
• [ ] My change has adequate Unit Test coverage.

Terms

• [ ] My contribution follow this project's contributing guide
• [ ] I agree to follow this project's Code of Conduct

[vercel[bot]]

@robbie3183 is attempting to deploy a commit to the reworkd Team on Vercel.

A member of the Team first needs to authorize it.