diff --git a/source/ch-coding.ptx b/source/ch-coding.ptx index a1637dd..aa3a997 100644 --- a/source/ch-coding.ptx +++ b/source/ch-coding.ptx @@ -4,7 +4,7 @@
Codespaces

-While the quick GitHub.dev interface we used +While the quick VSCode.dev/GitHub interface we used to get started in is great for quick uploads or edits, many projects require the ability to run applications and execute code as you would on @@ -34,29 +34,29 @@ the green Create codespace on [branchname] button.

After the Codespace boots up, you'll have an interface similar -to the GitHub.dev environment you learned about in +to the VSCode.dev/GitHub environment you learned about in .

Here are a few key differences between -GitHub.dev and Codespaces. +VSCode.dev/GitHub and Codespaces.

  1. -A GitHub.dev URL looks like github.dev/username/reponame, +A VSCode.dev/GitHub URL looks like VSCode.dev/GitHub/username/reponame, while a Codespace URL looks like random-word-123randomcharacters789.github.dev.

  2. -GitHub.dev is quicker to load than a Codespace. +VSCode.dev/GitHub is quicker to load than a Codespace.

  3. -GitHub.dev has a much more limited selection of VS Code +VSCode.dev/GitHub has a much more limited selection of VS Code extensions to use.

    4. @@ -69,7 +69,7 @@ You can only install applications and execute code on a Codespace.

    -One similarity between GitHub.dev and Codespaces +One similarity between VSCode.dev/GitHub and Codespaces (besides the obviously similar VS Code user interfaces), is that your work is still private to you and can only be shared with the public (and retained in the long term) by @@ -310,7 +310,7 @@ your Codespace will be retained before it is deleted

    Putting it all together, we have seen three ways to access files on your repo. Going from the least easy to edit to the most editable we have: GitHub.com, -GitHub.dev, random-codespace-string.github.dev. +VSCode.dev/GitHub, random-codespace-string.github.dev. Here is what these environments look like.

    diff --git a/source/ch-collaboration.ptx b/source/ch-collaboration.ptx index dbf5e2b..1f336bb 100644 --- a/source/ch-collaboration.ptx +++ b/source/ch-collaboration.ptx @@ -28,7 +28,7 @@ need their own GitHub account, and must accept the invitation to collaborate before gaining access.

    -Once they have access, a collaborator can either use GitHub.dev +Once they have access, a collaborator can either use VSCode.dev/GitHub () or create their own Codespace ().

    @@ -53,7 +53,7 @@ repository is to never directly commit to the main branch, even if you're the owner.

    -To commit to an alternative branch in GitHub.dev or Codespaces, select +To commit to an alternative branch in VSCode.dev/GitHub or Codespaces, select main in the bottom toolbar, then type the name of your new branch, and select Create new branch. It's a good idea to name your branch in the form UserName/short-description-of-topic, @@ -90,7 +90,7 @@ or ready to review.

    -Depending on whether the collaborator is using GitHub.dev or +Depending on whether the collaborator is using VSCode.dev/GitHub or Codespaces, they may be prompted to create a pull request when first pushing/syncing changes. If not, a pull request can be created by navigating to the repository page on GitHub.com. @@ -176,7 +176,7 @@ is a quick-enough fix nonetheless.

    This fix must be done in a Codespace, - not GitHub.dev. + not VSCode.dev/GitHub.

    diff --git a/source/ch-first-repo.ptx b/source/ch-first-repo.ptx index f4fda09..52d4293 100644 --- a/source/ch-first-repo.ptx +++ b/source/ch-first-repo.ptx @@ -126,7 +126,7 @@ down the line.

- Using <c>GitHub.dev</c> + Using <c>VSCode.dev/GitHub</c>

