Fine-grained PAT form fails silently when custom expiration date exceeds the 1-year max #213224
Replies: 2 comments
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
@Alekzv9 Thanks for the clear repro steps. Silent failure with no message is definitely worth reporting. For now you can sidestep the picker with the One thing that might help whoever reads this: is the token for your personal account or an org? The docs say a max lifetime policy set by an org or enterprise owner can block longer lifetimes, so it'd be good to know if one applies. |
Uh oh!
There was an error while loading. Please reload this page.
Discussion Type
Product Feedback
Discussion Content
Steps: Settings → Developer settings → Fine-grained tokens → Generate new token → Expiration: Custom → pick a date more than 1 year away (e.g. 2027-12-30) → Generate token.
Expected: A visible error saying the max date is 2027-11-15.
Actual: Nothing happens. The browser console shows: An invalid form control with name='user_programmatic_access[custom_expires_at]' is not focusable. The date picker allows/displays a date beyond the max attribute, and no message is shown to the user.
Browser: Version 157.0.8103.51 (Official Build) (arm64)
All reactions