3 ms·
The only time I could see myself using this is in the following scenario; 1. Browsing repos. 2. See a quick fix I could make (like a typo) 3. Open up the cod
by cachestash 6y ago
The only time I could see myself using this is in the following scenario;
1. Browsing repos.
2. See a quick fix I could make (like a typo)
3. Open up the code space view, make the change, add and commit it.
For my daily needs I would never replace an online IDE with my local IDE. I see no value in doing that. My concern would be for when github has a service outage. I am without my IDE until they resolve the issue? With a local IDE I can just continue to work on my branch and push it when GH comes back online.
- MauranKilom 6y ago> The only time I could see myself using this is in the following scenario You can already do this. There's an edit button when you view any file and a streamlined process for turning your change into a PR. I don't think Codespaces will make this any faster. Maybe you can fix slightly less trivial things due to the IDE support but on the level you described no new capabilities are added.
- radus 6y agoI think with the same editor experience as I use on my own machine, I can fix substantially more complicated issues, with significantly less effort.