This looks very similar to #17, but in the opposite direction. That issue made the items compare on dates, and the net effect was that the day a request is entered should be 0-day; a request entered on one Sunday (the 1st), with expiration at 14 days, should still be on the list 2 weeks from that day (both the 8th and 15th), but fall off the following Monday (the 16th).
Make the query and the "am I expired?" code match this behavior.
This looks very similar to #17, but in the opposite direction. That issue made the items compare on dates, and the net effect was that the day a request is entered should be 0-day; a request entered on one Sunday (the 1st), with expiration at 14 days, should still be on the list 2 weeks from that day (both the 8th and 15th), but fall off the following Monday (the 16th).
Make the query **and** the "am I expired?" code match this behavior.
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.
This looks very similar to #17, but in the opposite direction. That issue made the items compare on dates, and the net effect was that the day a request is entered should be 0-day; a request entered on one Sunday (the 1st), with expiration at 14 days, should still be on the list 2 weeks from that day (both the 8th and 15th), but fall off the following Monday (the 16th).
Make the query and the "am I expired?" code match this behavior.
Closing this in preference to #41