-
Notifications
You must be signed in to change notification settings - Fork 4
Flipping over 2025 and getting ready for 2026. #86
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -26,3 +26,6 @@ junit.xml | |
|
|
||
| # generated | ||
| src/version.json | ||
|
|
||
| # videos | ||
| public/videos/ | ||
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
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
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
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Potential bug: Countdown timers now use a date string without a timezone, causing them to resolve to the user's local time instead of a single global time.
Description: The application's countdown timers were changed to use a hardcoded date string,
2026-08-17T00:00:00, without a timezone specifier. Both the nativeDateconstructor and themoment.jslibrary interpret such strings in the user's local timezone. The previous implementation contained logic to synchronize the countdown to a specific moment in Pacific Time. As a result of this change, users in different timezones will see the countdown end at different absolute times, which can cause significant confusion for a globally coordinated event like a hackweek.Suggested fix: To ensure the countdown is synchronized globally, modify the date string to include a timezone. For example, use an ISO 8601 string with a UTC designator, such as
'2026-08-17T07:00:00Z', to represent a specific moment (e.g., midnight Pacific Daylight Time). Alternatively, restore the logic that dynamically calculates the target time in a specific timezone.severity: 0.7, confidence: 0.95
Did we get this right? 👍 / 👎 to inform future reviews.