Committing straight to main will trigger CI/CD and automatically deploy to heroku.
Sometimes Heroku will cache and read old files after a successful deploy. When this happens I have found that going to Heroku and restarting the app's dynos to help.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Run this in a separate terminal to watch for changes in the sass files.