Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It feels this way with PATs as well, with legacy PATs still necessary for most of the things I use them for, despite being pushed into the newer ones. And the documentation is terrible. I had the exact same thought, the PAT transition feels like an unfinished feature as does the API transition.

For me the API transition is even more bizarre since it’s almost trivial to wrap REST calls with GraphQL.

What it feels like to me is a mounting level of serious technical debt which isn’t being addressed, and if that’s not a sign of trouble in a product like GitHub, I don’t know what is.



The only reason holding me from using granular PATs is that they _must_ have an expiration date and the maximum is one year.


Yeah - I understand why they do this but I reckon they could have made them renewable without having to replace the tokens themselves.

Also granular PATs still don’t work everywhere.


What is PAT?



Personal Access Token




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: