-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ft schedule technical interview #169
Merged
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
iChris-tian
approved these changes
Dec 2, 2024
MUNYESHURImanzi
approved these changes
Dec 2, 2024
bahati10
force-pushed
the
ft-schedule-technical-interview
branch
from
December 2, 2024 10:10
8beddc7
to
24e8d07
Compare
bahati10
force-pushed
the
ft-schedule-technical-interview
branch
from
December 2, 2024 10:53
24e8d07
to
f6ee8b5
Compare
bahati10
force-pushed
the
ft-schedule-technical-interview
branch
from
December 2, 2024 11:12
f6ee8b5
to
e5ed95d
Compare
* fix: remove the rm step * test: run on PR * test: test pusher cluster env * fix: add notification envs * test: add pusher key * fix: add the pusher app key * fix: log container start output * fix: remove the e flag * fix: revert changes * fix: re-add the pusher app key * fix: add pusher app key value * fix: typo * fix: test env file * fix: syntax * fix: remove the env from run cmd * fix: revert changes * fix: revert changes * fix: wrap run cmd in an if statement * Revert "test: test pusher cluster env" This reverts commit 57b2bbe. * test: create env file * test: add error handling
- remove 'submitted' status - add comments for 'rejected status'
bahati10
force-pushed
the
ft-schedule-technical-interview
branch
from
December 6, 2024 11:13
4d791bc
to
c9b1a29
Compare
* fix: don't exit on cmd failure * fix: re-add values * fix: add new variables * test: add container name * fix: match ports * fix: add devpulse email * fix: port * fix: port * fix: remove container name * fix: remove extraneous node env * fix: add jwt key * fix: run on push
* fix (170): an author will be able to update a blog * fix (170): allow all users to create and update blogs
render
bot
temporarily deployed
to
ft-schedule-technical-interview - dev-pulse-bn PR #169
December 6, 2024 12:02
Destroyed
ceelogre
temporarily deployed
to
ft-schedule-technical-interview - atlp-devpulse-bn PR #169
December 6, 2024 12:02 — with
Render
Destroyed
Salim-54
added a commit
that referenced
this pull request
Dec 9, 2024
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.
PR Description
This PR allows the admin to invite a trainee applicant to the technical interview
Description of tasks that were expected to be completed
As a trainee applicant, I will receive an email with a meeting link for the interview invitation.
As an admin, I should be able to create, view, and update the status of the interview
How can this be tested?
.env.example
npm install
, thennpm run dev
to check if the app is running successfullyTrack PR (issue number & link)
Issue: #208
Screenshots (If appropriate especially on the frontend)
N/A