Aleksandr Sergeev

Actually before the action waited for 0.3 seconds between the requests. Apparently if we return this wait, the execution time will skyrocket. But we can try if there's no other...

Just to mention: manual reviewing changes shouldn't be a provlem now. All you have to do is: 1. Copy `.env.example` to some other file, preferrably having `.env` extension so it...

As this action requiers user GitHub API token, I think the only possible solution for testing would be be: Put someone's GitHub API token as a repository secret and automatically...

We'd better add a kind of dry-run option that will be able to run without user password. If you have some spare time, that would be great if you tested...

It would be also great if you could take a look at #375 as it appears to solve many issues and so it would be gread to merge it ASAP...

Yeah, I like the first solution. In addition we can make the output more verbose for this dry run. I'll try to implement it, but I still suggest it after...

@anmol098 so, we'll need a sample GitHub read token together with WakaTime read token in repository secrets. I think, maybe we should use yours? Your profile seems to be very...

@anmol098 great, keep me informed!

Or better do both and compare the results because we shouldn't forget about local running possibility.

I would also suggest publishing the Docker image for every pull request (named after the pull request, of course) for us and users to be able to test the action...