Onboarding schema changes - #4285
Merged
wavehassman merged 9 commits intoJun 26, 2026
Merged
Conversation
wavehassman
marked this pull request as ready for review
June 19, 2026 18:09
getheobald
changed the base branch from
develop
to
feature/onboarding-improvement
June 19, 2026 18:11
wavehassman
requested changes
Jun 21, 2026
This file contains hidden or 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.
Changes
Necessary schema changes for onboarding improvements.
Notes
The previous getAllOrganizationFaqs service method returned everything that wasn't a part review FAQ, but it's actual function is to return the recruitment FAQs for the recruiting page. I changed it to do that, but I'll need to rename it through the whole stack so it's clear that it's actually just returning recruiting FAQs not all FAQs. But I left a comment and saved that for when I'm actually working on those files.
Totally forgot to add ticket number to commits, soz hope that's ok
Test Cases
No new behavior, just ran existing tests
Checklist
It can be helpful to check the
ChecksandFiles changedtabs.Please review the contributor guide and reach out to your Tech Lead if anything is unclear.
Please request reviewers and ping on slack only after you've gone through this whole checklist.
yarn.lockchanges (unless dependencies have changed)