The Expiry section in the new page should support custom times beyond the fixed presets (Never/1h/1d/1w/30d): a 'Custom' option that reveals an input for a number + unit selector (minutes/hours/days/weeks/months). API already accepts arbitrary Go-duration expires_in values, so this is mostly UI: validate sensibly (min 1 minute, max maybe 1 year), pass through as duration string.
The Expiry section in the new page should support custom times beyond the fixed presets (Never/1h/1d/1w/30d): a 'Custom' option that reveals an input for a number + unit selector (minutes/hours/days/weeks/months). API already accepts arbitrary Go-duration expires_in values, so this is mostly UI: validate sensibly (min 1 minute, max maybe 1 year), pass through as duration string.
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 Expiry section in the new page should support custom times beyond the fixed presets (Never/1h/1d/1w/30d): a 'Custom' option that reveals an input for a number + unit selector (minutes/hours/days/weeks/months). API already accepts arbitrary Go-duration expires_in values, so this is mostly UI: validate sensibly (min 1 minute, max maybe 1 year), pass through as duration string.
Implemented in
127c12c+15ce7ff: Custom radio reveals number+unit select (minutes/hours/days/weeks/months, months=30d); client-side validation 1min-1year with inline error; composed Go-duration string sent as expires_in; presets unchanged. Verified in-browser.