The date calculation is wrong as it now reads "For those who don't know, on New Year's Eve 2025-12-31 10:00 UTC (5:00 AM EST), .... We will leave the recording going until at least 2026-01-01 12:00 UTC (7:00 AM EST)""
The date calculation is wrong as it now reads "For those who don't know, on New Year's Eve 2025-12-31 10:00 UTC (5:00 AM EST), .... We will leave the recording going until at least 2026-01-01 12:00 UTC (7:00 AM EST)""
Fixed and pushed to main, should show up on next website update. It was the same issue as the previous date calculations. The code was assuming the announcement would only be shown in Dec and on Jan 1st. It wasn't updated, after we decided for the announcement to start showing in Nov.
Fixed and pushed to main, should show up on next website update. It was the same issue as the previous date calculations. The code was assuming the announcement would only be shown in Dec and on Jan 1st. It wasn't updated, after we decided for the announcement to start showing in Nov.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The date calculation is wrong as it now reads "For those who don't know, on New Year's Eve 2025-12-31 10:00 UTC (5:00 AM EST), .... We will leave the recording going until at least 2026-01-01 12:00 UTC (7:00 AM EST)""
The number in words is not incrementing - it says
get_new_year_show_ordinal_year says Fourteenth, when it should be Fifteenth
Fixed and pushed to main, should show up on next website update. It was the same issue as the previous date calculations. The code was assuming the announcement would only be shown in Dec and on Jan 1st. It wasn't updated, after we decided for the announcement to start showing in Nov.