Using the GitHub.com interface to author or edit just one file can be useful (I do this all the time to make quick typo fixes on @@ -137,7 +137,7 @@ that you need to include in your work as well.

One way to quickly be able to manage several files at once is -to use the GitHub.dev service +to use the VSCode.dev/GitHub service offered by GitHub. Try clicking that link - you should have a fully-functional VS Code text editor right inside your web browser.

@@ -146,23 +146,24 @@ fully-functional VS Code text editor right inside your web browser. It's best to use an updated version of Chrome, Edge, or Firefox when using GitHub. In particular, Safari tends to show off its rough edges when using advanced web applications like -GitHub.dev, so it's best to choose an alternative. +VSCode.dev/GitHub, so it's best to choose an alternative.

You can create files, edit them, upload images, and do whatever you -like at GitHub.dev. But this isn't your repository - it's just an -example. So, we'll need a way to tell GitHub.dev we want to work on +like at VSCode.dev/GitHub. But this isn't your repository - it's just an +example. So, we'll need a way to tell VSCode.dev/GitHub we want to work on the repository we just made instead.

-There are two very easy ways to access the GitHub.dev service. +There are two very easy ways to access the VSCode.dev/GitHub service. The first is to just change the address of your repository from GitHub.com to -GitHub.dev in your browser. For example, if your repository lives at +VSCode.dev/GitHub in your browser. For example, if your repository lives at https://github.com/YourUserName/YourGreatRepo, you should visit -https://github.dev/YourUserName/YourGreatRepo. +https://VSCode.dev/GitHub/YourUserName/YourGreatRepo (or just +https://github.dev/YourUserName/YourGreatRepo for short).

The other trick is even fancier. When you are visiting @@ -171,12 +172,12 @@ and not writing in a text box, press the period (.) key.

-Either way, you should now have a GitHub.dev window where you can manage +Either way, you should now have a VSCode.dev/GitHub window where you can manage all the files of your project. Using the Explorer sidebar (), you can create new files, rename files, move files, upload files, and more. Selecting a file opens it, and lets you edit it as needed. Your changes are saved -automatically in GitHub.dev, but they won't show up at GitHub.com just yet. +automatically in VSCode.dev/GitHub, but they won't show up at GitHub.com just yet.

@@ -204,13 +205,13 @@ you can easily see where exactly a change is made between each commit.)

The idea is this: edit as you see fit, knowing that your files are being -saved at GitHub.dev and won't be lost if you accidentally refresh your +saved at VSCode.dev/GitHub and won't be lost if you accidentally refresh your web browser. However, you'll need to eventually commit those changes to the repository in order to share your work with anyone else, and to ensure that the work is preserved in the long term. The Source Control panel provides a place to write a commit message, a short phrase or sentence that summarizes the work you've done. (Writer's block? -For now just type learning GitHub.dev.) Then once you click +For now just type learning VSCode.dev/GitHub.) Then once you click the Commit and Push button, your work will be logged as a permanent commit to the repository.

@@ -218,7 +219,7 @@ commit to the repository. This is a good point to review your commit history again. You probably have three commits: the initial commit made when you created the repository, the README.md update you made using GitHub.com's editing interface, -and this more elaborate GitHub.dev commit involving possibly several files. +and this more elaborate VSCode.dev/GitHub commit involving possibly several files. To visualize this history, you can go to the Insights/Network page described earlier, or click on the 3 commits link from your GitHub.com repository diff --git a/source/ch-website.ptx b/source/ch-website.ptx index b064ee2..eceb956 100644 --- a/source/ch-website.ptx +++ b/source/ch-website.ptx @@ -18,7 +18,7 @@ to to create a portfolio website without using HTML.)

-Use GitHub.dev () +Use VSCode.dev/GitHub () to create three files in the root of a new or existing repository.

  • @@ -47,7 +47,7 @@ section, but for now add the following content: Download git-branches.png (used for ) -and upload it to GitHub.dev. +and upload it to VSCode.dev/GitHub.

@@ -94,7 +94,7 @@ or private.

  • -GitHub.dev is where you can make changes to your repository +VSCode.dev/GitHub is where you can make changes to your repository through your web browser. This is private to you and you must commit and push your changes to the GitHub.com repository every so often. (See also .) @@ -223,7 +223,7 @@ an orange dot (in progress), a green checkmark Now that you have the template website hosted by GitHub Pages, you of course will want to customize it to yourself. For this book, I'll get you started by handling a few of the obvious first steps, assuming you're -using the GitHub.dev service (). +using the VSCode.dev/GitHub service ().

    @@ -374,7 +374,7 @@ your changes ().

    -Personally, I use GitHub.dev (or even just the +Personally, I use VSCode.dev/GitHub (or even just the GitHub.com edit button) rather than a full Codespace when adding a quick post or making a quick edit on many of my GitHub Pages websites. But the Codespace option is very