[Feature/Idea]: OAuth flow to store GitHub token about komac HOT 4 OPEN

The thinking behind getting a token and not using OAuth flow was that Komac is very very new in this world, and people generally don't trust giving their account access to an unknown OAuth application.

It's the same thing as giving your PAT to an unknown application. I don't see why that would be the reason.

from komac.

The thinking behind getting a token and not using OAuth flow was that Komac is very very new in this world, and people generally don't trust giving their account access to an unknown OAuth application. Once Komac gets popular, and normal contributors start preferring Koamc over YamlCreate and WinGet-Create, we can add it as a feature that will work side-by-side with the normal storing of a token in the Credentials store. This way, (privacy/security)-concerned people will have the option to just give a token, and also have an optional choice to use a more convenient OAuth flow. As of now, I think we should look more into testing and finding bugs in manifest creation, and this issue can be postponed for a while.

from komac.

OAuth application can access some of the private information, which is not possible by just using a PAT.

from komac.

I could do but as @vedantmgoyal2009 said, my concern is I'm not a big corporation like Microsoft so it's difficult to people to trust a GitHub app from a sole developer. I could always add this as an option, but this would be something I'd look into in the future.

from komac.