Follow-up cleanup to the timezone troubleshooting section (post #313 investigation):
Remove the sentence referencing a deployment seeing times 2 hours behind (customer-specific detail; docs should not mention customers)
Remove the warning about downstream tzoneu2s() conversion code - it described one customer's post-approve hook, not DC behaviour
No technical content lost: the fix steps, notes on region/area TZ IDs vs fixed offsets, and the new-timestamps-only caveat remain.
Follow-up cleanup to the timezone troubleshooting section (post #313 investigation):
- Remove the sentence referencing a deployment seeing times 2 hours behind (customer-specific detail; docs should not mention customers)
- Remove the warning about downstream `tzoneu2s()` conversion code - it described one customer's post-approve hook, not DC behaviour
No technical content lost: the fix steps, notes on region/area TZ IDs vs fixed offsets, and the new-timestamps-only caveat remain.
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.
Follow-up cleanup to the timezone troubleshooting section (post #313 investigation):
tzoneu2s()conversion code - it described one customer's post-approve hook, not DC behaviourNo technical content lost: the fix steps, notes on region/area TZ IDs vs fixed offsets, and the new-timestamps-only caveat remain.