Chore/rename oobee oct #409
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds...
New Oobee UI
File renames as part of transition build
I've kept this PR as small as possible (~500 lines) by splitting it into PRs with manageable chunks of code
I've requested reviews from 1 reviewer
I've tested existing features (website scan, sitemap, custom flow) in both node index and cli
I've synced this fork with GovTechSG repo
I've added/updated unit tests
I've added/updated any necessary dependencies in
package[-lock].jsonnpm audit, portable installation on GitHub Actions