Trouble getting GitHub to connect with VSCode and my Excursion homework

I have my Excursion app page built ok, but can’t seem to make it show on https://goddesslinda.github.io/excursion Am 22% through FSE

how do I get my best version uploaded so you can see it? I am on a MacAir. thanks… love, Linda

If you want to have the best chances of getting a useful answer quickly, make sure you follow our guidelines about how to ask a good question. That way you’ll be helping everyone – helping people to answer your question and helping others who are stuck to find the question and answer! :slight_smile:

Hi @lindajoyfulcoder, I found my repos weren’t automatically deploying so to deploy each repo I had to go to that repo in github, click settings, then pages, then add that repo to the main branch (repeating the steps I did to deploy .github.io). After that the specific repo was deployed.

Did I write this clearly?

I have yet to give this a try… will get back to you soon. Am 26% thru FSE course! :innocent:

Your question doesn’t go into much detail, so let’s get some clarification:

  • Are you using VSCode or VSCode-insiders? Is it up to date?
  • Do you have the GitHub extension installed in VSCode? What other extensions are installed/enabled?
  • Since this is a github.io site, are you using a template like minimal-mistakes, or is everything hand-made by you?
  • Have you tried running a local server to view the page from your computer’s version to ensure it works properly? Are there any build errors or other warnings that pop up?
  • Assuming you have your GitHub repo set up properly, VSCode set up properly, and Git is working correctly, are you remembering the stage-commit-push workflow for your changes?

Sounds good, at 21% :slight_smile:

1 Like

am using VSCode. Now downloading update. Will get to other bullet points soon.

  • Just updated VSCode to v 1.59

  • Just Got GitHub pull request — Microsoft endorsed, I understand it’s not perfect

have Babel JavaScript, ESLint, HTML/CSS support, JavaScript ES6 code snippets, npm, and Prettier, Oceanic Next Theme, and VSCode Codeception

I basically coded it by hand in VSCode…. Linda Codecademy Student … well this is weird, but it works…

don’t know how to use a “local computer server” yet

I don’t yet have confidence in my STAGE-COMMIT-PUSH workflow…. I am a beginner at GitHub

Lindajoyfulcoder , Codecademy FSE student; now 26% through!

thank you, nothead … I am making progress not perfection… good night!

Michael, I will give your solution a try and see if it works for me. Will report back on progress.

Well, it appears that you have successfully pushed a working commit to your repo, since the link you provided does show up. That’s the biggest hurdle.

A few things that might help you get more familiar with GitHub, though, because it is very confusing when you are first learning git. This isn’t criticism or anything, I’m just sharing what my experience was and the things I found to be helpful when I was learning:

  • git and GitHub are two separate things. Understanding this was the biggest help for me, because I would always be looking at my problem as “how do I do this in GitHub”, and now when I have a problem, I rethink my question as “is this a problem with the git tool, or is it a problem with the GitHub website?”

  • VSCode has some very useful built-in extensions for using git. I will make a blog post on my website (nothead31.github.io) that gives an in-depth tutorial that you can look at, check it out later this week. For now, just keep in mind that you can use the VSCode console by pressing F1, and you can type commands like “stage” or “commit” and see what commands are available. I rarely use the git command line for regular work, I just use the “stage all” command, then “commit” and finally “push” my changes to the repo. This makes the process much easier, but also means that sometimes I forget to stage a file and have to make multiple commits. There are advanced solutions to that problem, but worry about the basics first.

  • Another important distinction that helped me was understanding that the workflow is split between “buckets” and “spouts” that flow into each other. Your working folder is the bucket you touch directly. You edit files, save them, make changes, etc. Staging opens a spout in that bucket and pours everything into the “staged” bucket, which continues to collect everything until the “Commit” spout opens and pours everything into the “commit” bucket. Then all those commits sit together until the “push” bucket opens, and they all pour into the “complete” bucket, where they now sit on the GitHub repo, or other remote location.

  • Finally, for the local server, it depends on how you develop your website. If you use strictly JS/HTML/CSS, then you could experiment with this VSCode extension. I have never used it, so I don’t vouch for whether it works, but you can also find other similar ones, too. The advantage of having a local server like this is that you can make your changes and see what the impact will be without having to stage/commit/push every change. I have Python installed on my system, and you actually have a python feature similar to this with “python -m http-server”. I use it to test my github.io site, even though the website project has no python code and it still works. There are also additional extensions like brackets 2, and others. I like spending some time every month just browsing the VS Code marketplace to see what’s new.

1 Like

that buckets and spouts discussion is very elucidating! I certainly haven’t yet mastered the basics of Git and GitHub. To me, it’s all “rocket-science”. :grin: