7
I am struggling with my lesson. I have no professor to help me wade through. It's learning how to begin with Git. (nord.pub)
submitted 4 months ago by to c/askbeehaw@beehaw.org
11 comments fedilink hide all child comments
 

https://www.theodinproject.com/lessons/foundations-git-basics this is the lesson that i am following. I completed the Create the Repository section successfully. I also completed the Use the Git Workflow section successfully. It’s the Modify a File or two where I am facing all the difficulties.

Can someone please show me the way how to do it ?

you are viewing a single comment's thread
view the rest of the comments
[–] [S] 3 points 4 months ago* (3 children)

I have done everything till we come to modify a file or two. I did everything in my WSL terminal. Then it's being said over here we will open the directory (which directory) in visual studio code by using the command inside my repository (which repository and where is it located?) These are the questions l need to figure out.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 4 months ago* (last edited 4 months ago) (2 children)

    WSL might make things a bit more complicated to understand at first, so that's fair.

    What do you see if you type pwd into the terminal where you are working? What about ls? You can redact any personal info before pasting it in (ex. if your name is included in a file path).

    • pwd will output the current directory, which can help you track down the right folder to open in VSCode
    • ls will output a list of all files in the current directory. If you see weird looking entries like . or .., don't worry about those (I'm happy to explain, but for now it's not important)

    Usually when you are working on something, you would put all the files related to that project in a folder. That highest level folder is the one that you open in VScode, since you will be able to see all the subfolders easily. For example, my folders might look like this

    |- My Documents
|   |-repos
|   |   |-My New Website
|   |   | 
|   |   |-My app
|   |

    In VSCode, you would open the "My New Website" folder when you are working on that project. In your case, you likely need to open whatever folder comes up from the output of pwd, or one of the subfolders (if that one shows "/.../.../repos". If your terminal supports it, you might also be able to open the current folder in vscode with a command like code ., or in the file explorer with open .

    If you have a messy setup, I would recommend learning some basic CLI commands for navigating your terminal first. That will help a lot for figuring out what is happening. Afterwards, you can easily navigate to the folder with all of your Odin Project files via. the terminal.

    As for the repository, usually the repository is created from the root (the highest level) of whatever project you are working on. So if I cloned a repository called otter/my-new-website, the repository is tied to the folder my-new-website.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 2 points 4 months ago (1 child)

    This comes up as i type pwd and ls 0GUqMg5xC02whd5.png

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 4 months ago

    Hmm, yea WSL doesn't make it clear.

    So I think WSL sets up an artificial Linux directory system somewhere inside of Windows. In your case, it might be at \\wsl$\ubuntu\home\hpdeb if you want to hunt around for that on Windows File explorer. (source: https://superuser.com/questions/1185033/what-is-the-home-directory-on-windows-subsystem-for-linux) Afterwards, you can try and open that same folder in VS Code, once you know where it is.

    If none of that works, I also see that there is an extension for VS Code that makes it easier to connect to WSL. You might be better off by installing that extension to get things connected more easily. Supposedly after it is set up, you will be able to run code . in your terminal to open the current directory in VS Code: https://code.visualstudio.com/docs/remote/wsl-tutorial

    note: Don't install VS Code a second time inside of WSL, that would be a pain to work with. Instead, this tool should take advantage of VS Code's ability to connect to a remote server, and instead get it to "connect" to your local WSL file system.

  • permalink
  • fedilink
  • source
  • parent