Repository navigation
Feature batchsend - #148
Open
michael4yardwork-afk wants to merge 2 commits into
Open
michael4yardwork-afk wants to merge 2 commits into
michael4yardwork-afk wants to merge 2 commits into
Conversation
This branch has not been deployed
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.
Summary
This PR adds asynchronous bulk application stage updates with per-applicant email tracking, alongside recruitment UI improvements, Horizon platform functionality, and server tooling updates.
Changes
People Portal recruitment
Horizon
Server and repository tooling
baseUrlconfiguration while retaining the@/*path alias.Validation
The Nx server test target’s Unix-style
NODE_ENV=testcommand is not directly compatible with Windows, so the server tests were run using the equivalent PowerShell environment setting.Note for Ian:
There was a merge conflict when I implemented this feature since I had initially committed my changes to Sriya's master branch instead of the feature branch, and so I had to stash and recommit to the correct branch. I tested to make sure the merge conflict didn't cause any loss in functionality, but I'm still paranoid and think its worth double checking.