Raine Revere

Here is where it errors: ```js try { const { conclusion, output } = await eslint_cli_1.eslint(filesToLint); await octokit.checks.update({ ...context.repo, check_run_id: checkId, completed_at: new Date().toISOString(), conclusion, output }); if (conclusion ===...

(unintentional close)

This actually seems like what is happening. It does not have write permission on forks: https://github.com/actions/labeler/issues/12#issuecomment-549901347

Yes, if I am understanding what you mean by shallow errors. I think until there is a better workaround for the permissions issue, the action should fail if there is...

Has anyone gotten this action to work when non-owners submit a pull request? I'm still having the same issue: https://github.com/cybersemics/em/pull/242/checks.

Let me know if this is something you're interested in. I noticed there were a lot of PR's without responses so I wanted to hold off on further development till...

Please don't add a procedural interface that mutates the module instance. It's more error-prone and messy if you need to revert the behavior back. If anything you could add `exitOnAbort:...

Please add a test and I can review. Thanks!

> What should it have changed into? Shouldn't it be at thought a even after undo? Wow, you're right! The cursor should be on `a` after the undo. Only navigation...

> When you say grouping issue, i am having a little confusion to understand what it exactly means, firstly. - Navigation actions immediately *after* the last edit should be grouped...