{"id":25707880,"url":"https://github.com/corinnekost/goan","last_synced_at":"2026-05-13T13:33:00.438Z","repository":{"id":273953987,"uuid":"920888962","full_name":"corinnekost/goan","owner":"corinnekost","description":"Repository to learn Git","archived":false,"fork":false,"pushed_at":"2025-01-23T23:58:42.000Z","size":0,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":1,"default_branch":"main","last_synced_at":"2025-01-24T00:25:57.589Z","etag":null,"topics":["git","github"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/corinnekost.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-01-23T00:14:38.000Z","updated_at":"2025-01-24T00:25:21.000Z","dependencies_parsed_at":"2025-01-24T00:36:04.537Z","dependency_job_id":null,"html_url":"https://github.com/corinnekost/goan","commit_stats":null,"previous_names":["corinnekost/goan"],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/corinnekost%2Fgoan","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/corinnekost%2Fgoan/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/corinnekost%2Fgoan/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/corinnekost%2Fgoan/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/corinnekost","download_url":"https://codeload.github.com/corinnekost/goan/tar.gz/refs/heads/main","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":240636643,"owners_count":19832922,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["git","github"],"created_at":"2025-02-25T08:54:45.414Z","updated_at":"2026-05-13T13:33:00.408Z","avatar_url":"https://github.com/corinnekost.png","language":null,"funding_links":[],"categories":[],"sub_categories":[],"readme":"- Check if Git is installed on your computer\n\t- `git --version`\n\n# Repositories\n## GitHub\n- What's the difference between Git and GitHub?\n\t- Git is the tool that allows software engineers to track changes\n\t- GitHub is the website that hosts Git repositories\n\t- You can use Git without GitHub, but you cannot use GitHub without Git\n- Code is stored in **repositories** (repos) on GitHub, which are like folders for your code files and resources\n##  Git Commands\n## Using Git\n- You have a repository on GitHub\n- Now we will push our code to the **remote repository**\n- It's empty right now, so let's work on adding some code\n## Git Init\n- `git init` initializes a new Git repository\n- First command you run when you have a new project and want to **start tracking changes**\n- When you run this command, Git will create a new directory named .git in your project folder\n\t- This directory contains all the information about your project's history and configuration\n\t- The terminal will output the following once completed successfully:\n\t\t- `Initialized empty Git repository in /Users/username/.git`\n## Git Remote\n- Now we need to connect our local repository (folder on computer) with our remote repository (the link on GitHub)\n- We can use `remote add` to connect our local and remote repositories\n\t- `git remote add origin \u003crepository_url\u003e`\n## Git Branch\n- Let's rename the branch to `main`\n- This will be the branch we *push code to* and will be default branch\n\t- `git branch -M main`\n## Instructions\n- Navigate to your project folder or directory on your computer\n\t- This can be any .py, .html, .css, .js file\n- Open your selected folder in a code editor of your choice\n- Open a terminal or command prompt\n\t- In VS Code, you can open the terminal with `CTRL + '`' or go to Terminal \u003e New Terminal\n- Once here, we're ready to connect our code on our device to our GitHub repo\n- Before we begin, we want to make sure that your terminal is in the correct place to initialize the repository\n\t- `pwd`\n- Next, create a connection between the file in our machine and the GitHub repo by linking them with the `git init`, `git remote add`, and `git branch` commands\n- To check we have successfully connected our local and remote repositories and renamed the branch, run the following command:\n```\ngit branch\n// Output:\n// * main\n```\n- If you see `main` in the output you're all set\n\n# Git Workflow\n## Working Directory\n- The **working directory** is where you have the files and folders on your computer that you're actively working on or changing\n- When you make changes to your files, Git will track these changes and allow you to move them to the staging area\n## Staging Area / Index\n- The **staging area** is a status of files and folders within your project that tells Git \"Hey, I'm getting ready to go online\"\n- Temporary area where you pick and choose what files you want to \"commit\" or send to the remote repository\n- Using the `git add` command allows us to do so; variation examples:\n\t- `git add example.txt` will add the single file to the staging area\n\t\t- If you only want one of your working files to show up on GitHub rather than the rest of your project, consider specifying a specific file\n\t- `git add .` will add **all** the changed files to the staging area\n\t\t- This means that any new file added or changed to the working directory will be included\n\t- `git add *.html` will only stage files with a specified extension\n\t\t- In this example, this command will only add **.html** files\n## Committed Files\n- Committing files are about sharing the current code as a \"snapshot\" that GitHub online has access to\n- Commits help us separate different actions in our code, and allow us to add helpful messages so we know and keep track of changes\n- Typical project commit examples:\n\t- `initial commit` - our first commit\n\t- `add fun pics to header` - developer added a header to their project\n\t- `fixed again fr this time!!!` - developer fixed a bug\n- **Note**: commit messages get silly when you're working on your own for a while, but short, clear, and descriptive messages are needed when working on a team\n- We want messages to explain what we're doing to the code so other devs can know what was worked on at a glance\n- Commit your staged files:\n\t- `git commit -m 'Your commit message here!'`\n## Instructions\n- Go back to your terminal or command prompt, and navigate to your project folder\n- Use `git add .` to commit all the files in your project folder to the staging area\n- Then use `git commit -m 'Initial Commit'` to write your first commit message\n\n# Local Push\n## Git Status\n- The `git status` command is used to check the status of your files\n- It is a handy command that will show you which files are staged, unstaged, and untracked\n\t- **Staged** files are ready to be committed\n\t- **Unstaged** files are not yet ready to be committed\n\t- **Untracked** files are new files that Git has not seen before\n- Check the status of your files: \n\t- `git status`\n## Git Push\n- The `git push` command is used to send your locally committed changes to your remote repository\n- You'll see all the changes you've made on GitHub\n- The very first time you push to a branch, the command usually looks like this:\n\t- `git push -u origin main`\n\t\t- This links your local branch to the remote branch so that the future push commands will automatically apply to this branch without needing to specify it each time\n- Once that's set, any commits you push to this branch will just require `git push`\n- When that's done, you'll be able to refresh your GitHub repository URl, and see your changes online\n## Instructions\n- Using the command from this lesson, push your code to GitHub\n- Check to make sure this was successful by refreshing the page\n# README\n## Review\n- Create a new repository on local machine\n\t- `git init`\n- Connecting our local repository to GitHub\n\t- `git remote add origin https://github.com/corinnekost/goan.git`\n- Rename a branch to main\n\t- `git branch -M main`\n- Stage and commit changes\n\t- `git add .`\n\t- `git commit -m \"initial commit\"`\n- Check the status of our files\n\t- `git status`\n- Push code to GitHub\n\t- `git push -u origin main`\n## Instructions\n- Create a new file in your project folder called README.md\n- Open the file in your code editor and add some text to describe your repository\n- Save the file and commit it to your local repository\n- Push the changes to GitHub\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcorinnekost%2Fgoan","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcorinnekost%2Fgoan","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcorinnekost%2Fgoan/lists"}