Open
Conversation
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
1 participant
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.
Title: Updating Years for Fury
Description:
Updated the recruitment portal year from 2023/2024 to 2025 across landing, dashboard, and backend components.
All
.envfiles are ignored locally and not included in this PR.No other functionality changes were made.
Testing:
Updated recruitment portal year to 2025 across landing, dashboard, and backend.
Tested locally — everything works fine;
.envfiles are ignored.Potential Flaw:
Pre login #2023Wrapped seems fine. Post-login
#2023Wrappedis part of an image and needs a new image to reflect 2024, so only after that the change can be made.Checklist: