That's the reason I stopped installing random extensions and even themes in VS Code, they are too dangerous.
I just moved to Zed (zed.dev). Has everything I need
GitHub is investigating unauthorized access to their internal repositories
181–190 of 359 posts
Re: GitHub is investigating unauthorized access to their internal repositories
#182Earlier quoted context omitted.
> I guess they mean customer's private repos? I don't think so. It is even worse if a random developer has access to customers' private repos.
Good point. Then why in the world would a company have 3,500 repos? Do they create a repo for each employee?
Re: GitHub is investigating unauthorized access to their internal repositories
#183Earlier quoted context omitted.
> I guess they mean customer's private repos? I don't think so. It is even worse if a random developer has access to customers' private repos.
Good point. Then why in the world would a company have 3,500 repos? Do they create a repo for each employee?
Re: GitHub is investigating unauthorized access to their internal repositories
#184Earlier quoted context omitted.
I just moved to Zed (zed.dev). Has everything I need
I really need to find the time to properly test Zed. I'm mainly using PHP Storm and I love what it can do, especially when it comes to code discovery and auto-completion. I'm not a huge fan of having a bloated toolbox, I never use PHP Storm's included terminal or database browser. Zed was super impressive when I first started it, but I don't know yet how it compares with PHP Storm.
It wont be the same experience at all, the debugging and deployment stuff will be strictly inferior and the jump to code might be less impressive.
Zed has LSP support though, so if you have a good LSP then you’ll get some nice IDE features, but they’re not really comparable.
Re: GitHub is investigating unauthorized access to their internal repositories
#185Earlier quoted context omitted.
This comment reminds me of a joke where the punchline is that a person is so poor that burglars break in to their house and leave money. Similarly, I could see ransomware groups hacking in and feeling bad for GH so they improve a few things to help them get to at leave nine fives of uptime.
Just in case you are not aware, a joke loses its fun factor if you explain it.
Re: GitHub is investigating unauthorized access to their internal repositories
#186Re: GitHub is investigating unauthorized access to their internal repositories
#187That's the reason I stopped installing random extensions and even themes in VS Code, they are too dangerous.
I just moved to Zed (zed.dev). Has everything I need
No shade on Zed, sometimes in-house security tools just don't like new software.
Re: GitHub is investigating unauthorized access to their internal repositories
#188Earlier quoted context omitted.
I just moved to Zed (zed.dev). Has everything I need
does it have some kind of sandboxing for its extensions?
Re: GitHub is investigating unauthorized access to their internal repositories
#189Earlier quoted context omitted.
This comment reminds me of a joke where the punchline is that a person is so poor that burglars break in to their house and leave money. Similarly, I could see ransomware groups hacking in and feeling bad for GH so they improve a few things to help them get to at leave nine fives of uptime.
Just in case you are not aware, a joke loses its fun factor if you explain it.
Re: GitHub is investigating unauthorized access to their internal repositories
#190Earlier quoted context omitted.
in my org, devs don’t have access to customer data directly, and sysadmins don’t have access to modify code. It’s a simple rule from a simpler time, to limit the risk of total compromise.
Repos should not contain customer data.