Robert Sese

Thanks for the report! Do you get the error for changes to any file? Also, can you share the path for a file that triggers the error?

Oh sorry one more question - can you also reproduce in safe mode (`atom --safe`)?

> And yes, I tried safe mode as well as a clean install of atom, all with the same results. Oy sorry, I spaced that you totally mentioned that in...

> Those errors actually led me to finding out the root of my problem is a duplicate of #977 Ahhh great, glad you found that one, that explains things. >...

Sorry for the trouble @shroudedcode - it looks like the issue is with https://github.com/shroudedcode/semantic-release-apm-example yes? Can you confirm if you published that package and then deleted/re-created the repository? I'm wondering...

Thanks for the report! To clarify, are you only having issues with your company's private repositories and otherwise have no issues with a repository owned by your user account for...

Hmm, though the error message is different, does this apply to your organization? https://github.com/atom/github/issues/1010#issuecomment-422882361

@jquinn-antaeus were you also seeing the "Query errors reported" Could not resolve to a Repository with the name" error message? For folks seeing that specific error, do you happen to...

Is there anything different about the repository that you can think of versus the rest of the repositories in your organization @Si-Thu-Thein? Do you have the same permissions on this...

While poking at this I was able to reproduce this behavior - I started by removing any saved credentials from Credential Manager. Then I cloned a private repository from Atom...