├── .freeCodeCamp ├── .bashrc └── test │ ├── .cwd │ └── .next_command ├── .gitignore ├── .gitpod.yml ├── .vscode └── settings.json ├── CHANGELOG.md ├── TUTORIAL.md ├── coderoad.yaml └── tutorial.json /.freeCodeCamp/.bashrc: -------------------------------------------------------------------------------- 1 | # ~/.bashrc: executed by bash(1) for non-login shells. 2 | # see /usr/share/doc/bash/examples/startup-files (in the package bash-doc) 3 | # for examples 4 | 5 | # If not running interactively, don't do anything 6 | case $- in 7 | *i*) ;; 8 | *) return;; 9 | esac 10 | 11 | # don't put duplicate lines or lines starting with space in the history. 12 | # See bash(1) for more options 13 | # I commented this out 14 | #HISTCONTROL=ignoreboth 15 | 16 | # append to the history file, don't overwrite it 17 | shopt -s histappend 18 | 19 | # for setting history length see HISTSIZE and HISTFILESIZE in bash(1) 20 | HISTSIZE=1000 21 | HISTFILESIZE=2000 22 | 23 | # check the window size after each command and, if necessary, 24 | # update the values of LINES and COLUMNS. 25 | shopt -s checkwinsize 26 | 27 | # If set, the pattern "**" used in a pathname expansion context will 28 | # match all files and zero or more directories and subdirectories. 29 | #shopt -s globstar 30 | 31 | # make less more friendly for non-text input files, see lesspipe(1) 32 | # I commented this out 33 | #[ -x /usr/bin/lesspipe ] && eval "$(SHELL=/bin/sh lesspipe)" 34 | 35 | # set variable identifying the chroot you work in (used in the prompt below) 36 | if [ -z "${debian_chroot:-}" ] && [ -r /etc/debian_chroot ]; then 37 | debian_chroot=$(cat /etc/debian_chroot) 38 | fi 39 | 40 | # set a fancy prompt (non-color, unless we know we "want" color) 41 | case "$TERM" in 42 | xterm-color|*-256color) color_prompt=yes;; 43 | esac 44 | 45 | # uncomment for a colored prompt, if the terminal has the capability; turned 46 | # off by default to not distract the user: the focus in a terminal window 47 | # should be on the output of commands, not on the prompt 48 | #force_color_prompt=yes 49 | 50 | if [ -n "$force_color_prompt" ]; then 51 | if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then 52 | # We have color support; assume it's compliant with Ecma-48 53 | # (ISO/IEC-6429). (Lack of such support is extremely rare, and such 54 | # a case would tend to support setf rather than setaf.) 55 | color_prompt=yes 56 | else 57 | color_prompt= 58 | fi 59 | fi 60 | 61 | if [ "$color_prompt" = yes ]; then 62 | PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ ' 63 | else 64 | PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w\$ ' 65 | fi 66 | unset color_prompt force_color_prompt 67 | 68 | # If this is an xterm set the title to user@host:dir 69 | case "$TERM" in 70 | xterm*|rxvt*) 71 | PS1="\[\e]0;${debian_chroot:+($debian_chroot)}\u@\h: \w\a\]$PS1" 72 | ;; 73 | *) 74 | ;; 75 | esac 76 | 77 | # enable color support of ls and also add handy aliases 78 | if [ -x /usr/bin/dircolors ]; then 79 | test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)" 80 | alias ls='ls --color=auto' 81 | #alias dir='dir --color=auto' 82 | #alias vdir='vdir --color=auto' 83 | 84 | # I commented these out 85 | # alias grep='grep --color=auto' 86 | # alias fgrep='fgrep --color=auto' 87 | # alias egrep='egrep --color=auto' 88 | fi 89 | 90 | # colored GCC warnings and errors 91 | #export GCC_COLORS='error=01;31:warning=01;35:note=01;36:caret=01;32:locus=01:quote=01' 92 | 93 | # some more ls aliases - # I commented these out 94 | # alias ll='ls -alF' 95 | # alias la='ls -A' 96 | # alias l='ls -CF' 97 | 98 | # Add an "alert" alias for long running commands. Use like so: 99 | # sleep 10; alert 100 | # I commented this out 101 | #alias alert='notify-send --urgency=low -i "$([ $? = 0 ] && echo terminal || echo error)" "$(history|tail -n1|sed -e '\''s/^\s*[0-9]\+\s*//;s/[;&|]\s*alert$//'\'')"' 102 | 103 | # Alias definitions. 104 | # You may want to put all your additions into a separate file like 105 | # ~/.bash_aliases, instead of adding them here directly. 106 | # See /usr/share/doc/bash-doc/examples in the bash-doc package. 107 | 108 | if [ -f ~/.bash_aliases ]; then 109 | . ~/.bash_aliases 110 | fi 111 | 112 | # enable programmable completion features (you don't need to enable 113 | # this, if it's already enabled in /etc/bash.bashrc and /etc/profile 114 | # sources /etc/bash.bashrc). 115 | if ! shopt -oq posix; then 116 | if [ -f /usr/share/bash-completion/bash_completion ]; then 117 | . /usr/share/bash-completion/bash_completion 118 | elif [ -f /etc/bash_completion ]; then 119 | . /etc/bash_completion 120 | fi 121 | fi 122 | 123 | # I commented this out 124 | #for i in $(ls -A $HOME/.bashrc.d/); do source $HOME/.bashrc.d/$i; done 125 | 126 | # Add RVM to PATH for scripting. Make sure this is the last PATH variable change. 127 | export PATH="$PATH:$HOME/.rvm/bin" 128 | 129 | # stuff I added 130 | PS1='camper: \[\033[01;34m\]/${PWD##*/}\[\033[00m\]\$ ' 131 | HISTFILE=/workspace/.bash_history 132 | PROMPT_COMMAND='echo $PWD >> /workspace/project/.freeCodeCamp/test/.cwd; history -a' 133 | trap 'echo $BASH_COMMAND >> /workspace/project/.freeCodeCamp/test/.next_command' DEBUG -------------------------------------------------------------------------------- /.freeCodeCamp/test/.cwd: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/freeCodeCamp/learn-git-by-building-an-sql-reference-object/d835a0f8cf8d0392a2f6687bc14be12e2bd66ef6/.freeCodeCamp/test/.cwd -------------------------------------------------------------------------------- /.freeCodeCamp/test/.next_command: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/freeCodeCamp/learn-git-by-building-an-sql-reference-object/d835a0f8cf8d0392a2f6687bc14be12e2bd66ef6/.freeCodeCamp/test/.next_command -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | node_modules 2 | .DS_Store 3 | -------------------------------------------------------------------------------- /.gitpod.yml: -------------------------------------------------------------------------------- 1 | image: gitpod/workspace-node-18:2024-01-24-09-19-42 2 | 3 | workspaceLocation: 'project' 4 | checkoutLocation: 'project' 5 | 6 | tasks: 7 | - before: | 8 | sudo touch /workspace/.bash_history 9 | sudo chmod -R 777 /workspace 10 | sudo cp /workspace/project/.freeCodeCamp/.bashrc ~/.bashrc 11 | echo -e '\nexport GIT_EDITOR=/usr/bin/nano' >> $HOME/.bashrc 12 | 13 | command: | 14 | sudo rm /workspace/project/CHANGELOG.md 15 | sudo rm /workspace/project/coderoad.yaml 16 | sudo rm /workspace/project/tutorial.json 17 | sudo rm /workspace/project/TUTORIAL.md 18 | exit 19 | 20 | vscode: 21 | extensions: 22 | - CodeRoad.coderoad 23 | -------------------------------------------------------------------------------- /.vscode/settings.json: -------------------------------------------------------------------------------- 1 | { 2 | "breadcrumbs.enabled": false, 3 | "debug.internalConsoleOptions": "neverOpen", 4 | "debug.showInStatusBar": "never", 5 | "editor.acceptSuggestionOnCommitCharacter": false, 6 | "editor.acceptSuggestionOnEnter": "off", 7 | "editor.autoClosingBrackets": "never", 8 | "editor.codeActionsOnSave": { 9 | "source.fixAll": "explicit" 10 | }, 11 | "editor.hover.enabled": false, 12 | "editor.inlineSuggest.enabled": false, 13 | "editor.minimap.enabled": false, 14 | "editor.parameterHints.enabled": false, 15 | "editor.quickSuggestions": { 16 | "other": false, 17 | "comments": false, 18 | "strings": false 19 | }, 20 | "editor.referenceInfos": false, 21 | "editor.snippetSuggestions": "none", 22 | "editor.suggest.statusBar.visible": false, 23 | "editor.suggestOnTriggerCharacters": false, 24 | "editor.tabSize": 2, 25 | "explorer.autoReveal": false, 26 | "explorer.openEditors.visible": 0, 27 | "extensions.autoCheckUpdates": false, 28 | "extensions.ignoreRecommendations": true, 29 | "files.autoSave": "afterDelay", 30 | "files.exclude": { 31 | "**/.git": true, 32 | "**/.svn": true, 33 | "**/.hg": true, 34 | "**/CVS": true, 35 | "**/.DS_Store": true, 36 | ".vscode": true, 37 | ".gitignore": true, 38 | ".freeCodeCamp": true, 39 | "learn-git-by-building-an-sql-reference-object": true, 40 | ".gitpod.Dockerfile": true, 41 | ".gitpod.yml": true, 42 | "CHANGELOG.md": true, 43 | "coderoad.yaml": true, 44 | "tutorial.json": true, 45 | "TUTORIAL.md": true 46 | }, 47 | "html.autoClosingTags": false, 48 | "npm.fetchOnlinePackageInfo": false, 49 | "task.slowProviderWarning": false, 50 | "terminal.integrated.allowChords": false, 51 | "terminal.integrated.commandsToSkipShell": ["coderoad.enter"], 52 | "terminal.integrated.enableFileLinks": false, 53 | "terminal.integrated.environmentChangesIndicator": "off", 54 | "terminal.integrated.macOptionIsMeta": true, 55 | "terminal.integrated.showExitAlert": false, 56 | "telemetry.enableTelemetry": false, 57 | "update.mode": "none", 58 | "update.showReleaseNotes": false, 59 | "workbench.enableExperiments": false, 60 | "workbench.startupEditor": "none", 61 | "workbench.colorTheme": "Tomorrow Night Blue", 62 | "workbench.colorCustomizations": { 63 | "[Tomorrow Night Blue]": { 64 | "menu.background": "#0a0a23", 65 | "menu.foreground": "#ffffff", 66 | "activityBar.background": "#0a0a23", 67 | "activityBar.foreground": "#ffffff", 68 | "activityBar.activeBorder": "#ffffff", 69 | "activityBar.border": "#2a2a40", 70 | "editorWidget.background": "#0a0a23", 71 | "editorWidget.foreground": "#ffffff", 72 | "sideBar.background": "#1b1b32", 73 | "sideBarTitle.foreground": "#858591", 74 | "sideBar.foreground": "#f5f6f7", 75 | "sideBar.border": "#2a2a40", 76 | "editor.background": "#2a2a40", 77 | "editor.foreground": "#dfdfe2", 78 | "tab.activeForeground": "#ffffff", 79 | "tab.inactiveBackground": "#1b1b32", 80 | "tab.inactiveForeground": "#d0d0d5", 81 | "tab.border": "#2a2a40", 82 | "editorGroupHeader.tabsBackground": "#0a0a23", 83 | "editorIndentGuide.background": "#3b3b4f", 84 | "terminal.background": "#0a0a23", 85 | "terminal.foreground": "#ffffff", 86 | "terminal.ansiBrightGreen": "#ffffff", 87 | "panel.background": "#1b1b32", 88 | "panelTitle.inactiveForeground": "#858591", 89 | "panelTitle.activeBorder": "#f5f6f7" 90 | } 91 | }, 92 | "workbench.iconTheme": null, 93 | "workbench.statusBar.visible": false, 94 | "workbench.tips.enabled": false, 95 | "workbench.tree.renderIndentGuides": "none", 96 | "zenMode.centerLayout": false 97 | } -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | ## Contributing 2 | 3 | Please read the guidelines in the [contributing docs](https://contribute.freecodecamp.org/#/how-to-work-on-tutorials-that-use-coderoad) before contributing. Contributions to this project need to follow the correct workflow. 4 | 5 | # Change Log 6 | 7 | Whenever a new version is created, add the new branch name and the changes here 8 | 9 | ## [v1.0.0] 10 | 11 | - Initial soft release with news article 12 | 13 | ## [v1.0.1] 14 | 15 | - Add in `.vscode/settings.json` setting to use spaces for indentation 16 | 17 | ## [v1.0.2] 18 | 19 | - Move setup commands from `coderoad.yaml` to `setup.sh` 20 | - Add creation of `.bash_history` in setup commands so CodeRoad watchers recognize it when the first command is entered 21 | 22 | ## [v1.0.3] 23 | 24 | - Fix reset commands so it works everywhere 25 | 26 | ## [v1.0.4] 27 | 28 | - Further improve reset command so it doesn't delete and recreate the `sql_reference` folder when resetting 29 | 30 | ## [v1.0.5] 31 | 32 | - Restructure commits to use new style. Instead of loading a new test file, and commenting out the old one on each commit, this loads all the tests in the `INIT` commit and uses mocha settings to only run tests in a specific file. The commits now just change the test file that should run. 33 | - There was an issue with the last commit not loading after using the reset button in a tutorial. I added a final commit at end that seems to have resolved it. 34 | - Add `exit` flag to mocha so the tests can't hang 35 | 36 | ## [v2.0.0] 37 | 38 | - Add Gitpod config 39 | -------------------------------------------------------------------------------- /TUTORIAL.md: -------------------------------------------------------------------------------- 1 | # Learn Git by Building an SQL Reference Object 2 | 3 | > Welcome to the git lessons! 4 | 5 | ## 10. Start Terminal 6 | 7 | ### 10.1 8 | 9 | The first thing you need to do is start the terminal. Open a new one by clicking the "hamburger" menu at the top left of the window, going to the "terminal" section, and clicking "new terminal". Once you open a new one, type `echo hello git` into the terminal and press enter. 10 | 11 | #### HINTS 12 | 13 | - Follow the directions closely 14 | - If the tests don't pass, trash all the terminals with the trash can icon at the top right of the terminal. Then, redo those instructions 15 | 16 | ## 20. Make Directory 17 | 18 | ### 20.1 19 | 20 | You should be in the `project` folder in the terminal you opened. Use the terminal to make a new directory named `sql_reference` in the `project` folder. As a reminder, you can use the `mkdir` command to make a new folder. 21 | 22 | #### HINTS 23 | 24 | - Enter `mkdir sql_reference` in the terminal from the `project` folder 25 | - Enter `cd ~/project` to get to the `project` folder if you aren't there 26 | - Don't try to create the folder with another method 27 | 28 | ## 30. Change Directory 29 | 30 | ### 30.1 31 | 32 | Use the "change directory" command in the terminal to change to your new folder. 33 | 34 | #### HINTS 35 | 36 | - Enter `cd sql_reference` into the terminal 37 | - Make sure you are in the `project` folder first 38 | - Enter `cd ~/project` to get to the `project` folder if you aren't there 39 | 40 | ## 40. Initialize a git Repository 41 | 42 | ### 40.1 43 | 44 | Git is a version control system to keep track of your code. This folder will be your git repository. Turn it into one by typing `git init` in the terminal from this folder. 45 | 46 | #### HINTS 47 | 48 | - Enter `git init` into the terminal while in the `sql_reference` folder 49 | - Make sure you are in the `sql_reference` folder first 50 | - Enter `cd ~/project/sql_reference` to get to the folder if you aren't there 51 | 52 | ## 50. View .git Folder 53 | 54 | ### 50.1 55 | 56 | Use the list command with the `-a` flag to list the hidden folders and files. 57 | 58 | #### HINTS 59 | 60 | - The list command is `ls` 61 | - Type `ls -a` into the terminal and press enter 62 | - Make sure you are in the `sql_reference` folder first 63 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 64 | 65 | ## 60. git status 66 | 67 | ### 60.1 68 | 69 | The `git init` command created that `.git` folder for you. It's what keeps track of all the things in your repository. Use `git status` to see the status of where you are. This command will be your best friend. 70 | 71 | #### HINTS 72 | 73 | - Type `git status` into the terminal and press enter 74 | - Make sure you are in the `sql_reference` folder first 75 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 76 | 77 | ## 70. Checkout main Branch 78 | 79 | ### 70.1 80 | 81 | A git repository has branches to help keep track of things you are doing with your code. It's common to have a `main` branch which might be for your production code, and other branches for adding new features or fixing bugs. You can create and go to a new branch with `git checkout -b new_branch`. The `-b` stands for "branch". Use that command to switch to a new branch named `main`. 82 | 83 | #### HINTS 84 | 85 | - Capitalization matters 86 | - Type `git checkout -b main` into the terminal 87 | - Make sure you are in your `sql-reference` repo folder 88 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 89 | 90 | ## 80. git status 91 | 92 | ### 80.1 93 | 94 | Check your status again with `git status`. 95 | 96 | #### HINTS 97 | 98 | - Type `git status` into the terminal and press enter 99 | - Make sure you are in your `sql_reference` repo folder 100 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 101 | 102 | ## 90. touch README.md 103 | 104 | ### 90.1 105 | 106 | Now you are on the `main` branch. Use the `touch` command to create `README.md` inside your repository. This is a file you will see in many repos to describe what the repo is for. 107 | 108 | #### HINTS 109 | 110 | - Use `touch file_name` to create a file 111 | - Type `touch README.md` into the terminal and press enter 112 | - Don't try to create the file with another method 113 | - Make sure you are in your `sql_reference` repo folder 114 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 115 | 116 | ## 100. Add Readme Text 117 | 118 | ### 100.1 119 | 120 | Add the text `SQL Reference` at the top of your new file to let people know what your repo is for. 121 | 122 | #### HINTS 123 | 124 | - Add the suggested text in your `README.md` file 125 | 126 | ## 110. git status 127 | 128 | ### 110.1 129 | 130 | Check the status of your repo again. 131 | 132 | #### HINTS 133 | 134 | - Use the "git status" command in your repo 135 | - Type `git status` into the terminal and press enter 136 | - Make sure you are in your `sql_reference` repo folder 137 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 138 | 139 | ## 120. git add README.md 140 | 141 | ### 120.1 142 | 143 | The file you created has not been added to git yet so it is showing that it is untracked. There's two steps to make git keep track of it for you. First you need to add it to the staging area like this: `git add file_name`. Add your `README.md` file to the staging area. 144 | 145 | #### HINTS 146 | 147 | - Replace `file_name` in the example with your `README.md` file 148 | - Type `git add README.md` into the terminal and press enter 149 | - Make sure you are in your `sql_reference` repo folder 150 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 151 | 152 | ## 130. git status 153 | 154 | ### 130.1 155 | 156 | Check your status again. 157 | 158 | #### HINTS 159 | 160 | - Use the "git status" command in your repo 161 | - Type `git status` into the terminal and press enter 162 | - Make sure you are in your `sql_reference` repo folder 163 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 164 | 165 | ## 140. touch sql_reference.json 166 | 167 | ### 140.1 168 | 169 | Now your file is in staging and will be added with the next commit. You aren't quite ready to commit this yet though. Use `touch` again to create `sql_reference.json` in your repo. 170 | 171 | #### HINTS 172 | 173 | - Use `touch file_name` to create a file 174 | - Type `touch sql_reference.json` into the terminal and press enter 175 | - Don't try to create the file with another method 176 | - Make sure you are in your `sql_reference` repo folder 177 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 178 | 179 | ## 150. git status 180 | 181 | ### 150.1 182 | 183 | Check your status again. 184 | 185 | #### HINTS 186 | 187 | - Use the "git status" command in your repo 188 | - Type `git status` into the terminal and press enter 189 | - Make sure you are in your `sql_reference` repo folder 190 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 191 | 192 | ## 160. git add Initial commit 193 | 194 | ### 160.1 195 | 196 | You now have one file in staging and one that is untracked. Add the new file you created to the staging area. 197 | 198 | #### HINTS 199 | 200 | - Here's the example again: `git add file_name` 201 | - You added the last one with `git add README.md` 202 | - Type `git add sql_reference.json` into the terminal and press enter 203 | - Make sure you are in your `sql_reference` repo folder 204 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 205 | 206 | ## 170. git status 207 | 208 | ### 170.1 209 | 210 | Check your status one more time please :grin: 211 | 212 | #### HINTS 213 | 214 | - Use the "git status" command in your repo 215 | - Type `git status` into the terminal and press enter 216 | - Make sure you are in your `sql_reference` repo folder 217 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 218 | 219 | ## 180. git commit Initial commit 220 | 221 | ### 180.1 222 | 223 | Now you have two files in staging. To commit them, you can use `git commit -m "Initial commit"`. The `-m` stands for "message". Often times, the first commit of a repo will have the message "Initial commit". Commit your two files with the message `Initial commit`. 224 | 225 | #### HINTS 226 | 227 | - Type `git commit -m "Initial commit"` in the terminal and press enter 228 | - Enter `git log` to see if your message is correct 229 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 230 | - Or, reset the lesson and try again 231 | 232 | ## 190. git status 233 | 234 | ### 190.1 235 | 236 | When you make a commit, whatever is in the staging area will be added to your git history. You can see some info in the terminal output about the commit. Check your status again to see what's there. 237 | 238 | #### HINTS 239 | 240 | - Use the "git status" command in your repo 241 | - Type `git status` into the terminal and press enter 242 | - Make sure you are in your `sql_reference` repo folder 243 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 244 | 245 | ## 200. git log 246 | 247 | ### 200.1 248 | 249 | Your "working tree" is clean, the files were committed and there's no other new changes that git recognizes. You can see your commit history with `git log`. Check your commit history. 250 | 251 | #### HINTS 252 | 253 | - Type `git log` into the terminal and press enter 254 | - Make sure you are in your `sql_reference` repo folder 255 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 256 | 257 | ## 210. Add CREATE DATABASE Command 258 | 259 | ### 210.1 260 | 261 | You can see the commit you made. It shows the message you gave with the commit, along with your username, email, the date, and a commit hash. The hash is that long string of characters. Open up your `.json` file and create an object with a reference for how to create a database that looks like this: 262 | 263 | ```json 264 | { 265 | "database": { 266 | "create": "CREATE DATABASE database_name;" 267 | } 268 | } 269 | ``` 270 | 271 | Make sure there's one empty line at the bottom of the file and no extra spaces after the value or any of the curly brackets. 272 | 273 | #### HINTS 274 | 275 | - Add the suggested object to your `sql_reference.json` file 276 | - Double check for those extra spaces and the empty line 277 | 278 | ## 220. git status 279 | 280 | ### 220.1 281 | 282 | Check your status again. 283 | 284 | #### HINTS 285 | 286 | - Use the "git status" command in your repo 287 | - Type `git status` into the terminal and press enter 288 | - Make sure you are in your `sql_reference` repo folder 289 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 290 | 291 | ## 230. git diff 292 | 293 | ### 230.1 294 | 295 | Git recognizes new unstaged changes to your file. Notice that it says that file is modified instead of untracked because the file has been previously committed. You can see the changes you made with `git diff`. Take a look at the new changes. 296 | 297 | #### HINTS 298 | 299 | - Type `git diff` into the terminal and press enter 300 | - Make sure you are in your `sql_reference` repo folder 301 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 302 | 303 | ## 240. git add sql_reference.json 304 | 305 | ### 240.1 306 | 307 | The lines with `+` in front means that those lines were added. Add your new changes to staging with the `git add` command again. Make sure to put the filename you want to add at the end of the command. 308 | 309 | #### HINTS 310 | 311 | - You previously used `git add README.md` to add changes to staging 312 | - Type `git add sql_reference.json` into the terminal and press enter 313 | - Make sure you are in your `sql_reference` repo folder 314 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 315 | 316 | ## 250. git status 317 | 318 | ### 250.1 319 | 320 | Check your status. 321 | 322 | #### HINTS 323 | 324 | - Use the "git status" command in your repo 325 | - Type `git status` into the terminal and press enter 326 | - Make sure you are in your `sql_reference` repo folder 327 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 328 | 329 | ## 260. git commit feat: add create database reference 330 | 331 | ### 260.1 332 | 333 | Your new changes are staged and ready to be committed. Commit them with the message `feat: add create database reference`. As a reminder, here what the command to commit looks like: `git commit -m "message"`. 334 | 335 | #### HINTS 336 | 337 | - Type `git commit -m "feat: add create database reference"` into the terminal and press enter 338 | - View your `git log` to see if your message is correct 339 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 340 | - Or, reset the lesson and try again 341 | - Make sure you are in your `sql_reference` repo folder 342 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 343 | 344 | ## 270. git log 345 | 346 | ### 270.1 347 | 348 | Commit messages often start with `fix:` or `feat:`, among others, to help people understand what your commit was for. Check your `git log` again to see the new commit added. 349 | 350 | #### HINTS 351 | 352 | - Type `git log` into the terminal and press enter 353 | - Make sure you are in your `sql_reference` repo folder 354 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 355 | 356 | ## 280. Add DROP DATABASE command 357 | 358 | ### 280.1 359 | 360 | Now there's two commits in your history, the newest one is at the top :smile: In your JSON file, add a `drop` key to your `database` object. Give it a value for how to drop a database similar to the `create` value. The syntax is in the hints. Again, make sure there's an empty line at the bottom of the file and no extra spaces after any values or curly brackets. 361 | 362 | #### HINTS 363 | 364 | - The value should be `"DROP DATABASE database_name;"` 365 | - Don't forget the comma at the end of the previous line to make it a valid json object. 366 | - Your database object should have these values: 367 | ```json 368 | { 369 | "create": "CREATE DATABASE database_name;", 370 | "drop": "DROP DATABASE database_name;" 371 | } 372 | ``` 373 | - The whole file should look like this: 374 | ```json 375 | { 376 | "database": { 377 | "create": "CREATE DATABASE database_name;", 378 | "drop": "DROP DATABASE database_name;" 379 | } 380 | } 381 | 382 | ``` 383 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 384 | - You can view the `git diff` to see if there's any extra spaces 385 | 386 | ## 290. git status 387 | 388 | ### 290.1 389 | 390 | Check your status. 391 | 392 | #### HINTS 393 | 394 | - Use the "git status" command in your repo 395 | - Type `git status` into the terminal and press enter 396 | - Make sure you are in your `sql_reference` repo folder 397 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 398 | 399 | ## 300. git diff 400 | 401 | ### 300.1 402 | 403 | Changes not staged. Check the `diff` quick. 404 | 405 | #### HINTS 406 | 407 | - Use the "git diff" command in your repo 408 | - Type `git diff` into the terminal and press enter 409 | - Make sure you are in your `sql_reference` repo folder 410 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 411 | 412 | ## 310. git add DROP DATABASE command 413 | 414 | ### 310.1 415 | 416 | It should show one line removed and two lines added. Add your changes to the staging area. 417 | 418 | #### HINTS 419 | 420 | - You previously used `git add README.md` to add changes to staging 421 | - Type `git add sql_reference.json` into the terminal and press enter 422 | - Make sure you are in your `sql_reference` repo folder 423 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 424 | 425 | ## 320. git commit feat: add drop database reference 426 | 427 | ### 320.1 428 | 429 | Commit your staged changes with the message, `feat: add drop database reference` 430 | 431 | #### HINTS 432 | 433 | - Commit changes with `git commit -m "message"` 434 | - Type `git commit -m "feat: add drop database reference"` into the terminal and press enter 435 | - View your `git log` to see if your message is correct 436 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 437 | - Or, reset the lesson and try again 438 | - Make sure you are in your `sql_reference` repo folder 439 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 440 | 441 | ## 330. git log 442 | 443 | ### 330.1 444 | 445 | I think you're catching on :smile: Check the `log` again. 446 | 447 | #### HINTS 448 | 449 | - Type `git log` into the terminal and press enter 450 | - Press `enter` in the terminal to go through the whole log 451 | - Make sure you are in your `sql_reference` repo folder 452 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 453 | 454 | ## 340. git branch 455 | 456 | ### 340.1 457 | 458 | Now there's three commits :smile: You have been making changes to your `main` branch. You actually want to try and avoid that. Type `git branch` to see the current branches in your repo. 459 | 460 | #### HINTS 461 | 462 | - Type `git branch` into the terminal and press enter 463 | - Make sure you are in your `sql_reference` repo folder 464 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 465 | 466 | ## 350. git branch feat/add-create-table-reference 467 | 468 | ### 350.1 469 | 470 | You only have the `main` branch still. You can create a branch with `git branch branch_name`. Branches often start with `fix/` or `feat/`, among others, like commit messages, but they use a forward slash and can't contain spaces. Create a new branch named `feat/add-create-table-reference`. 471 | 472 | #### HINTS 473 | 474 | - Type `git branch feat/add-create-table-reference` into the terminal and press enter 475 | - Make sure you are in your `sql_reference` repo folder 476 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 477 | 478 | ## 360. git branch 479 | 480 | ### 360.1 481 | 482 | Your new branch is a clone of the `main` branch since that's the branch you were on when you created it. It will have the same code and commit history as `main` did at the time of the branch creation. View your branches again with `git branch`. 483 | 484 | #### HINTS 485 | 486 | - Type `git branch` into the terminal and press enter 487 | - Make sure you are in your `sql_reference` repo folder 488 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 489 | 490 | ## 370. git checkout feat/add-create-table-reference 491 | 492 | ### 370.1 493 | 494 | You can see your new branch, but you are still on the `main` branch, as denoted with the `*`. To switch to a branch use: `git checkout branch_name`. Switch to your new branch. 495 | 496 | #### HINTS 497 | 498 | - Type `git checkout feat/add-create-table-reference` into the terminal and press enter 499 | - Make sure you are in your `sql_reference` repo folder 500 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 501 | 502 | ## 380. git branch 503 | 504 | ### 380.1 505 | 506 | It says you switched to your new branch. Type `git branch` so I can make sure the `*` switched. 507 | 508 | #### HINTS 509 | 510 | - Type `git branch` into the terminal and press enter 511 | - Make sure you are in your `sql_reference` repo folder 512 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 513 | 514 | ## 390. Add CREATE TABLE Command 515 | 516 | ### 390.1 517 | 518 | Like I said, you often don't want to make commits directly to the main branch of a repo. This branch will be for some new changes. What you will do is make the changes and commits here, then merge them into the `main` branch when they are ready. Add a reference for creating an SQL table to your json file along side your `database` property. Make it look like this: 519 | 520 | ```json 521 | "table": { 522 | "create": "CREATE TABLE table_name;" 523 | } 524 | ``` 525 | 526 | #### HINTS 527 | 528 | - Make sure to add commas to keep it a valid json object 529 | - The `table` key should be on the same level as the `database` key 530 | - The whole file should look like this: 531 | ```json 532 | { 533 | "database": { 534 | "create": "CREATE DATABASE database_name;", 535 | "drop": "DROP DATABASE database_name;" 536 | }, 537 | "table": { 538 | "create": "CREATE TABLE table_name;" 539 | } 540 | } 541 | 542 | ``` 543 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 544 | - You can view the `git diff` to see if there's any extra spaces 545 | 546 | ## 400. git status 547 | 548 | ### 400.1 549 | 550 | Show me the status again. You might as well get used to it :smiley_cat: 551 | 552 | #### HINTS 553 | 554 | - Use the "git status" command in your repo 555 | - Type `git status` into the terminal and press enter 556 | - Make sure you are in your `sql_reference` repo folder 557 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 558 | 559 | ## 405. git diff 560 | 561 | ### 405.1 562 | 563 | Changes not staged. Check the `diff` quick so you can make sure your changes look good. 564 | 565 | #### HINTS 566 | 567 | - Use the "git diff" command in your repo 568 | - Type `git diff` into the terminal and press enter 569 | - Make sure you are in your `sql_reference` repo folder 570 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 571 | 572 | ## 410. git add CREATE TABLE reference 573 | 574 | ### 410.1 575 | 576 | You made new changes so the file shows up as not staged. Add the file to staging so you can commit the changes. 577 | 578 | #### HINTS 579 | 580 | - Here's an example: `git add file_name` 581 | - You previously used `git add README.md` to add changes to staging 582 | - Type `git add sql_reference.json` into the terminal and press enter 583 | - Make sure you are in your `sql_reference` repo folder 584 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 585 | 586 | ## 420. git commit feat: add create table reference 587 | 588 | ### 420.1 589 | 590 | The changes are now in staging. Commit your staged changes with the message `feat: add create table reference`. 591 | 592 | #### HINTS 593 | 594 | - Commit changes with `git commit -m "message"` 595 | - Type `git commit -m "feat: add create table reference"` into the terminal and press enter 596 | - View your `git log` to see if your message is correct 597 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 598 | - Or, reset the lesson and try again 599 | - Make sure you are in your `sql_reference` repo folder 600 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 601 | 602 | ## 430. git log 603 | 604 | ### 430.1 605 | 606 | Check your `git log` again. 607 | 608 | #### HINTS 609 | 610 | - Type `git log` into the terminal and press enter 611 | - Press `enter` in the terminal to go through the whole log 612 | - Make sure you are in your `sql_reference` repo folder 613 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 614 | 615 | ## 435. git log oneline 616 | 617 | ### 435.1 618 | 619 | Now you have four commits, they are getting a little hard to see. Check the log again, but this time use the `--oneline` flag to condense the output so it's more readable. 620 | 621 | #### HINTS 622 | 623 | - Type `git log --oneline` into the terminal and press enter 624 | - Make sure you are in your `sql_reference` repo folder 625 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 626 | 627 | ## 440. git checkout main 628 | 629 | ### 440.1 630 | 631 | That's better. Use `git checkout` to switch back to the `main` branch. 632 | 633 | #### HINTS 634 | 635 | - Use `git checkout branch_name` to switch to a branch 636 | - Enter `git checkout main` into the terminal and press enter 637 | 638 | ## 450. git log 639 | 640 | ### 450.1 641 | 642 | You may have noticed that the code you added disappeared from the JSON file. Your changes were added on the `feat/add-create-table-reference` branch so they don't exist on this branch. Check the log of the main branch, use the `--oneline` flag again. 643 | 644 | #### HINTS 645 | 646 | - Type `git log --oneline` into the terminal and press enter 647 | - Make sure you are in your `sql_reference` repo folder 648 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 649 | 650 | ## 460. git branch 651 | 652 | ### 460.1 653 | 654 | You can see three commits on this branch and four on the feature branch you were just on. The commit and code you added on the feature branch only exist over there for now. View the branches you have to remind me the name of your other branch. 655 | 656 | #### HINTS 657 | 658 | - Type `git branch` into the terminal and press enter 659 | - Make sure you are in your `sql_reference` repo folder 660 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 661 | 662 | ## 470. git merge feat/add-create-table-reference 663 | 664 | ### 470.1 665 | 666 | You created the `feat/add-create-table-reference` branch, made a commit, and now it's ready to be added to the `main` branch. You can use `git merge branch_name` to bring changes from a branch into the branch you are currently on. Merge the changes from your feature branch into the `main` branch. 667 | 668 | #### HINTS 669 | 670 | - Type `git merge feat/add-create-table-reference` into the terminal and press enter 671 | - Make sure you enter the command while on the `main` branch 672 | 673 | ## 480. git log oneline 674 | 675 | ### 480.1 676 | 677 | The commits and code from your feature branch were added to this branch. There's a message with some info about the merge. Check the log with the `--oneline` flag again. 678 | 679 | #### HINTS 680 | 681 | - Use the `git log` command with the correct flag 682 | - Type `git log --oneline` into the terminal and press enter 683 | 684 | ## 490. git branch -d feat/add-create-table-reference 685 | 686 | ### 490.1 687 | 688 | The `feat: add create table reference` commit you made on your feature branch was added to this branch with the merge. You can delete a branch with `git branch -d branch_name`. `-d` stands for "delete". Since your changes were added, you can safely delete your feature branch. Do that now. 689 | 690 | #### HINTS 691 | 692 | - The branch name is `feat/add-create-table-reference` 693 | - Type `git branch -d feat/add-create-table-reference` into the terminal and press enter 694 | 695 | ## 500. git branch 696 | 697 | ### 500.1 698 | 699 | It said it was deleted, but view your branches again for me to verify that it's gone. 700 | 701 | #### HINTS 702 | 703 | - Type `git branch` into the terminal and press enter 704 | - Make sure you are in your `sql_reference` repo folder 705 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 706 | 707 | ## 510. git checkout -b feat/add-drop-table-reference 708 | 709 | ### 510.1 710 | 711 | You're just left with the `main` branch... Want to try it again? Last time you created a branch and then switched to it. You can do both at the same time with `git checkout -b branch_name`. Create and switch to a new branch named `feat/add-drop-table-reference`. 712 | 713 | #### HINTS 714 | 715 | - Type `git checkout -b feat/add-drop-table-reference` into the terminal and press enter 716 | 717 | ## 520. Add DROP TABLE Command 718 | 719 | ### 520.1 720 | 721 | Add a `drop` key to the `table` object of your JSON file. Give it a value for how to drop a table. The syntax is in the hints. 722 | 723 | #### HINTS 724 | 725 | - The value should be `"DROP TABLE table_name;"` 726 | - Don't forget the commas to make it a valid json object 727 | - The key looks like this: `"drop": "DROP TABLE table_name;"` 728 | - The `table` object should look like this: 729 | ```json 730 | "table": { 731 | "create": "CREATE TABLE table_name;", 732 | "drop": "DROP TABLE table_name;" 733 | } 734 | ``` 735 | - The whole file should look like this: 736 | ```json 737 | { 738 | "database": { 739 | "create": "CREATE DATABASE database_name;", 740 | "drop": "DROP DATABASE database_name;" 741 | }, 742 | "table": { 743 | "create": "CREATE TABLE table_name;", 744 | "drop": "DROP TABLE table_name;" 745 | } 746 | } 747 | 748 | ``` 749 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 750 | - You can view the `git diff` to see if there's any extra spaces 751 | 752 | ## 530. git status 753 | 754 | ### 530.1 755 | 756 | Check your status. 757 | 758 | #### HINTS 759 | 760 | - Use the "git status" command in your repo 761 | - Type `git status` into the terminal and press enter 762 | - Make sure you are in your `sql_reference` repo folder 763 | 764 | ## 535. git diff 765 | 766 | ### 535.1 767 | 768 | Check the `diff` so you can confirm you like your changes. 769 | 770 | #### HINTS 771 | 772 | - Use the "git diff" command in your repo 773 | - Type `git diff` into the terminal and press enter 774 | - Make sure you are in your `sql_reference` repo folder 775 | - Enter `cd ~/project/sql_reference` to go to the folder if you aren't there 776 | 777 | ## 540. git add DROP TABLE command 778 | 779 | ### 540.1 780 | 781 | Add your changes to staging. 782 | 783 | #### HINTS 784 | 785 | - You previously used `git add README.md` to add changes to staging 786 | - Type `git add sql_reference.json` into the terminal and press enter 787 | - Make sure you are in your `sql_reference` repo folder 788 | 789 | ## 550. git commit feat: add drop table reference 790 | 791 | ### 550.1 792 | 793 | Commit your staged changes with the message `feat: add drop table reference`. 794 | 795 | #### HINTS 796 | 797 | - Commit changes with `git commit -m "message"` 798 | - Type `git commit -m "feat: add drop table reference"` into the terminal and press enter 799 | - View your `git log` to see if your message is correct 800 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 801 | - Or, reset the lesson and try again 802 | - Make sure you are in your `sql_reference` repo folder 803 | 804 | ## 560. git checkout main 805 | 806 | ### 560.1 807 | 808 | Switch back your `main` branch so you can merge in these changes. 809 | 810 | #### HINTS 811 | 812 | - Use `git checkout branch_name` to switch to a branch 813 | - Enter `git checkout main` into the terminal and press enter 814 | 815 | ## 570. git branch 816 | 817 | ### 570.1 818 | 819 | Remember that the code and commit you added aren't on this branch, so they disappeared again. View the branches on your repo so you can get the name of it to merge your feature into the main branch. 820 | 821 | #### HINTS 822 | 823 | - Use `git branch` to view your branches 824 | - Make sure you are in your `sql_reference` repo folder 825 | 826 | ## 580. git merge feat/add-drop-table-reference 827 | 828 | ### 580.1 829 | 830 | Merge your feature branch into the `main` branch. 831 | 832 | #### HINTS 833 | 834 | - Here's an example: `git merge branch_name` 835 | - The command will merge `branch_name` into whatever branch you are on 836 | - Type `git merge feat/add-drop-table-reference` into the terminal and press enter 837 | - Make sure you enter the command while on the `main` branch 838 | 839 | ## 590. git branch -d feat/add-drop-table-reference 840 | 841 | ### 590.1 842 | 843 | The commit from your feature branch was added to the `main` branch so you can safely delete the feature branch. Delete your feature branch. 844 | 845 | #### HINTS 846 | 847 | - Use the `git branch` command with the `-d` flag to delete a branch 848 | - Use the "git branch" command to find the branch name 849 | - The branch name is `feat/add-drop-table-reference` 850 | - Here's an example: `git branch -d branch_name` 851 | - Type `git branch -d feat/add-drop-table-reference` into the terminal and press enter 852 | 853 | ## 600. git checkout -b feat/add-column-references 854 | 855 | ### 600.1 856 | 857 | You're getting the hang of it :smile: The process is to create a branch, make the changes you want, commit them, and then merge the changes into branch you started on. Pretty simple, lets keep going. Create and checkout a new branch named `feat/add-column-references` 858 | 859 | #### HINTS 860 | 861 | - You can create and checkout a branch with `git checkout -b branch_name` 862 | - Type `git checkout -b feat/add-column-references` into the terminal and press enter 863 | 864 | ## 610. Add ADD COLUMN command 865 | 866 | ### 610.1 867 | 868 | This branch will be a work in progress. Add a `column` key to your JSON object. Make it an object like the other two. Give it a single property, `add`, that has the value `"ALTER TABLE table_name ADD COLUMN column_name;"`. 869 | 870 | #### HINTS 871 | 872 | - The `column` key should be on the same level as the `table` key 873 | - The `column` object should look like this: 874 | ```json 875 | "column": { 876 | "add": "ALTER TABLE table_name ADD COLUMN column_name;" 877 | } 878 | ``` 879 | - The whole file should look like this: 880 | ```json 881 | { 882 | "database": { 883 | "create": "CREATE DATABASE database_name;", 884 | "drop": "DROP DATABASE database_name;" 885 | }, 886 | "table": { 887 | "create": "CREATE TABLE table_name;", 888 | "drop": "DROP TABLE table_name;" 889 | }, 890 | "column": { 891 | "add": "ALTER TABLE table_name ADD COLUMN column_name;" 892 | } 893 | } 894 | 895 | ``` 896 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 897 | - You can view the `git diff` to see if there's any extra spaces 898 | 899 | ## 620. git diff 900 | 901 | ### 620.1 902 | 903 | View the `diff` to make sure your new changes are what you expect. 904 | 905 | #### HINTS 906 | 907 | - Use the "git diff" command 908 | - Type `git diff` into the terminal and press enter 909 | - Make sure you are in your repo folder first 910 | 911 | ## 630. git add ADD COLUMN command 912 | 913 | ### 630.1 914 | 915 | Add your changes to staging. Here's a tip: you can use `git add .` to add all files to staging. 916 | 917 | #### HINTS 918 | 919 | - Here's an example: `git add file_name` 920 | - You previously used `git add README.md` to add changes to staging 921 | - Type `git add sql_reference.json` into the terminal and press enter 922 | 923 | ## 640. git commit feat: add column reference 924 | 925 | ### 640.1 926 | 927 | Commit your staged changes with the message `feat: add column reference`. 928 | 929 | #### HINTS 930 | 931 | - Commit changes with `git commit -m "message"` 932 | - Type `git commit -m "feat: add column reference"` into the terminal and press enter 933 | - View your `git log` to see if your message is correct 934 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 935 | - Or, reset the lesson and try again 936 | 937 | ## 650. git log oneline 938 | 939 | ### 650.1 940 | 941 | View your log with the oneline flag. 942 | 943 | #### HINTS 944 | 945 | - Use the `git log` command with the correct flag 946 | - It's the `--oneline` flag 947 | - Type `git log --oneline` into the terminal and press enter 948 | 949 | ## 670. git checkout main 950 | 951 | ### 670.1 952 | 953 | The commit was added. I see an error in the syntax of one of the commands. You want to fix it, but this branch is not for fixing it. Switch back to your `main` branch so you can create a new branch to fix it. 954 | 955 | #### HINTS 956 | 957 | - Use `git checkout branch_name` to switch to a branch 958 | - Enter `git checkout main` into the terminal and press enter 959 | 960 | ## 680. git checkout -b fix/create-table-syntax 961 | 962 | ### 680.1 963 | 964 | Remember that, when you create a branch, it will be a clone of whatever branch you are on when you create it. That's why you switched to `main` first. Create and switch to a branch named `fix/create-table-syntax`. 965 | 966 | #### HINTS 967 | 968 | - Here's an example: `git checkout -b branch_name` 969 | - Type `git checkout -b fix/create-table-syntax` into the terminal and press enter 970 | 971 | ## 690. Fix CREATE TABLE syntax 972 | 973 | ### 690.1 974 | 975 | The create table command is a function, so it needs parenthesis `()` at the end. Add those to the end of the command. 976 | 977 | #### HINTS 978 | 979 | - It's the `table.create` key that you need to change 980 | - The value should look like this: `CREATE TABLE table_name();` 981 | - The `table` object should look like this: 982 | ```json 983 | "table": { 984 | "create": "CREATE TABLE table_name();", 985 | "drop": "DROP TABLE table_name;" 986 | } 987 | ``` 988 | - The whole file should look like this: 989 | ```json 990 | { 991 | "database": { 992 | "create": "CREATE DATABASE database_name;", 993 | "drop": "DROP DATABASE database_name;" 994 | }, 995 | "table": { 996 | "create": "CREATE TABLE table_name();", 997 | "drop": "DROP TABLE table_name;" 998 | } 999 | } 1000 | 1001 | ``` 1002 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1003 | - You can view the `git diff` to see if there's any extra spaces 1004 | 1005 | ## 700. git add FIX CREATE TABLE command 1006 | 1007 | ### 700.1 1008 | 1009 | Check your status and diff to see your new changes. Then, add your files to staging. 1010 | 1011 | #### HINTS 1012 | 1013 | - Here's an example: `git add file_name` 1014 | - You previously used `git add README.md` to add changes to staging 1015 | - Type `git add sql_reference.json` into the terminal and press enter 1016 | 1017 | ## 710. git commit fix: create table syntax 1018 | 1019 | ### 710.1 1020 | 1021 | Commit your changes with the message `fix: create table syntax`. 1022 | 1023 | #### HINTS 1024 | 1025 | - Commit changes with `git commit -m "message"` 1026 | - Type `git commit -m "fix: create table syntax"` into the terminal and press enter 1027 | - View your `git log` to see if your message is correct 1028 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 1029 | - Or, reset the lesson and try again 1030 | 1031 | ## 720. git checkout main 1032 | 1033 | ### 720.1 1034 | 1035 | Switch back to your `main` so you can merge this important bug fix. 1036 | 1037 | #### HINTS 1038 | 1039 | - Use `git checkout branch_name` to switch to a branch 1040 | - Enter `git checkout main` into the terminal and press enter 1041 | 1042 | ## 730. git branch 1043 | 1044 | ### 730.1 1045 | 1046 | View your branches to remind me of the branch name. 1047 | 1048 | #### HINTS 1049 | 1050 | - Use `git branch` to view your branches 1051 | - Make sure you are in your `sql_reference` repo folder 1052 | 1053 | ## 740. git merge fix/create-table-syntax 1054 | 1055 | ### 740.1 1056 | 1057 | Merge your bug fix branch into this branch. 1058 | 1059 | #### HINTS 1060 | 1061 | - It's the `fix/create-table-syntax` branch 1062 | - Here's an example: `git merge branch_name` 1063 | - Type `git merge fix/create-table-syntax` into the terminal and press enter 1064 | 1065 | ## 750. git log oneline 1066 | 1067 | ### 750.1 1068 | 1069 | View your log with the oneline flag. 1070 | 1071 | #### HINTS 1072 | 1073 | - Use the `git log` command with the correct flag 1074 | - It's the `--oneline` flag 1075 | - Type `git log --oneline` into the terminal and press enter 1076 | 1077 | ## 755. git branch -d fix/create-table-syntax 1078 | 1079 | ### 755.1 1080 | 1081 | The bug fix is in and you can safely delete the branch. Go ahead and delete the branch that was for that fix. View your branches if you need to find the name. 1082 | 1083 | #### HINTS 1084 | 1085 | - Use the `git branch` command with the `-d` flag 1086 | - Here's an example: `git branch -d branch_name` 1087 | - The branch name is `fix/create-table-syntax` 1088 | - Type `git branch -d fix/create-table-syntax` into the terminal and press enter 1089 | 1090 | ## 760. git checkout feat/add-column-references 1091 | 1092 | ### 760.1 1093 | 1094 | Your bug fix is merged into the `main` branch. Switch back to your feature branch so you can continue adding column references. 1095 | 1096 | #### HINTS 1097 | 1098 | - Check your branches if you need to get the name of the branch 1099 | - You can view your branches with `git branch` 1100 | - Use `git checkout branch_name` to switch to a branch 1101 | - It's the `feat/add-column-references` branch 1102 | - Enter `git checkout feat/add-column-references` into the terminal and press enter 1103 | 1104 | ## 770. git log oneline 1105 | 1106 | ### 770.1 1107 | 1108 | View your log with the oneline flag. 1109 | 1110 | #### HINTS 1111 | 1112 | - Use the `git log` command with the correct flag 1113 | - It's the `--oneline` flag 1114 | - Type `git log --oneline` into the terminal and press enter 1115 | 1116 | ## 780. git rebase main 1117 | 1118 | ### 780.1 1119 | 1120 | You created this branch and made a commit. Since then, a commit for a bug fix was added to `main`. This is common with many people working on a codebase simultaneously. You need to update this branch so it has the same commits from `main`, but you can't just merge that branch into this one. You need that bug fix commit to be in the same order here as it is on `main`, right after the "drop table" commit. You need to `rebase` this branch against `main` to do that. Enter `git rebase main` to rebase this branch. 1121 | 1122 | #### HINTS 1123 | 1124 | - Type `git rebase main` into the terminal and press enter 1125 | 1126 | ## 790. git log oneline 1127 | 1128 | ### 790.1 1129 | 1130 | There was some fancy output there, but you can see the parenthesis from the bug fix commit were added to the `table.create` value. Show me the log again with the same flag you have been using so you can see what happened. 1131 | 1132 | #### HINTS 1133 | 1134 | - Use the `git log` command with the correct flag 1135 | - It's the `--oneline` flag 1136 | - Type `git log --oneline` into the terminal and press enter 1137 | 1138 | ## 800. Add DROP COLUMN command 1139 | 1140 | ### 800.1 1141 | 1142 | The logs show that the bug fix commit from `main` was added, and then the commit from this branch was added on top of it. Now, when this branch is ready to be merged into `main`, it will have the same commit history. You should try to keep your branches up to date like this by rebasing them often. In your JSON file, add a `drop` key to the `column` object with a reference for dropping a column. The syntax is in the hints, give it a try first. 1143 | 1144 | #### HINTS 1145 | 1146 | - It follows a similar syntax as adding a column 1147 | - Don't forget the semi-colon at the end 1148 | - Here's the syntax: `ALTER TABLE table_name DROP COLUMN column_name;` 1149 | - Make sure the above value is in the `column.drop` key 1150 | - Here's what the `column` object should look like: 1151 | ```json 1152 | "column": { 1153 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 1154 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;" 1155 | } 1156 | ``` 1157 | - The whole file should look like this: 1158 | ```json 1159 | { 1160 | "database": { 1161 | "create": "CREATE DATABASE database_name;", 1162 | "drop": "DROP DATABASE database_name;" 1163 | }, 1164 | "table": { 1165 | "create": "CREATE TABLE table_name();", 1166 | "drop": "DROP TABLE table_name;" 1167 | }, 1168 | "column": { 1169 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 1170 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;" 1171 | } 1172 | } 1173 | 1174 | ``` 1175 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1176 | - You can view the `git diff` to see if there's any extra spaces 1177 | 1178 | ## 810. git add DROP COLUMN command 1179 | 1180 | ### 810.1 1181 | 1182 | Check your status and diff to see your new changes. Then, add your changes to staging. 1183 | 1184 | #### HINTS 1185 | 1186 | - Here's an example: `git add file_name` 1187 | - You previously used `git add README.md` to add changes to staging 1188 | - Type `git add sql_reference.json` into the terminal and press enter 1189 | 1190 | ## 820. git commit feat: drop column reference 1191 | 1192 | ### 820.1 1193 | 1194 | Commit your changes with the message: `feat: add drop column reference`. 1195 | 1196 | #### HINTS 1197 | 1198 | - Commit changes with `git commit -m "message"` 1199 | - Type `git commit -m "feat: add drop column reference"` into the terminal and press enter 1200 | - View your `git log` to see if your message is correct 1201 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 1202 | - Or, reset the lesson and try again 1203 | 1204 | ## 830. git log oneline 1205 | 1206 | ### 830.1 1207 | 1208 | View your log again. Make sure you use my favorite flag. 1209 | 1210 | #### HINTS 1211 | 1212 | - Use the `git log` command with the correct flag 1213 | - It's the `--oneline` flag 1214 | - Type `git log --oneline` into the terminal and press enter 1215 | 1216 | ## 840. git checkout main 1217 | 1218 | ### 840.1 1219 | 1220 | Switch to your `main` branch, there's another feature that needs to be worked on. 1221 | 1222 | #### HINTS 1223 | 1224 | - Use the `git checkout` command 1225 | - Here's an example: `git checkout branch_name` 1226 | - Enter `git checkout main` into the terminal and press enter 1227 | 1228 | ## 850. git checkout -b feat/add-insert-row-reference 1229 | 1230 | ### 850.1 1231 | 1232 | Create and switch to a new branch named `feat/add-insert-row-reference`. 1233 | 1234 | #### HINTS 1235 | 1236 | - Here's an example: `git checkout -b branch_name` 1237 | - Type `git checkout -b feat/add-insert-row-reference` into the terminal and press enter 1238 | 1239 | ## 860. Add INSERT ROW command 1240 | 1241 | ### 860.1 1242 | 1243 | Pretend that this branch is for someone else working on a new feature at the same time you are working on the column commands. Add a `row` key to your JSON object. Make it an object with an `insert` key whose value is `"INSERT INTO table_name(columns) VALUES(values);"` 1244 | 1245 | #### HINTS 1246 | 1247 | - Your JSON object should have this: 1248 | ```json 1249 | "row": { 1250 | "insert": "INSERT INTO table_name(columns) VALUES(values);" 1251 | } 1252 | ``` 1253 | - The `row` key should be on the same level as the `table` key 1254 | - The whole file should look like this: 1255 | ```json 1256 | { 1257 | "database": { 1258 | "create": "CREATE DATABASE database_name;", 1259 | "drop": "DROP DATABASE database_name;" 1260 | }, 1261 | "table": { 1262 | "create": "CREATE TABLE table_name();", 1263 | "drop": "DROP TABLE table_name;" 1264 | }, 1265 | "row": { 1266 | "insert": "INSERT INTO table_name(columns) VALUES(values);" 1267 | } 1268 | } 1269 | 1270 | ``` 1271 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1272 | - You can view the `git diff` to see if there's any extra spaces 1273 | 1274 | ## 870. git add INSERT ROW command 1275 | 1276 | ### 870.1 1277 | 1278 | Check your status and diff so you can see your new changes. Then, add your changes to staging. 1279 | 1280 | #### HINTS 1281 | 1282 | - Here's an example: `git add file_name` 1283 | - You previously used `git add README.md` to add changes to staging 1284 | - Type `git add sql_reference.json` into the terminal and press enter 1285 | 1286 | ## 880. git commit feat: add insert row reference 1287 | 1288 | ### 880.1 1289 | 1290 | Commit your changes with the message: `feat: add insert row reference`. 1291 | 1292 | #### HINTS 1293 | 1294 | - Commit changes with `git commit -m "message"` 1295 | - Type `git commit -m "feat: add insert row reference"` into the terminal and press enter 1296 | - View your `git log` to see if your message is correct 1297 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 1298 | - Or, reset the lesson and try again 1299 | 1300 | ## 890. git checkout main 1301 | 1302 | ### 890.1 1303 | 1304 | This branch is finished. Switch to your `main` branch so you can merge this commit in. 1305 | 1306 | #### HINTS 1307 | 1308 | - Use the `git checkout` command 1309 | - Here's an example: `git checkout branch_name` 1310 | - Enter `git checkout main` into the terminal and press enter 1311 | 1312 | ## 900. git branch 1313 | 1314 | ### 900.1 1315 | 1316 | View your branches to find the name of the branch you want to merge. 1317 | 1318 | #### HINTS 1319 | 1320 | - Use `git branch` to view your branches 1321 | - Make sure you are in your `sql_reference` repo folder 1322 | 1323 | ## 910. git merge feat/add-insert-row-reference 1324 | 1325 | ### 910.1 1326 | 1327 | Merge your branch with the `insert row` reference you were just working on into the `main` branch. 1328 | 1329 | #### HINTS 1330 | 1331 | - Use the `git merge` command 1332 | - Here's an example: `git merge branch_name` 1333 | - You want to merge the `feat/add-insert-row-reference` branch 1334 | - Type `git merge feat/add-insert-row-reference` into the terminal and press enter 1335 | 1336 | ## 930. git checkout feat/add-column-references 1337 | 1338 | ### 930.1 1339 | 1340 | Check your logs to make sure the commit was added. Then, switch to your branch for adding column references. 1341 | 1342 | #### HINTS 1343 | 1344 | - Use the "git branch" command to find the name of the branch 1345 | - Use the `git checkout` command 1346 | - The branch you want to switch to is `feat/add-column-references` 1347 | - Here's an example: `git checkout branch_name` 1348 | - Enter `git checkout feat/add-column-references` into the terminal and press enter 1349 | 1350 | ## 940. git rebase main 1351 | 1352 | ### 940.1 1353 | 1354 | Another commit was added to `main`, you should update this branch again. To be more specific, a rebase will "rewind" this branch to where it last matched `main`, then, add the commits from `main` that aren't here. After that, it adds the commits you made to this branch on top. `rebase` this branch against `main` so it's up to date. You should see a conflict... 1355 | 1356 | #### HINTS 1357 | 1358 | - Here's an example: `git rebase branch_name` 1359 | - Type `git rebase main` into the terminal and press enter 1360 | 1361 | ## 950. fix conflicts 1362 | 1363 | ### 950.1 1364 | 1365 | The conflict arose because the first commit you added to this branch changed the same lines as the commit from `main`. So it tried to add the commit, but couldn't because something was already there. There are sections, separated by characters (`<`, `>`, and `=`), that represent the commit you are on (`HEAD`) and the commit that is trying to be added (`feat: add column reference`). Fix the conflict by removing those `<`, `>`, and `=` characters. Then making the JSON object valid again. 1366 | 1367 | #### HINTS 1368 | 1369 | - Be sure to remove all those special characters 1370 | - The part of the JSON object with conflicts should look like this: 1371 | ```json 1372 | "row": { 1373 | "insert": "INSERT INTO table_name(columns) VALUES(values);" 1374 | }, 1375 | "column": { 1376 | "add": "ALTER TABLE table_name ADD COLUMN column_name;" 1377 | } 1378 | ``` 1379 | - The whole file should look like this: 1380 | ```json 1381 | { 1382 | "database": { 1383 | "create": "CREATE DATABASE database_name;", 1384 | "drop": "DROP DATABASE database_name;" 1385 | }, 1386 | "table": { 1387 | "create": "CREATE TABLE table_name();", 1388 | "drop": "DROP TABLE table_name;" 1389 | }, 1390 | "row": { 1391 | "insert": "INSERT INTO table_name(columns) VALUES(values);" 1392 | }, 1393 | "column": { 1394 | "add": "ALTER TABLE table_name ADD COLUMN column_name;" 1395 | } 1396 | } 1397 | 1398 | ``` 1399 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1400 | - You can view the `git diff` to see if there's any extra spaces 1401 | 1402 | ## 953. git status 1403 | 1404 | ### 953.1 1405 | 1406 | Check your status. 1407 | 1408 | #### HINTS 1409 | 1410 | - Use the "git status" command in your repo 1411 | - Type `git status` into the terminal and press enter 1412 | - Make sure you are in your `sql_reference` repo folder 1413 | 1414 | ## 956. git add fixed conflicts 1415 | 1416 | ### 956.1 1417 | 1418 | It says that you are still in the middle of rebasing and there's one file that needs to be merged yet. Add the file to staging like you would any other commit. 1419 | 1420 | #### HINTS 1421 | 1422 | - Here's an example: `git add file_name` 1423 | - You previously used `git add README.md` to add changes to staging 1424 | - Type `git add sql_reference.json` into the terminal and press enter 1425 | 1426 | ## 958. git status 1427 | 1428 | ### 958.1 1429 | 1430 | Check your status again. 1431 | 1432 | #### HINTS 1433 | 1434 | - Use the "git status" command in your repo 1435 | - Type `git status` into the terminal and press enter 1436 | - Make sure you are in your `sql_reference` repo folder 1437 | 1438 | ## 960. git rebase continue 1439 | 1440 | ### 960.1 1441 | 1442 | You fixed the conflicts that arose from trying to add this commit and added them to staging. It says `all conflicts fixed: run "git rebase --continue"`. Run the suggested command to continue the rebase. 1443 | 1444 | #### HINTS 1445 | 1446 | - Enter `git rebase --continue` in the terminal and press enter 1447 | 1448 | ## 970. git log oneline 1449 | 1450 | ### 970.1 1451 | 1452 | The last commit was added after you continued the rebase without conflict. The rebase is now finished. View your log with the `oneline` flag. 1453 | 1454 | #### HINTS 1455 | 1456 | - Use the `git log` command 1457 | - Type `git log --oneline` into the terminal and press enter 1458 | 1459 | ## 980. Add RENAME COLUMN command 1460 | 1461 | ### 980.1 1462 | 1463 | You can see the "insert row" commit from `main` was added to this branch before the two commits you made here. Now this branch is up to date and you can continue working on it. Add a `rename` key to the `column` object. The value should look like this: `"ALTER TABLE table_name RENAME COLUMN column_name TO new_name;"` 1464 | 1465 | #### HINTS 1466 | 1467 | - The `column` key should look like this: 1468 | ```json 1469 | "column": { 1470 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 1471 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 1472 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;" 1473 | } 1474 | ``` 1475 | - The whole file should look like this: 1476 | ```json 1477 | { 1478 | "database": { 1479 | "create": "CREATE DATABASE database_name;", 1480 | "drop": "DROP DATABASE database_name;" 1481 | }, 1482 | "table": { 1483 | "create": "CREATE TABLE table_name();", 1484 | "drop": "DROP TABLE table_name;" 1485 | }, 1486 | "row": { 1487 | "insert": "INSERT INTO table_name(columns) VALUES(values);" 1488 | }, 1489 | "column": { 1490 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 1491 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 1492 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;" 1493 | } 1494 | } 1495 | 1496 | ``` 1497 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1498 | - You can view the `git diff` to see if there's any extra spaces 1499 | 1500 | 1501 | ## 990. git add RENAME COLUMN command 1502 | 1503 | ### 990.1 1504 | 1505 | Check your status and diff to see your new changes. Then, add the file to staging. 1506 | 1507 | #### HINTS 1508 | 1509 | - Use the `git add` command 1510 | - Here's an example: `git add file_name` 1511 | - You previously used `git add README.md` to add changes to staging 1512 | - Type `git add sql_reference.json` into the terminal and press enter 1513 | 1514 | ## 1000. git commit feat: add rename column reference 1515 | 1516 | ### 1000.1 1517 | 1518 | Commit your changes with the message `feat: add rename column reference` 1519 | 1520 | #### HINTS 1521 | 1522 | - Commit changes with `git commit -m "message"` 1523 | - Type `git commit -m "feat: add rename column reference"` into the terminal and press enter 1524 | - View your `git log` to see if your message is correct 1525 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 1526 | - Or, reset the lesson and try again 1527 | 1528 | ## 1010. git checkout feat/add-insert-row-reference 1529 | 1530 | ### 1010.1 1531 | 1532 | There's now three commits that are unique to this branch, you will come back to it later. Switch to the branch for adding row references. 1533 | 1534 | #### HINTS 1535 | 1536 | - View your branches with `git branch` if you need to find the name 1537 | - Use the `git checkout` command to switch branches 1538 | - Here's an example: `git checkout branch_name` 1539 | - The branch you want is `feat/add-insert-row-reference` 1540 | - Enter `git checkout feat/add-insert-row-reference` into the terminal and press enter 1541 | 1542 | ## 1015. Add UPDATE ROW command 1543 | 1544 | ### 1015.1 1545 | 1546 | This branch is still up to date since no commits have been added to `main` since this branch was created. Add an `update` key to the `row` object with `"UPDATE table_name SET column_name = new_value WHERE condition;"` as it's value. 1547 | 1548 | #### HINTS 1549 | 1550 | - The `row` key should look like this: 1551 | ```json 1552 | "row": { 1553 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 1554 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;" 1555 | } 1556 | ``` 1557 | - The whole file should look like this: 1558 | ```json 1559 | { 1560 | "database": { 1561 | "create": "CREATE DATABASE database_name;", 1562 | "drop": "DROP DATABASE database_name;" 1563 | }, 1564 | "table": { 1565 | "create": "CREATE TABLE table_name();", 1566 | "drop": "DROP TABLE table_name;" 1567 | }, 1568 | "row": { 1569 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 1570 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;" 1571 | } 1572 | } 1573 | 1574 | ``` 1575 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1576 | - You can view the `git diff` to see if there's any extra spaces 1577 | 1578 | ## 1017. git status 1579 | 1580 | ### 1017.1 1581 | 1582 | Check your status. 1583 | 1584 | #### HINTS 1585 | 1586 | - Use the "git status" command in your repo 1587 | - Type `git status` into the terminal and press enter 1588 | - Make sure you are in your `sql_reference` repo folder 1589 | 1590 | ## 1020. git stash 1591 | 1592 | ### 1020.1 1593 | 1594 | There's been a mistake. This branch was for the `insert` command, not the `update` command. You can put your changes aside with `git stash`. Stash your changes so you can add them to a different branch. 1595 | 1596 | #### HINTS 1597 | 1598 | - Type `git stash` in the terminal and press enter 1599 | 1600 | ## 1025. git status 1601 | 1602 | ### 1025.1 1603 | 1604 | You might have noticed your uncommitted changes disappeared from the file. Check your status again. 1605 | 1606 | #### HINTS 1607 | 1608 | - Use the "git status" command in your repo 1609 | - Type `git status` into the terminal and press enter 1610 | - Make sure you are in your `sql_reference` repo folder 1611 | 1612 | ## 1030. git stash list 1613 | 1614 | ### 1030.1 1615 | 1616 | Your working tree is clean and there's no changes git recognizes. The changes you made are stashed. View the things you have stashed with `git stash list`. 1617 | 1618 | #### HINTS 1619 | 1620 | - View your stash list with the suggested command 1621 | - Type `git stash list` in the terminal and press enter 1622 | 1623 | ## 1040. git stash pop 1624 | 1625 | ### 1040.1 1626 | 1627 | You can see one item there. Bring the changes back with `git stash pop`. 1628 | 1629 | #### HINTS 1630 | 1631 | - Bring your stash back with the suggested command 1632 | - Type `git stash pop` in the terminal and press enter 1633 | 1634 | ## 1050. git stash list 1635 | 1636 | ### 1050.1 1637 | 1638 | The changes from the stash reappeared in the file and git showed the status for you. You are right where you left off before stashing the changes. Popping a stash like that will remove the most recent stash and apply it to your working tree. View the list of your stashes again. 1639 | 1640 | #### HINTS 1641 | 1642 | - Use the "git stash list" command in your repo 1643 | - Type `git stash list` in the terminal and press enter 1644 | 1645 | ## 1055. git stash 1646 | 1647 | ### 1055.1 1648 | 1649 | The list is empty again. Put the changes back in the stash. 1650 | 1651 | #### HINTS 1652 | 1653 | - Use the "git stash" command 1654 | - Type `git stash` in the terminal and press enter 1655 | 1656 | ## 1070. git stash list 1657 | 1658 | ### 1070.1 1659 | 1660 | View the list of your stashed changes. 1661 | 1662 | #### HINTS 1663 | 1664 | - Use the "git stash list" command in your repo 1665 | - Type `git stash list` in the terminal and press enter 1666 | 1667 | ## 1073. git stash show 1668 | 1669 | ### 1073.1 1670 | 1671 | The changes are stashed again. View a condensed version of the changes in the **latest** stash with `git stash show`. 1672 | 1673 | #### HINTS 1674 | 1675 | - Type `git stash show` in the terminal and press enter 1676 | 1677 | ## 1076. git stash show -p 1678 | 1679 | ### 1076.1 1680 | 1681 | You can see what file was changed and how many lines were added and removed from the file. View the full changes of the latest stash with `git stash show -p`. `-p` stands for "patch". 1682 | 1683 | #### HINTS 1684 | 1685 | - Type `git stash show -p` in the terminal and press enter 1686 | 1687 | ## 1080. git stash apply 1688 | 1689 | ### 1080.1 1690 | 1691 | Now you can see the actual changes that are stored in the stash. Before, you used the pop command to remove the latest stash and add it to your working tree. You can add the latest stash while keeping it in the list with `git stash apply`. Apply your stash with this method. 1692 | 1693 | #### HINTS 1694 | 1695 | - Type `git stash apply` in the terminal and press enter 1696 | 1697 | ## 1090. git stash list 1698 | 1699 | ### 1090.1 1700 | 1701 | Git showed you your status after applying the stash. The one file is unstaged again. View your stash list. 1702 | 1703 | #### HINTS 1704 | 1705 | - Use the "git stash list" command in your repo 1706 | - Type `git stash list` in the terminal and press enter 1707 | 1708 | ## 1100. git stash 1709 | 1710 | ### 1100.1 1711 | 1712 | The code from the stash was added to your working tree, and the stash is still there in case you want to add it somewhere else. Stash the changes again. 1713 | 1714 | #### HINTS 1715 | 1716 | - Use the "git stash" command 1717 | - Type `git stash` in the terminal and press enter 1718 | 1719 | ## 1110. git stash list 1720 | 1721 | ### 1110.1 1722 | 1723 | View the list of your stashed changes again. 1724 | 1725 | #### HINTS 1726 | 1727 | - Use the "git stash list" command in your repo 1728 | - Type `git stash list` in the terminal and press enter 1729 | 1730 | ## 1113. git stash show stash@{1} 1731 | 1732 | ### 1113.1 1733 | 1734 | Now there's two things stashed. You can use the name at the front of each stash (`stash@{#}`) with many of the stash commands to select one other than the latest one. The most recent stash is the one at the top, `stash@{0}`. View the condensed changes of the **oldest** stash with the `git stash show` command by putting the name of the stash after it. 1735 | 1736 | #### HINTS 1737 | 1738 | - Add the stash name at the end of the `git stash show` command 1739 | - The stash name is `stash@{1}` 1740 | - Type `git stash show stash@{1}` in the terminal and press enter 1741 | 1742 | ## 1116. git stash show -p stash@{1} 1743 | 1744 | ### 1116.1 1745 | 1746 | Next, using a similar method, **show** the full changes of the **oldest** stash with the "patch" flag you used earlier. 1747 | 1748 | #### HINTS 1749 | 1750 | - The patch flag is `-p` 1751 | - Use the `git stash show` command with the patch flag 1752 | - Include the stash you want to view at the end of the command 1753 | - The stash you want to view is `stash@{1}` 1754 | - Type `git stash show -p stash@{1}` in the terminal and press enter 1755 | 1756 | ## 1120. git stash drop 1757 | 1758 | ### 1120.1 1759 | 1760 | There's two identical items in your stash. Drop one of them with `git stash drop` or `git stash drop `. 1761 | 1762 | #### HINTS 1763 | 1764 | - Drop one of the stashed changes with the suggested command 1765 | - Type `git stash drop` in the terminal and press enter 1766 | 1767 | ## 1130. git stash list 1768 | 1769 | ### 1130.1 1770 | 1771 | View the list of stashed changes again to verify the one got deleted. 1772 | 1773 | #### HINTS 1774 | 1775 | - Use the "git stash list" command in your repo 1776 | - Type `git stash list` in the terminal and press enter 1777 | 1778 | ## 1140. git checkout main 1779 | 1780 | ### 1140.1 1781 | 1782 | You should just have the one stash left. Switch to your `main` branch so you can create a new branch from that and add these changes to it. 1783 | 1784 | #### HINTS 1785 | 1786 | - Use the `git checkout` command 1787 | - Here's an example: `git checkout branch_name` 1788 | - Enter `git checkout main` into the terminal and press enter 1789 | 1790 | ## 1150. git branch -d feat/add-insert-row-reference 1791 | 1792 | ### 1150.1 1793 | 1794 | Before I make you work on the wrong branch again. Delete the branch for inserting a row. 1795 | 1796 | #### HINTS 1797 | 1798 | - View your branches if you need to find the name 1799 | - Use the `git branch` command with the `-d` flag 1800 | - The branch name is `feat/add-insert-row-reference` 1801 | - Here's an example: `git branch -d branch_name` 1802 | - Type `git branch -d feat/add-insert-row-reference` into the terminal and press enter 1803 | 1804 | ## 1160. git checkout feat/add-more-row-references 1805 | 1806 | ### 1160.1 1807 | 1808 | Create and checkout a new branch named `feat/add-more-row-references` for adding some more row related commands. 1809 | 1810 | #### HINTS 1811 | 1812 | - Use the "git checkout" command with the `-b` flag 1813 | - Here's an example: `git checkout -b branch_name` 1814 | - Type `git checkout -b feat/add-more-row-references` into the terminal and press enter 1815 | 1816 | ## 1170. git stash list 1817 | 1818 | ### 1170.1 1819 | 1820 | Show me your stash list again to make sure your changes from the other branch are still stashed. 1821 | 1822 | #### HINTS 1823 | 1824 | - Use the "git stash list" command in your repo 1825 | - Type `git stash list` in the terminal and press enter 1826 | 1827 | ## 1180. git stash pop 1828 | 1829 | ### 1180.1 1830 | 1831 | It's still there. Pop the stash so the code gets added to this new branch. 1832 | 1833 | #### HINTS 1834 | 1835 | - Use the "git stash pop" command in your repo 1836 | - Type `git stash pop` in the terminal and press enter 1837 | 1838 | ## 1190. git stash list 1839 | 1840 | ### 1190.1 1841 | 1842 | Git showed you your status again, and it looks like it recognizes that the file has new changes after adding the stash. View the stash list to verify that it's empty. 1843 | 1844 | #### HINTS 1845 | 1846 | - Use the "git stash list" command in your repo 1847 | - Type `git stash list` in the terminal and press enter 1848 | 1849 | ## 1210. git diff 1850 | 1851 | ### 1210.1 1852 | 1853 | The list is empty. View the diff of your changes so you can make sure they are what you expect. 1854 | 1855 | #### HINTS 1856 | 1857 | - Use the "git diff" command 1858 | - Type `git diff` into the terminal and press enter 1859 | - Make sure you are in your repo folder first 1860 | 1861 | ## 1220. git add UPDATE ROW command 1862 | 1863 | ### 1220.1 1864 | 1865 | It looks good. Add the changes to staging. 1866 | 1867 | #### HINTS 1868 | 1869 | - Use the `git add` command 1870 | - Here's an example: `git add file_name` 1871 | - You previously used `git add README.md` to add changes to staging 1872 | - Type `git add sql_reference.json` into the terminal and press enter 1873 | 1874 | ## 1230. git commit feat: add update row reference 1875 | 1876 | ### 1230.1 1877 | 1878 | View your status, then commit the staged changes with the message `feat: add update row reference`. 1879 | 1880 | #### HINTS 1881 | 1882 | - Commit changes with `git commit -m "message"` 1883 | - Type `git commit -m "feat: add update row reference"` into the terminal and press enter 1884 | - View your `git log` to see if your message is correct 1885 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 1886 | - Or, reset the lesson and try again 1887 | 1888 | ## 1240. git checkout main 1889 | 1890 | ### 1240.1 1891 | 1892 | Your work on this branch is done for now. Switch to your `main` branch so you can merge the commit you just made. 1893 | 1894 | #### HINTS 1895 | 1896 | - Use the `git checkout` command 1897 | - Here's an example: `git checkout branch_name` 1898 | - Enter `git checkout main` into the terminal and press enter 1899 | 1900 | ## 1250. git merge feat/add-more-row-references 1901 | 1902 | ### 1250.1 1903 | 1904 | Merge your branch for adding row references that you just added a commit to. 1905 | 1906 | #### HINTS 1907 | 1908 | - Use the "git merge" command 1909 | - View your branches if you need to find the name 1910 | - It's the `feat/add-more-row-references` branch 1911 | - Here's an example: `git merge branch_name` 1912 | - Type `git merge feat/add-more-row-references` into the terminal and press enter 1913 | 1914 | ## 1260. git checkout feat/add-column-references 1915 | 1916 | ### 1260.1 1917 | 1918 | Switch to your branch for the column references so you can continue working on that. 1919 | 1920 | #### HINTS 1921 | 1922 | - Use the `git checkout` command 1923 | - View your branches if you need to find the name 1924 | - Here's an example: `git checkout branch_name` 1925 | - Enter `git checkout feat/add-column-references` into the terminal and press enter 1926 | 1927 | ## 1270. git rebase main 1928 | 1929 | ### 1270.1 1930 | 1931 | Once again, commits have been added to `main` so you should update this branch. Rebase this branch against `main` to bring in the new commits. You should get a conflict. 1932 | 1933 | #### HINTS 1934 | 1935 | - Use the "git rebase" command 1936 | - Add the branch after the command that you want to rebase against 1937 | - Here's an example: `git rebase branch_name` 1938 | - Type `git rebase main` into the terminal and press enter 1939 | 1940 | ## 1280. Fix Conflicts 1941 | 1942 | ### 1280.1 1943 | 1944 | This conflict is a little trickier. Make the JSON object whole again so you can add the changes and finish rebasing. Make sure you put all the references in their correct objects, and in the same order they were originally in. There may be a duplicate line you need to delete. 1945 | 1946 | #### HINTS 1947 | 1948 | - The whole file should look like this: 1949 | ```json 1950 | { 1951 | "database": { 1952 | "create": "CREATE DATABASE database_name;", 1953 | "drop": "DROP DATABASE database_name;" 1954 | }, 1955 | "table": { 1956 | "create": "CREATE TABLE table_name();", 1957 | "drop": "DROP TABLE table_name;" 1958 | }, 1959 | "row": { 1960 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 1961 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;" 1962 | }, 1963 | "column": { 1964 | "add": "ALTER TABLE table_name ADD COLUMN column_name;" 1965 | } 1966 | } 1967 | 1968 | ``` 1969 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 1970 | - You can view the `git diff` to see if there's any extra spaces 1971 | 1972 | ## 1290. git status 1973 | 1974 | ### 1290.1 1975 | 1976 | View the status of your repo. 1977 | 1978 | #### HINTS 1979 | 1980 | - Use the "git status" command in your repo 1981 | - Type `git status` into the terminal and press enter 1982 | - Make sure you are in your `sql_reference` repo folder 1983 | 1984 | ## 1300. git add fixed conflicts 1985 | 1986 | ### 1300.1 1987 | 1988 | You are still rebasing. You fixed the conflicts for the commit trying to be added. It looks like it was the "add column" commit that had the conflict. Add your changes to staging. 1989 | 1990 | #### HINTS 1991 | 1992 | - Use the "git add" command 1993 | - Here's an example: `git add file_name` 1994 | - You previously used `git add README.md` to add changes to staging 1995 | - Type `git add sql_reference.json` into the terminal and press enter 1996 | 1997 | ## 1305. git status 1998 | 1999 | ### 1305.1 2000 | 2001 | View the status again. 2002 | 2003 | #### HINTS 2004 | 2005 | - Use the "git status" command in your repo 2006 | - Type `git status` into the terminal and press enter 2007 | - Make sure you are in your `sql_reference` repo folder 2008 | 2009 | ## 1310. git rebase continue 2010 | 2011 | ### 1310.1 2012 | 2013 | Continue your rebase with the suggested command. 2014 | 2015 | #### HINTS 2016 | 2017 | - View the output in the terminal to find the command 2018 | - It's the "git rebase continue" command 2019 | - Enter `git rebase --continue` in the terminal and press enter 2020 | 2021 | ## 1320. git log oneline 2022 | 2023 | ### 1320.1 2024 | 2025 | The rest of the commits were added without conflict. View your log with the oneline flag. 2026 | 2027 | #### HINTS 2028 | 2029 | - Use the `git log` command with the correct flag 2030 | - It's the `--oneline` flag 2031 | - Type `git log --oneline` into the terminal and press enter 2032 | 2033 | ## 1330. Add PRIMARY KEY command 2034 | 2035 | ### 1330.1 2036 | 2037 | The rebase added the "row" commits where they are supposed to be, then the "column" commits from this branch on top. Excellent. Now you can continue working on it. Add a reference to the column object for setting a column as the primary key. Give it a key of `primary_key` and a value of `"ALTER TABLE table_name ADD PRIMARY KEY(column_name);"` 2038 | 2039 | #### HINTS 2040 | 2041 | - The `column` key should look like this: 2042 | ```json 2043 | "column": { 2044 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2045 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2046 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2047 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);" 2048 | } 2049 | ``` 2050 | - The whole file should look like this: 2051 | ```json 2052 | { 2053 | "database": { 2054 | "create": "CREATE DATABASE database_name;", 2055 | "drop": "DROP DATABASE database_name;" 2056 | }, 2057 | "table": { 2058 | "create": "CREATE TABLE table_name();", 2059 | "drop": "DROP TABLE table_name;" 2060 | }, 2061 | "row": { 2062 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2063 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;" 2064 | }, 2065 | "column": { 2066 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2067 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2068 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2069 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);" 2070 | } 2071 | } 2072 | 2073 | ``` 2074 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2075 | - You can view the `git diff` to see if there's any extra spaces 2076 | 2077 | ## 1340. git diff PRIMARY KEY command 2078 | 2079 | ### 1340.1 2080 | 2081 | Check the diff to make sure you like your changes. Then, add the changes to staging. 2082 | 2083 | #### HINTS 2084 | 2085 | - Use the `git add` command 2086 | - Here's an example: `git add file_name` 2087 | - You previously used `git add README.md` to add changes to staging 2088 | - Type `git add sql_reference.json` into the terminal and press enter 2089 | 2090 | ## 1350. git commit feat: add primary key reference 2091 | 2092 | ### 1350.1 2093 | 2094 | Commit your staged files with `feat: add primary key reference` as the message. 2095 | 2096 | #### HINTS 2097 | 2098 | - Commit changes with `git commit -m "message"` 2099 | - Type `git commit -m "feat: add primary key reference"` into the terminal and press enter 2100 | - View your `git log` to see if your message is correct 2101 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 2102 | - Or, reset the lesson and try again 2103 | 2104 | ## 1352. Add FOREIGN KEY command 2105 | 2106 | ### 1352.1 2107 | 2108 | Add `foreign_key` to the `column` object for another command. It's value should be `"ALTER TABLE table_name ADD FOREIGN KEY(column_name) REFERENCES table_name(column_name);"`. 2109 | 2110 | #### HINTS 2111 | 2112 | - The `column` key should look like this: 2113 | ```json 2114 | "column": { 2115 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2116 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2117 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2118 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);", 2119 | "foreign_key": "ALTER TABLE table_name ADD FOREIGN KEY(column_name) REFERENCES table_name(column_name);" 2120 | } 2121 | ``` 2122 | - The whole file should look like this: 2123 | ```json 2124 | { 2125 | "database": { 2126 | "create": "CREATE DATABASE database_name;", 2127 | "drop": "DROP DATABASE database_name;" 2128 | }, 2129 | "table": { 2130 | "create": "CREATE TABLE table_name();", 2131 | "drop": "DROP TABLE table_name;" 2132 | }, 2133 | "row": { 2134 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2135 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;" 2136 | }, 2137 | "column": { 2138 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2139 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2140 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2141 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);", 2142 | "foreign_key": "ALTER TABLE table_name ADD FOREIGN KEY(column_name) REFERENCES table_name(column_name);" 2143 | } 2144 | } 2145 | 2146 | ``` 2147 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2148 | - You can view the `git diff` to see if there's any extra spaces 2149 | 2150 | ## 1354. git add FOREIGN command 2151 | 2152 | ### 1354.1 2153 | 2154 | Check the diff to make sure you like the changes, then add the changes to staging. 2155 | 2156 | #### HINTS 2157 | 2158 | - Use the `git add` command 2159 | - Here's an example: `git add file_name` 2160 | - You previously used `git add README.md` to add changes to staging 2161 | - Type `git add sql_reference.json` into the terminal and press enter 2162 | 2163 | ## 1356. git commit feat: add foreign key reference 2164 | 2165 | ### 1356.1 2166 | 2167 | Commit the changes with `feat: add foreign key reference` as its message. 2168 | 2169 | #### HINTS 2170 | 2171 | - Commit changes with `git commit -m "message"` 2172 | - Type `git commit -m "feat: add foreign key reference"` into the terminal and press enter 2173 | - View your `git log` to see if your message is correct 2174 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 2175 | - Or, reset the lesson and try again 2176 | 2177 | ## 1360. git checkout feat/add-more-row-references 2178 | 2179 | ### 1360.1 2180 | 2181 | Go to your branch for the row references so you can continue work on those. 2182 | 2183 | #### HINTS 2184 | 2185 | - Use the `git checkout` command 2186 | - Here's an example: `git checkout branch_name` 2187 | - Use the `git branch` command to find the name of the branch 2188 | - It's the `feat/add-more-row-references` branch 2189 | - Enter `git checkout feat/add-more-row-references` into the terminal and press enter 2190 | 2191 | ## 1370. Add DELETE ROW command 2192 | 2193 | ### 1370.1 2194 | 2195 | In your JSON file, add a `delete` key to the `row` object. Take a guess at the value, it should include the `DELETE FROM` and `WHERE` keywords. The whole value is in the hints. 2196 | 2197 | #### HINTS 2198 | 2199 | - The `row.delete` value should be `"DELETE FROM table_name WHERE condition;"` 2200 | - The `row` key should look like this: 2201 | ```json 2202 | "row": { 2203 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2204 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;", 2205 | "delete": "DELETE FROM table_name WHERE condition;" 2206 | } 2207 | ``` 2208 | - The whole file should look like this: 2209 | ```json 2210 | { 2211 | "database": { 2212 | "create": "CREATE DATABASE database_name;", 2213 | "drop": "DROP DATABASE database_name;" 2214 | }, 2215 | "table": { 2216 | "create": "CREATE TABLE table_name();", 2217 | "drop": "DROP TABLE table_name;" 2218 | }, 2219 | "row": { 2220 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2221 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;", 2222 | "delete": "DELETE FROM table_name WHERE condition;" 2223 | } 2224 | } 2225 | 2226 | ``` 2227 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2228 | - You can view the `git diff` to see if there's any extra spaces 2229 | 2230 | ## 1380. git add DELETE ROW command 2231 | 2232 | ### 1380.1 2233 | 2234 | View the diff of your changes, then add them to staging. 2235 | 2236 | #### HINTS 2237 | 2238 | - Use the `git add` command 2239 | - Here's an example: `git add file_name` 2240 | - You previously used `git add README.md` to add changes to staging 2241 | - Type `git add sql_reference.json` into the terminal and press enter 2242 | 2243 | ## 1390. git commit feat: add delete row reference 2244 | 2245 | ### 1390.1 2246 | 2247 | Commit the staged changes with the message `feat: add delete row reference`. 2248 | 2249 | #### HINTS 2250 | 2251 | - Commit changes with `git commit -m "message"` 2252 | - Type `git commit -m "feat: add delete row reference"` into the terminal and press enter 2253 | - View your `git log` to see if your message is correct 2254 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 2255 | - Or, reset the lesson and try again 2256 | 2257 | ## 1400. git checkout main 2258 | 2259 | ### 1400.1 2260 | 2261 | Go to the `main` branch so you can merge these commits. 2262 | 2263 | #### HINTS 2264 | 2265 | - Use the `git checkout` command 2266 | - Here's an example: `git checkout branch_name` 2267 | - Enter `git checkout main` into the terminal and press enter 2268 | 2269 | ## 1410. git merge feat/add-more-row-references 2270 | 2271 | ### 1410.1 2272 | 2273 | Merge the branch for the row commands into `main`. 2274 | 2275 | #### HINTS 2276 | 2277 | - Use the "git merge" command 2278 | - Here's an example: `git merge branch_name` 2279 | - Use the `git branch` command if you need to find the branch name 2280 | - It's the `feat/add-more-row-references` branch 2281 | - Type `git merge feat/add-more-row-references` into the terminal and press enter 2282 | 2283 | ## 1416. git branch -d feat/add-more-row-references 2284 | 2285 | ### 1416.1 2286 | 2287 | You merged the branch and are done with it. Delete the branch for the row references. 2288 | 2289 | #### HINTS 2290 | 2291 | - Use the `git branch` command with the `-d` flag 2292 | - Here's an example: `git branch -d branch_name` 2293 | - View your branches if you need to find the name 2294 | - The branch name is `feat/add-more-row-references` 2295 | - Type `git branch -d feat/add-more-row-references` into the terminal and press enter 2296 | 2297 | ## 1420. git checkout -b fix/add-missing-rename-references 2298 | 2299 | ### 1420.1 2300 | 2301 | I missed a bunch of the rename commands when I had you work on a few of the objects. Create and checkout a branch named `fix/add-missing-rename-references`. 2302 | 2303 | #### HINTS 2304 | 2305 | - Use the `git checkout` command with the `-b` flag 2306 | - Here's an example: `git checkout -b branch_name` 2307 | - Type `git checkout -b fix/add-missing-rename-references` into the terminal and press enter 2308 | 2309 | ## 1430. Add RENAME DATABASE command 2310 | 2311 | ### 1430.1 2312 | 2313 | I forgot to add a command for how to rename a database. In your JSON file, add a `rename` key to the `database` object. The value should be `"ALTER DATABASE database_name RENAME TO new_name;"` 2314 | 2315 | #### HINTS 2316 | 2317 | - The `database` object should look like this: 2318 | ```json 2319 | "database": { 2320 | "create": "CREATE DATABASE database_name;", 2321 | "drop": "DROP DATABASE database_name;", 2322 | "rename": "ALTER DATABASE database_name RENAME TO new_name;" 2323 | } 2324 | ``` 2325 | - The whole file should look like this: 2326 | ```json 2327 | { 2328 | "database": { 2329 | "create": "CREATE DATABASE database_name;", 2330 | "drop": "DROP DATABASE database_name;", 2331 | "rename": "ALTER DATABASE database_name RENAME TO new_name;" 2332 | }, 2333 | "table": { 2334 | "create": "CREATE TABLE table_name();", 2335 | "drop": "DROP TABLE table_name;" 2336 | }, 2337 | "row": { 2338 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2339 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;", 2340 | "delete": "DELETE FROM table_name WHERE condition;" 2341 | } 2342 | } 2343 | 2344 | ``` 2345 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2346 | - You can view the `git diff` to see if there's any extra spaces 2347 | 2348 | ## 1440. git add RENAME DATABASE command 2349 | 2350 | ### 1440.1 2351 | 2352 | View the diff of your changes to make sure you like them, then add them to staging. 2353 | 2354 | #### HINTS 2355 | 2356 | - Use the `git add` command 2357 | - Here's an example: `git add file_name` 2358 | - You previously used `git add README.md` to add changes to staging 2359 | - Type `git add sql_reference.json` into the terminal and press enter 2360 | 2361 | ## 1450. git commit fix: add missing rename database reference 2362 | 2363 | ### 1450.1 2364 | 2365 | Commit your stages changes with `fix: add missing rename database reference` for the message. 2366 | 2367 | #### HINTS 2368 | 2369 | - Commit changes with `git commit -m "message"` 2370 | - Type `git commit -m "fix: add missing rename database reference"` into the terminal and press enter 2371 | - View your `git log` to see if your message is correct 2372 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 2373 | - Or, reset the lesson and try again 2374 | 2375 | ## 1460. git checkout feat/add-column-references 2376 | 2377 | ### 1460.1 2378 | 2379 | Leave this branch for now. Switch back to your branch for the column references so you can hopefully finally finish it. 2380 | 2381 | #### HINTS 2382 | 2383 | - Use the `git checkout` command 2384 | - Here's an example: `git checkout branch_name` 2385 | - Use the `git branch` command to find the name of the branch 2386 | - It's the `feat/add-column-references` branch 2387 | - Enter `git checkout feat/add-column-references` into the terminal and press enter 2388 | 2389 | ## 1470. git rebase main 2390 | 2391 | ### 1470.1 2392 | 2393 | There was a commit to `main` since you last worked on this from when you merged the "add more row references" branch. Rebase this branch against `main` so it's up to date and you can finish working on it. 2394 | 2395 | #### HINTS 2396 | 2397 | - Use the "git rebase" command 2398 | - Add the branch after the command that you want to rebase against 2399 | - Here's an example: `git rebase branch_name` 2400 | - Type `git rebase main` into the terminal and press enter 2401 | 2402 | ## 1480. Fix Conflicts 2403 | 2404 | ### 1480.1 2405 | 2406 | Fix the conflicts so that all the commands are in their correct objects. 2407 | 2408 | #### HINTS 2409 | 2410 | - Be sure to delete any special characters 2411 | - The order of the keys should be: 2412 | ```json 2413 | { 2414 | "database": {}, 2415 | "table": {}, 2416 | "row": {}, 2417 | "column": {} 2418 | } 2419 | ``` 2420 | - The whole file should look like this: 2421 | ```json 2422 | { 2423 | "database": { 2424 | "create": "CREATE DATABASE database_name;", 2425 | "drop": "DROP DATABASE database_name;" 2426 | }, 2427 | "table": { 2428 | "create": "CREATE TABLE table_name();", 2429 | "drop": "DROP TABLE table_name;" 2430 | }, 2431 | "row": { 2432 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2433 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;", 2434 | "delete": "DELETE FROM table_name WHERE condition;" 2435 | }, 2436 | "column": { 2437 | "add": "ALTER TABLE table_name ADD COLUMN column_name;" 2438 | } 2439 | } 2440 | 2441 | ``` 2442 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2443 | - You can view the `git diff` to see if there's any extra spaces 2444 | 2445 | ## 1490. git add Fixed Conflicts 2446 | 2447 | ### 1490.1 2448 | 2449 | You fixed the conflicts. Check your status, then add your files to staging. 2450 | 2451 | #### HINTS 2452 | 2453 | - Use the `git add` command 2454 | - Here's an example: `git add file_name` 2455 | - You previously used `git add README.md` to add changes to staging 2456 | - Type `git add sql_reference.json` into the terminal and press enter 2457 | 2458 | ## 1495. git status 2459 | 2460 | ### 1495.1 2461 | 2462 | Check your status again. 2463 | 2464 | #### HINTS 2465 | 2466 | - Use the "git status" command in your repo 2467 | - Type `git status` into the terminal and press enter 2468 | - Make sure you are in your `sql_reference` repo folder 2469 | 2470 | ## 1500. git rebase continue 2471 | 2472 | ### 1500.1 2473 | 2474 | Use the suggested command to continue your rebase. 2475 | 2476 | #### HINTS 2477 | 2478 | - View the output in the terminal to find the command 2479 | - It's the "git rebase continue" command 2480 | - Enter `git rebase --continue` in the terminal and press enter 2481 | 2482 | ## 1510. Add UNIQUE command 2483 | 2484 | ### 1510.1 2485 | 2486 | There was a conflict when it tried to add the first commit from this branch on top of the one that was brought in from `main`. The rest of the commits were added without conflicts. In your JSON file, add a `unique` key to the `column` object. Give it a value of `"ALTER TABLE table_name ADD UNIQUE(column_name);"` 2487 | 2488 | #### HINTS 2489 | 2490 | - The should be `"unique": "ALTER TABLE table_name ADD UNIQUE(column_name);"` in your `column` object 2491 | - The `column` object should look like this: 2492 | ```json 2493 | "column": { 2494 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2495 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2496 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2497 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);", 2498 | "foreign_key": "ALTER TABLE table_name ADD FOREIGN KEY(column_name) REFERENCES table_name(column_name);", 2499 | "unique": "ALTER TABLE table_name ADD UNIQUE(column_name);" 2500 | } 2501 | ``` 2502 | - The whole file should look like this: 2503 | ```json 2504 | { 2505 | "database": { 2506 | "create": "CREATE DATABASE database_name;", 2507 | "drop": "DROP DATABASE database_name;" 2508 | }, 2509 | "table": { 2510 | "create": "CREATE TABLE table_name();", 2511 | "drop": "DROP TABLE table_name;" 2512 | }, 2513 | "row": { 2514 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2515 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;", 2516 | "delete": "DELETE FROM table_name WHERE condition;" 2517 | }, 2518 | "column": { 2519 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2520 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2521 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2522 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);", 2523 | "foreign_key": "ALTER TABLE table_name ADD FOREIGN KEY(column_name) REFERENCES table_name(column_name);", 2524 | "unique": "ALTER TABLE table_name ADD UNIQUE(column_name);" 2525 | } 2526 | } 2527 | 2528 | ``` 2529 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2530 | - You can view the `git diff` to see if there's any extra spaces 2531 | 2532 | ## 1520. git add UNIQUE command 2533 | 2534 | ### 1520.1 2535 | 2536 | View the diff to make sure you like the changes, then add the changes to staging. 2537 | 2538 | #### HINTS 2539 | 2540 | - Use the `git add` command 2541 | - Here's an example: `git add file_name` 2542 | - You previously used `git add README.md` to add changes to staging 2543 | - Type `git add sql_reference.json` into the terminal and press enter 2544 | 2545 | ## 1530. git commit feat: add unique reference 2546 | 2547 | ### 1530.1 2548 | 2549 | Commit the stages files with `feat: add unique reference` for the message. 2550 | 2551 | #### HINTS 2552 | 2553 | - Commit changes with `git commit -m "message"` 2554 | - Type `git commit -m "feat: add unique reference"` into the terminal and press enter 2555 | - View your `git log` to see if your message is correct 2556 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 2557 | - Or, reset the lesson and try again 2558 | 2559 | ## 1533. git reset HEAD~1 2560 | 2561 | ### 1533.1 2562 | 2563 | I'm going to show you a few ways to remove or undo a commit. The first is to simply "travel back in time". You can use the `git reset` command to travel to any point in your commit history. Your current `HEAD` is a reference to the last commit you just made. Use `git reset HEAD~1` to go back one before `HEAD`. 2564 | 2565 | #### HINTS 2566 | 2567 | - Enter `git reset HEAD~1` in the terminal 2568 | 2569 | ## 1536. git log oneline 2570 | 2571 | ### 1536.1 2572 | 2573 | This is a "mixed" reset and will put the changes from the commit you undid in your working tree. You can see that it says there's unstaged changes after the reset to your file. View your log with the oneline flag. 2574 | 2575 | #### HINTS 2576 | 2577 | - Use the `git log` command with the correct flag 2578 | - It's the `--oneline` flag 2579 | - Type `git log --oneline` into the terminal and press enter 2580 | 2581 | ## 1539. git status 2582 | 2583 | ### 1539.1 2584 | 2585 | Your commit for how to set a column to unique is gone. View your status. 2586 | 2587 | #### HINTS 2588 | 2589 | - Use the "git status" command in your repo 2590 | - Type `git status` into the terminal and press enter 2591 | - Make sure you are in your `sql_reference` repo folder 2592 | 2593 | ## 1540. git diff 2594 | 2595 | ### 1540.1 2596 | 2597 | View the diff. 2598 | 2599 | #### HINTS 2600 | 2601 | - Use the "git diff" command 2602 | - Type `git diff` into the terminal and press enter 2603 | 2604 | ## 1542. git add UNIQUE command 2605 | 2606 | ### 1542.1 2607 | 2608 | And the changes from the reset are back in the working tree. So when you `reset` to one commit before `HEAD`, it removed the most recent commit, and put all the changes in the working tree. If you used the `--hard` flag with the reset, the changes would have not been added to the working tree and if you used the `--soft` flag, the changes would have been added to the working tree and to staging. Add the changes back to staging so you can commit them again. 2609 | 2610 | #### HINTS 2611 | 2612 | - Use the `git add` command 2613 | - Here's an example: `git add file_name` 2614 | - You previously used `git add README.md` to add changes to staging 2615 | - Type `git add sql_reference.json` into the terminal and press enter 2616 | 2617 | ## 1545. git commit feat: add unique reference 2618 | 2619 | ### 1545.1 2620 | 2621 | Commit the change staged files with `feat: add unique reference` for its message. 2622 | 2623 | #### HINTS 2624 | 2625 | - Commit changes with `git commit -m "message"` 2626 | - Type `git commit -m "feat: add unique reference"` into the terminal and press enter 2627 | - View your `git log` to see if your message is correct 2628 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 2629 | - Or, reset the lesson and try again 2630 | 2631 | ## 1548. git revert HEAD 2632 | 2633 | ### 1548.1 2634 | 2635 | Reverting is a good way to undo a commit because you don't lose the commit from the history. You can revert the most recent commit (`HEAD`) with `git revert HEAD`. Do that now. 2636 | 2637 | #### HINTS 2638 | 2639 | - Enter the suggested command 2640 | - Enter `git revert HEAD` in the terminal 2641 | 2642 | ## 1549. Nano: Enter git revert HEAD Message 2643 | 2644 | ### 1549.1 2645 | 2646 | Git put you into Nano and is asking you enter a commit message for the revert, but they added a default one for you. Don't change anything in Nano, just exit the file to use the default message. You can exit the file by pressing `ctrl+x`. 2647 | 2648 | #### HINTS 2649 | 2650 | - Exit the file by pressing `ctrl+x` 2651 | - If you accidentally changed something in Nano, press `n` after `ctrl+x` to discard the changes 2652 | - Your last commit message should be `Revert "feat: add unique reference"` 2653 | - View your log to make sure the message is correct 2654 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git revert HEAD` after it's done resetting 2655 | 2656 | ## 1551. git log oneline 2657 | 2658 | ### 1551.1 2659 | 2660 | View the log with that flag I like again. 2661 | 2662 | #### HINTS 2663 | 2664 | - Use the `git log` command with the correct flag 2665 | - It's the `--oneline` flag 2666 | - Type `git log --oneline` into the terminal and press enter 2667 | - Press enter until you have seen the whole log 2668 | 2669 | ## 1554. git show 2670 | 2671 | ### 1554.1 2672 | 2673 | Using revert to undo that commit added another commit that is the exact opposite of it. Enter `git show` into the terminal to see the last commit added (now `HEAD`) and its details. 2674 | 2675 | #### HINTS 2676 | 2677 | - Enter the suggested command 2678 | - Type `git show` in the terminal and press enter 2679 | - Press enter until you have seen the whole message 2680 | 2681 | ## 1557. git show HEAD~1 2682 | 2683 | ### 1557.1 2684 | 2685 | Type `git show HEAD~1` to take a look at the details of the original commit that you reverted. 2686 | 2687 | #### HINTS 2688 | 2689 | - Enter the suggested command 2690 | - Type `git show` in the terminal and press enter 2691 | 2692 | ## 1560. git rebase interactive HEAD~2 2693 | 2694 | ### 1560.1 2695 | 2696 | If you look at the bottom of those two messages, it shows the diff. The diff of the revert commit is the exact opposite of the one before it. Effectively, undoing the changes. You've used rebase to update this branch, but you can enter an "interactive" mode to manipulate commits. Type `git rebase --interactive HEAD~2` into the terminal to enter this mode. The `HEAD~2` means you will have a chance to change the last two commits. 2697 | 2698 | #### HINTS 2699 | 2700 | - Enter the suggested command 2701 | - Type `git rebase --interactive HEAD~2` into the terminal and press enter 2702 | - If you entered the wrong command, save and exit Nano. Then try again 2703 | - You can save and exit Nano by pressing `ctrl+x` then `y` then `enter` 2704 | 2705 | ## 1563. Nano: Drop UNIQUE commits 2706 | 2707 | ### 1563.1 2708 | 2709 | At the top of Nano, you can see the two commits with `pick` next to them. Below them, there's a list of options for working with them. `pick` means that it will use the commits as they were. At the bottom, it says, `d, drop = remove commit`. Replace the word `pick` preceeding your two commits with a `d` to drop them both. When you are done, save the file and exit Nano. 2710 | 2711 | #### HINTS 2712 | 2713 | - You can save and exit Nano by pressing `ctrl+x` then `y` then `enter` 2714 | - The most recent commit message should be `feat: add foreign key reference` 2715 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~2` after it's done resetting 2716 | 2717 | ## 1564. git log oneline 2718 | 2719 | ### 1564.1 2720 | 2721 | View your log. Use the `--oneline` flag. 2722 | 2723 | #### HINTS 2724 | 2725 | - Use the `git log` command with the correct flag 2726 | - It's the `--oneline` flag 2727 | - Type `git log --oneline` into the terminal and press enter 2728 | - Press enter until you have seen the whole history 2729 | 2730 | ## 1567. git rebase interactive root 2731 | 2732 | ### 1567.1 2733 | 2734 | Both, the commit to add the unique command and the one to revert it, were dropped. Enter another `--interactive` rebase that goes back to the `--root` instead of `HEAD~2`. I am going to show you how to change a commit message. `--root` means that the rebase will go back to your very first commit. 2735 | 2736 | #### HINTS 2737 | 2738 | - The command is `git rebase` with two arguments 2739 | - The two arguments are `--interactive` and `--root` 2740 | - Enter `git rebase --interactive --root` into the terminal and press enter 2741 | 2742 | ## 1570. Nano: Select Reword Column References Commit 2743 | 2744 | ### 1570.1 2745 | 2746 | You can see that the latest commit is at the bottom here. Be careful not to change the wrong commits. One of the options is `r, reword = use commit, but edit the commit message`. Replace `pick` with an `r` next to the commit with the message `feat: add column reference` to reword the message, it's the very first commit you added to this branch. When you are done, save the file and exit Nano. Git will put you in another Nano instance to reword the commit message. Don't change anything in it yet. 2747 | 2748 | #### HINTS 2749 | 2750 | - Replace `pick` with an `r` next to the suggested commit 2751 | - Save and exit the file by pressing `ctrl+x` then `y` then `enter` 2752 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive --root` after it's done resetting 2753 | 2754 | ## 1572. Nano: Change Column References Commit Message 2755 | 2756 | ### 1572.1 2757 | 2758 | Git is waiting for you to edit the commit message. Add an `s` at the end of the commit message so it is `feat: add column references`. When you are done, save the file and exit Nano. 2759 | 2760 | #### HINTS 2761 | 2762 | - Save and exit the file by pressing `ctrl+x` then `y` then `enter` 2763 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive --root` after it's done resetting. Then, in nano, replace `pick` with an `r` next to the `feat: add column reference` commit, and save and exit 2764 | 2765 | ## 1575. git log oneline 2766 | 2767 | ### 1575.1 2768 | 2769 | View your log. Use the `--oneline` flag. 2770 | 2771 | #### HINTS 2772 | 2773 | - Use the `git log` command with the correct flag 2774 | - It's the `--oneline` flag 2775 | - Type `git log --oneline` into the terminal and press enter 2776 | - Press enter until you have seen the whole history 2777 | 2778 | ## 1576. git rebase main 2779 | 2780 | ### 1576.1 2781 | 2782 | The message was reworded, but there's a problem. Look at the commit hash for your `Initial commit` from the last two times you viewed the log, it's that string left of the log. They aren't the same anymore since you rebased back to the root. Same goes for the rest of the commits. When you rebase interactively it changes all those hashes, so git sees them as different commits. If you were to try and merge this into `main`, it wouldn't work because they don't share the same history anymore. For this reason, you don't want to do an interactive rebase where you go back passed commits unique to the branch you are on. Fortunately, you can fix this. Enter `git rebase main` to realign the history of the two branches. 2783 | 2784 | #### HINTS 2785 | 2786 | - Use the "git rebase" command 2787 | - Add the branch after the command that you want to rebase against 2788 | - Here's an example: `git rebase branch_name` 2789 | - Type `git rebase main` into the terminal and press enter 2790 | 2791 | ## 1578. git log oneline 2792 | 2793 | ### 1578.1 2794 | 2795 | View your log again. Use the `--oneline` flag. 2796 | 2797 | #### HINTS 2798 | 2799 | - Use the `git log` command with the correct flag 2800 | - It's the `--oneline` flag 2801 | - Type `git log --oneline` into the terminal and press enter 2802 | 2803 | ## 1580. git rebase interactive HEAD~5 2804 | 2805 | ### 1580.1 2806 | 2807 | Now the hashes are the same as they were before you rebased back to `--root`, which is what they are on `main`. Enter another interactive rebase. Go back to the first commit you added to this branch, it's `HEAD~5`. 2808 | 2809 | #### HINTS 2810 | 2811 | - It's the `git rebase` command with two arguments 2812 | - The two arguments are `--interactive` and `HEAD~5` 2813 | - Enter `git rebase --interactive HEAD~5` into the terminal and press enter 2814 | - If you entered the wrong command, exit nano without changing anything. Then try again. 2815 | - You can exit nano by pressing `ctrl+x` 2816 | - If you accidentally changed something in Nano, press `n` after `ctrl+x` to discard the changes 2817 | 2818 | ## 1590. Nano: Squash feat/add-column-references Commits 2819 | 2820 | ### 1590.1 2821 | 2822 | Squashing commits means that you will take a bunch of commits and turn them into one. This is helpful to keep your commit history clean and something you want try to do. Replace `pick` with an `s` next to all your commits except the one with the message `feat: add column references`. When you are done, save and exit the file. You will find yourself in another instance of Nano. Don't change anything in it yet. 2823 | 2824 | #### HINTS 2825 | 2826 | - Replace `pick` with an `s` next to the suggested commits 2827 | - Save and exit the file by pressing `ctrl+x` then `y` then `enter` 2828 | - The most recent commit message should be `feat: add column references` 2829 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~5` after it's done resetting 2830 | 2831 | ## 1595. Nano: Save and Exit to Squash 2832 | 2833 | ### 1595.1 2834 | 2835 | Nano brought up a list of all the commit messages you used for the commits. Don't change anything in there, just exit the file to use those messages and finish squashing the commits. 2836 | 2837 | #### HINTS 2838 | 2839 | - Press `ctrl+x` to exit the file 2840 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~5` after it's done resetting. Then, in nano, replace `pick` with an `s` next to all the commits except the `feat: add column reference` commit, and save and exit 2841 | 2842 | ## 1600. git log oneline 2843 | 2844 | ### 1600.1 2845 | 2846 | View your log with the oneline flag. 2847 | 2848 | #### HINTS 2849 | 2850 | - Use the `git log` command with the correct flag 2851 | - It's the `--oneline` flag 2852 | - Type `git log --oneline` into the terminal and press enter 2853 | 2854 | ## 1610. git log -1 2855 | 2856 | ### 1610.1 2857 | 2858 | Now all the "column" commits you made to this branch have been squashed into just the one commit at the top. View the log again, but use `-1` instead of `--oneline` this time to view only the last commit. 2859 | 2860 | #### HINTS 2861 | 2862 | - Use `git log` with the suggested argument 2863 | - Type `git log -1` into the terminal and press enter 2864 | 2865 | ## 1620. git checkout main 2866 | 2867 | ### 1620.1 2868 | 2869 | You can see that your one commit has all the messages that were in Nano, which are all of the commits you made to this branch squashed into one commit. I think you are finally done with this branch. Go to your `main` branch so it can get merged. 2870 | 2871 | #### HINTS 2872 | 2873 | - Use the `git checkout` command 2874 | - Here's an example: `git checkout branch_name` 2875 | - Enter `git checkout main` into the terminal and press enter 2876 | 2877 | ## 1630. git merge feat/add-column-references 2878 | 2879 | ### 1630.1 2880 | 2881 | Merge your branch for adding column commands into this one. 2882 | 2883 | #### HINTS 2884 | 2885 | - Use the `git merge` command with the branch name after it 2886 | - Here's an example: `git merge branch_name` 2887 | - Use the `git branch` command if you need to find the branch name 2888 | - It's the `feat/add-column-references` branch 2889 | - Type `git merge feat/add-column-references` into the terminal and press enter 2890 | - If you got `fatal: refusing to merge unrelated histories`, you need to switch back to the feature branch, enter `git rebase main` to align the histories, then come back to `main` and try again 2891 | 2892 | ## 1635. git branch -d feat/add-column-references 2893 | 2894 | ### 1635.1 2895 | 2896 | Hopefully, there were no conflicts. Delete your branch for adding information about column commands since you are done with it. 2897 | 2898 | #### HINTS 2899 | 2900 | - Use the `git branch` command with the `-d` flag 2901 | - Here's an example: `git branch -d branch_name` 2902 | - View your branches if you need to find the name 2903 | - The branch name is `feat/add-column-references` 2904 | - Type `git branch -d feat/add-column-references` into the terminal and press enter 2905 | 2906 | ## 1640. git checkout fix/add-missing-rename-references 2907 | 2908 | ### 1640.1 2909 | 2910 | Go to your branch for adding the commands that were missing. There's one more to add. 2911 | 2912 | #### HINTS 2913 | 2914 | - Use the `git checkout` command 2915 | - Here's an example: `git checkout branch_name` 2916 | - Use the `git branch` command to find the name of the branch 2917 | - It's the `fix/add-missing-rename-references` branch 2918 | - Enter `git checkout fix/add-missing-rename-references` into the terminal and press enter 2919 | 2920 | ## 1650. git rebase main 2921 | 2922 | ### 1650.1 2923 | 2924 | There was added a commit to `main` since you last worked on this. Update this branch with a rebase against main. 2925 | 2926 | #### HINTS 2927 | 2928 | - Use the "git rebase" command 2929 | - Add the branch after the command that you want to rebase against 2930 | - Here's an example: `git rebase branch_name` 2931 | - Type `git rebase main` into the terminal and press enter 2932 | 2933 | ## 1680. git log -5 oneline 2934 | 2935 | ### 1680.1 2936 | 2937 | You viewed the most recent log with a `-1` flag. You can view the last `x` number of commits with any number instead of `1`. View the last five commits with the oneline flag. 2938 | 2939 | #### HINTS 2940 | 2941 | - Use the `git log` command with the correct two arguments 2942 | - The two arguments are `-5` and `--oneline` 2943 | - Type `git log -5 --oneline` into the terminal and press enter 2944 | 2945 | ## 1690. Add RENAME TABLE Command 2946 | 2947 | ### 1690.1 2948 | 2949 | This branch is up to date now. In your JSON file, add a `rename` key to the `table` object. The value is in the hints, but give it a try first. It follows a similar structure as the rest of them. 2950 | 2951 | #### HINTS 2952 | 2953 | - The value is `"ALTER TABLE table_name RENAME TO new_name;"` 2954 | - The `table` object should look like this: 2955 | ```json 2956 | { 2957 | "create": "CREATE TABLE table_name();", 2958 | "drop": "DROP TABLE table_name;", 2959 | "rename": "ALTER TABLE table_name RENAME TO new_name;" 2960 | } 2961 | ``` 2962 | - The whole file should look like this: 2963 | ```json 2964 | { 2965 | "database": { 2966 | "create": "CREATE DATABASE database_name;", 2967 | "drop": "DROP DATABASE database_name;", 2968 | "rename": "ALTER DATABASE database_name RENAME TO new_name;" 2969 | }, 2970 | "table": { 2971 | "create": "CREATE TABLE table_name();", 2972 | "drop": "DROP TABLE table_name;", 2973 | "rename": "ALTER TABLE table_name RENAME TO new_name;" 2974 | }, 2975 | "row": { 2976 | "insert": "INSERT INTO table_name(columns) VALUES(values);", 2977 | "update": "UPDATE table_name SET column_name = new_value WHERE condition;", 2978 | "delete": "DELETE FROM table_name WHERE condition;" 2979 | }, 2980 | "column": { 2981 | "add": "ALTER TABLE table_name ADD COLUMN column_name;", 2982 | "drop": "ALTER TABLE table_name DROP COLUMN column_name;", 2983 | "rename": "ALTER TABLE table_name RENAME COLUMN column_name TO new_name;", 2984 | "primary_key": "ALTER TABLE table_name ADD PRIMARY KEY(column_name);", 2985 | "foreign_key": "ALTER TABLE table_name ADD FOREIGN KEY(column_name) REFERENCES table_name(column_name);" 2986 | } 2987 | } 2988 | 2989 | ``` 2990 | - Make sure there's one empty line at the bottom of the file and no extra spaces after any of the values or curly brackets 2991 | - You can view the `git diff` to see if there's any extra spaces 2992 | 2993 | ## 1700. git add RENAME TABLE command 2994 | 2995 | ### 1700.1 2996 | 2997 | Check the diff of your changes, then add them changes to staging. 2998 | 2999 | #### HINTS 3000 | 3001 | - Use the `git add` command 3002 | - Here's an example: `git add file_name` 3003 | - You previously used `git add README.md` to add changes to staging 3004 | - Type `git add sql_reference.json` into the terminal and press enter 3005 | 3006 | ## 1710. git commit fix: add missing rename table reference 3007 | 3008 | ### 1710.1 3009 | 3010 | Commit your staged changes with the message, `fix: add missing rename table reference`. 3011 | 3012 | #### HINTS 3013 | 3014 | - Commit changes with `git commit -m "message"` 3015 | - Type `git commit -m "fix: add missing rename table reference"` into the terminal and press enter 3016 | - View your `git log` to see if your message is correct 3017 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 3018 | - Or, reset the lesson and try again 3019 | 3020 | ## 1715. git log -5 oneline 3021 | 3022 | ### 1715.1 3023 | 3024 | View your last five logs with the oneline flag again. 3025 | 3026 | #### HINTS 3027 | 3028 | - Use the `git log` command with the correct flag 3029 | - It's the `--oneline` flag 3030 | - Use `-5` with your `git log --oneline` command 3031 | - Type `git log --oneline -5` into the terminal and press enter 3032 | 3033 | ## 1720. git rebase interactive HEAD~2 3034 | 3035 | ### 1720.1 3036 | 3037 | You have two commits on this branch that could be squashed. Enter an interactive rebase that goes back to `HEAD~2` so you can squash them. 3038 | 3039 | #### HINTS 3040 | 3041 | - It's the `git rebase` command with two arguments 3042 | - The two arguments and `--interactive` and `HEAD~2` 3043 | - Enter `git rebase --interactive HEAD~2` into the terminal and press enter 3044 | - If you entered the wrong command, save and exit nano without changing anything. Then try again 3045 | - You can save and exit nano by pressing `ctrl+x` then `y` then `enter` 3046 | 3047 | ## 1730. Nano: Squash feat/add-missing-rename-references Commits 3048 | 3049 | ### 1730.1 3050 | 3051 | Replace `pick` with `s` next to your commit for adding the rename table reference to squash it. Be careful not to do the wrong one. When you are done, save and exit Nano. 3052 | 3053 | #### HINTS 3054 | 3055 | - Replace `pick` with `s` next to your `fix: add missing rename table reference` commit 3056 | - You can save and exit nano by pressing `ctrl+x` then `y` then `enter` 3057 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~2` after it's done resetting 3058 | 3059 | ## 1735. Nano: Add Missing Renames Commit Message 3060 | 3061 | ### 1735.1 3062 | 3063 | The lines that don't start with a `#` will be the commit messages. Add a new message at the top of the file on it's own line. Give it the text, `fix: add missing rename references`. When you are done, save and exit the file. 3064 | 3065 | #### HINTS 3066 | 3067 | - You can save and exit nano by pressing `ctrl+x` then `y` then `enter` 3068 | - The most recent commit message should be `fix: add missing rename references` 3069 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~2` after it's done resetting. Then, in nano, replace `pick` with `s` next to your `fix: add missing rename table reference` commit, and save and exit 3070 | 3071 | ## 1737. git log -1 3072 | 3073 | ### 1737.1 3074 | 3075 | View only the last commit in your log to see your squashed commit. 3076 | 3077 | #### HINTS 3078 | 3079 | - Use the `git log` command 3080 | - View the last `x` number of commits with `-x` 3081 | - Use `-1` with the command 3082 | - Type `git log -1` into the terminal and press enter 3083 | 3084 | ## 1740. git checkout main 3085 | 3086 | ### 1740.1 3087 | 3088 | I think this branch is ready to go. Switch to `main` so you can merge it. 3089 | 3090 | #### HINTS 3091 | 3092 | - Use the `git checkout` command 3093 | - Here's an example: `git checkout branch_name` 3094 | - Enter `git checkout main` into the terminal and press enter 3095 | 3096 | ## 1750. git merge fix/add-missing-rename-references 3097 | 3098 | ### 1750.1 3099 | 3100 | Merge your branch for adding the rename commands into `main`. 3101 | 3102 | #### HINTS 3103 | 3104 | - Use the `git merge` command with the branch name after it 3105 | - Here's an example: `git merge branch_name` 3106 | - Use the `git branch` command if you need to find the branch name 3107 | - It's the `fix/add-missing-rename-references` branch 3108 | - Type `git merge fix/add-missing-rename-references` into the terminal and press enter 3109 | 3110 | ## 1760. git branch 3111 | 3112 | ### 1760.1 3113 | 3114 | View your branches. 3115 | 3116 | #### HINTS 3117 | 3118 | - Use `git branch` to view your branches 3119 | - Make sure you are in your `sql_reference` repo folder 3120 | 3121 | ## 1770. git branch -d all but main 3122 | 3123 | ### 1770.1 3124 | 3125 | Delete all your branches except `main`. 3126 | 3127 | #### HINTS 3128 | 3129 | - Use the `git branch` command with the `-d` flag 3130 | - Here's an example: `git branch -d branch_name` 3131 | - The branch name is `fix/add-missing-rename-references` 3132 | - Type `git branch -d fix/add-missing-rename-references` into the terminal and press enter 3133 | 3134 | ## 1780. git log oneline 3135 | 3136 | ### 1780.1 3137 | 3138 | I think the file is complete, thanks for making this for me. View the log with the oneline flag. 3139 | 3140 | #### HINTS 3141 | 3142 | - Use the `git log` command with the correct flag 3143 | - It's the `--oneline` flag 3144 | - Type `git log --oneline` into the terminal and press enter 3145 | 3146 | ## 1790. git checkout -b feat/add-gitignore 3147 | 3148 | ### 1790.1 3149 | 3150 | That's a nice looking commit history. There's one more thing you should learn. Create and checkout a branch named `feat/add-gitignore`. 3151 | 3152 | #### HINTS 3153 | 3154 | - Use the `git checkout` command with the `-b` flag 3155 | - Here's an example: `git checkout -b branch_name` 3156 | - Type `git checkout -b feat/add-gitignore` into the terminal and press enter 3157 | 3158 | ## 1800. touch .env 3159 | 3160 | ### 1800.1 3161 | 3162 | Use the `touch` command to create a file named `.env` in your repo. 3163 | 3164 | #### HINTS 3165 | 3166 | - Use `touch file_name` to create a file 3167 | - Type `touch .env` into the terminal and press enter 3168 | - Don't try to create the file with another method 3169 | - Make sure you are in your `sql_reference` repo folder 3170 | 3171 | ## 1810. Add SECRETS to .env 3172 | 3173 | ### 1810.1 3174 | 3175 | `.env` files are used to store environment variables for running code. Often times, there may be sensitive information in it. Add the text `SECRET=MY_SECRET` to the file. 3176 | 3177 | #### HINTS 3178 | 3179 | - Add the suggested text to the `.env` file 3180 | - Add `SECRET=MY_SECRET` to the `.env` file 3181 | - Make sure there's nothing else in the file 3182 | 3183 | ## 1820. git status 3184 | 3185 | ### 1820.1 3186 | 3187 | View your status. 3188 | 3189 | #### HINTS 3190 | 3191 | - Use the "git status" command in your repo 3192 | - Type `git status` into the terminal and press enter 3193 | - Make sure you are in your `sql_reference` repo folder 3194 | 3195 | ## 1830. touch .gitignore 3196 | 3197 | ### 1830.1 3198 | 3199 | You can see the `.env` file is new. Use `touch` again to create another file named `.gitignore` in your repo. 3200 | 3201 | #### HINTS 3202 | 3203 | - Use `touch file_name` to create a file 3204 | - Type `touch .gitignore` into the terminal and press enter 3205 | - Don't try to create the file with another method 3206 | - Make sure you are in your `sql_reference` repo folder 3207 | 3208 | ## 1835. git status 3209 | 3210 | ### 1835.1 3211 | 3212 | View the status again. 3213 | 3214 | #### HINTS 3215 | 3216 | - Use the "git status" command in your repo 3217 | - Type `git status` into the terminal and press enter 3218 | - Make sure you are in your `sql_reference` repo folder 3219 | 3220 | ## 1840. Add .env to .gitignore 3221 | 3222 | ### 1840.1 3223 | 3224 | Now there's two new files that aren't tracked yet. Add the text `.env` to your `.gitignore` file. 3225 | 3226 | #### HINTS 3227 | 3228 | - Add `.env` to the `.gitignore` file 3229 | - Make sure there's nothing else in the file 3230 | 3231 | ## 1850. git status 3232 | 3233 | ### 1850.1 3234 | 3235 | View the status again. 3236 | 3237 | #### HINTS 3238 | 3239 | - Use the "git status" command in your repo 3240 | - Type `git status` into the terminal and press enter 3241 | - Make sure you are in your `sql_reference` repo folder 3242 | 3243 | ## 1860. git add .gitignore 3244 | 3245 | ### 1860.1 3246 | 3247 | Now the `.env` file is being ignored by git because you added it to the `.gitignore` file. There are often a number of things you don't want to include in a repository, especially if it's publicly visible. Now, you know how to keep them from being tracked by git. Add your new changes to staging. 3248 | 3249 | #### HINTS 3250 | 3251 | - Use the `git add` command 3252 | - Here's an example: `git add file_name` 3253 | - You previously used `git add sql_reference.json` to add changes to staging 3254 | - Type `git add .gitignore` into the terminal and press enter 3255 | 3256 | ## 1870. git commit feat: add .gitignore 3257 | 3258 | ### 1870.1 3259 | 3260 | Commit your changes with `feat: add .gitignore` for the message. 3261 | 3262 | #### HINTS 3263 | 3264 | - Commit changes with `git commit -m "message"` 3265 | - Type `git commit -m "feat: add .gitignore"` into the terminal and press enter 3266 | - View your `git log` to see if your message is correct 3267 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 3268 | - Or, reset the lesson and try again 3269 | 3270 | ## 1880. touch sample.env 3271 | 3272 | ### 1880.1 3273 | 3274 | Use touch to create another file named `sample.env` in your repo. 3275 | 3276 | #### HINTS 3277 | 3278 | - Use `touch file_name` to create a file 3279 | - Type `touch sample.env` into the terminal and press enter 3280 | - Don't try to create the file with another method 3281 | - Make sure you are in your `sql_reference` repo folder 3282 | 3283 | ## 1890. git status 3284 | 3285 | ### 1890.1 3286 | 3287 | View the status. 3288 | 3289 | #### HINTS 3290 | 3291 | - Use the "git status" command in your repo 3292 | - Type `git status` into the terminal and press enter 3293 | - Make sure you are in your `sql_reference` repo folder 3294 | 3295 | ## 1900. Add SECRET= to sample.env 3296 | 3297 | ### 1900.1 3298 | 3299 | Git won't ignore this file. Sensitive information can be stored in the `.env` file, but people need to know the variables that are in there so they can run a repository locally. Add `SECRET=` to `sample.env`. 3300 | 3301 | #### HINTS 3302 | 3303 | - Add the suggested text to the `sample.env` file 3304 | 3305 | ## 1930. git add sample.env 3306 | 3307 | ### 1930.1 3308 | 3309 | Now, when someone wants to run your repo, they will know that they need to create a `.env` file and add a value in it for `SECRET`. Add your new file to staging. 3310 | 3311 | #### HINTS 3312 | 3313 | - Use the `git add` command 3314 | - Here's an example: `git add file_name` 3315 | - You previously used `git add sql_reference.json` to add changes to staging 3316 | - Type `git add sample.env` into the terminal and press enter 3317 | 3318 | ## 1940. git commit feat: add sample.env 3319 | 3320 | ### 1940.1 3321 | 3322 | Commit the new changes with the message `feat: add sample.env`. 3323 | 3324 | #### HINTS 3325 | 3326 | - Commit changes with `git commit -m "message"` 3327 | - Type `git commit -m "feat: add sample.env"` into the terminal and press enter 3328 | - View your `git log` to see if your message is correct 3329 | - If the message is wrong, enter `git reset HEAD~1`, then `git add .`, and then you can try to make the commit again 3330 | - Or, reset the lesson and try again 3331 | 3332 | ## 1945. git log -5 oneline 3333 | 3334 | ### 1945.1 3335 | 3336 | View the last five commits in your log with the oneline flag. 3337 | 3338 | #### HINTS 3339 | 3340 | - Use the `git log` command with two flags 3341 | - Use `-5` and `--oneline` with the command 3342 | - Type `git log -5 --oneline` into the terminal and press enter 3343 | 3344 | ## 1950. git rebase HEAD~2 3345 | 3346 | ### 1950.1 3347 | 3348 | The two commits you made to this branch can be squashed. Do an interactive rebase that goes back to all the commits unique to this branch (`HEAD~2`). 3349 | 3350 | #### HINTS 3351 | 3352 | - It's the `git rebase` command with two arguments 3353 | - Use `--interactive` and `HEAD~2` with the command 3354 | - Enter `git rebase --interactive HEAD~2` into the terminal and press enter 3355 | 3356 | ## 1960. Nano: Squash feat/add-gitignore Commits 3357 | 3358 | ### 1960.1 3359 | 3360 | Squash your commit that was for adding the `sample.env` file. When you are done, save the file and exit Nano. 3361 | 3362 | #### HINTS 3363 | 3364 | - Replace `pick` with `s` next to the suggested commit 3365 | - It's the `feat: add sample.env` commit 3366 | - You can save and exit by pressing `ctrl+x` then `y` then `enter` 3367 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~2` after it's done resetting 3368 | 3369 | ## 1962. Nano: Add Message + Save and Exit 3370 | 3371 | ### 1962.1 3372 | 3373 | Add a new message at the very top of the file, `feat: add .gitignore and sample.env`. When you are done, save and exit the file. 3374 | 3375 | #### HINTS 3376 | 3377 | - Add the suggested message on it's own line above the other messages 3378 | - You can save and exit by pressing `ctrl+x` then `y` then `enter` 3379 | - The most recent commit message should be `feat: add .gitignore and sample.env` 3380 | - To reset this lesson, make sure nano is closed. Then, hit reset and enter `git rebase --interactive HEAD~2` after it's done resetting. Then, in nano, replace `pick` with `s` next to your `feat: add sample.env` commit, and save and exit 3381 | 3382 | ## 1964. git log -1 3383 | 3384 | ### 1964.1 3385 | 3386 | View only the last commit in your log. 3387 | 3388 | #### HINTS 3389 | 3390 | - Use the `git log` command with the correct argument 3391 | - View the last `x` number of commits with `-x` 3392 | - Use `-1` with the command 3393 | - Type `git log -1` into the terminal and press enter 3394 | 3395 | ## 1970. git checkout main 3396 | 3397 | ### 1970.1 3398 | 3399 | Switch back to `main` so you can add this in. 3400 | 3401 | #### HINTS 3402 | 3403 | - Use the `git checkout` command 3404 | - Here's an example: `git checkout branch_name` 3405 | - Enter `git checkout main` into the terminal and press enter 3406 | 3407 | ## 1980. git merge feat/add-gitignore 3408 | 3409 | ### 1980.1 3410 | 3411 | Merge the branch you just made into here. 3412 | 3413 | #### HINTS 3414 | 3415 | - Use the `git merge` command with the branch name after it 3416 | - Here's an example: `git merge branch_name` 3417 | - Use the `git branch` command if you need to find the branch name 3418 | - It's the `feat/add-gitignore` branch 3419 | - Type `git merge feat/add-gitignore` into the terminal and press enter 3420 | - If you got `fatal: refusing to merge unrelated histories`, you need to switch back to the feature branch, enter `git rebase main` to align the histories, then come back to `main` and try again 3421 | 3422 | ## 1990. git branch -d feat/add-gitignore 3423 | 3424 | ### 1990.1 3425 | 3426 | Delete the feature branch you just merged. 3427 | 3428 | #### HINTS 3429 | 3430 | - Use the `git branch` command with the `-d` flag 3431 | - Here's an example: `git branch -d branch_name` 3432 | - Use just `git branch` if you need to find the branch name 3433 | - The branch name is `feat/add-gitignore` 3434 | - Type `git branch -d feat/add-gitignore` into the terminal and press enter 3435 | 3436 | ## 1995. git log oneline 3437 | 3438 | ### 1995.1 3439 | 3440 | I think it's all finished. View your log with the oneline flag to see your whole history. 3441 | 3442 | #### HINTS 3443 | 3444 | - Use the `git log` command with the correct flag 3445 | - It's the `--oneline` flag 3446 | - Type `git log --oneline` into the terminal and press enter 3447 | 3448 | ## 2000. git log 3449 | 3450 | ### 2000.1 3451 | 3452 | Looks great :smile: View the log one last time, without any flags, to see the details of all the commits. Congratulations, you are finished with your repo for now. 3453 | 3454 | #### HINTS 3455 | 3456 | - Use the `git log` command 3457 | - Don't use any flags with the command 3458 | - Press enter until you have seen the whole log 3459 | -------------------------------------------------------------------------------- /coderoad.yaml: -------------------------------------------------------------------------------- 1 | id: 'freeCodeCamp/learn-git-by-building-an-sql-reference-object:v1.0.0' 2 | version: '2.0.0' 3 | config: 4 | setup: 5 | commands: 6 | - ./.freeCodeCamp/setup.sh 7 | - cd .freeCodeCamp && npm install 8 | testRunner: 9 | command: npm run programmatic-test 10 | args: 11 | tap: --reporter=mocha-tap-reporter 12 | directory: .freeCodeCamp 13 | repo: 14 | uri: https://github.com/freeCodeCamp/learn-git-by-building-an-sql-reference-object 15 | branch: v2.0.0 16 | continue: 17 | commands: 18 | - './.freeCodeCamp/setup.sh' 19 | - './.freeCodeCamp/reset.sh' 20 | reset: 21 | commands: 22 | - './.freeCodeCamp/setup.sh' 23 | - './.freeCodeCamp/reset.sh' 24 | dependencies: 25 | - name: node 26 | version: '>=10' 27 | webhook: 28 | url: 'https://api.freecodecamp.org/coderoad-challenge-completed' 29 | events: 30 | init: false 31 | reset: false 32 | step_complete: false 33 | level_complete: false 34 | tutorial_complete: true 35 | levels: 36 | - id: '10' 37 | steps: 38 | - id: '10.1' 39 | setup: 40 | watchers: 41 | - ../.bash_history 42 | - id: '20' 43 | steps: 44 | - id: '20.1' 45 | setup: 46 | watchers: 47 | - ../.bash_history 48 | - id: '30' 49 | steps: 50 | - id: '30.1' 51 | setup: 52 | watchers: 53 | - ../.bash_history 54 | - id: '40' 55 | steps: 56 | - id: '40.1' 57 | setup: 58 | watchers: 59 | - ../.bash_history 60 | - id: '50' 61 | steps: 62 | - id: '50.1' 63 | setup: 64 | watchers: 65 | - ../.bash_history 66 | - id: '60' 67 | steps: 68 | - id: '60.1' 69 | setup: 70 | watchers: 71 | - ../.bash_history 72 | - id: '70' 73 | steps: 74 | - id: '70.1' 75 | setup: 76 | watchers: 77 | - ../.bash_history 78 | - id: '80' 79 | steps: 80 | - id: '80.1' 81 | setup: 82 | watchers: 83 | - ../.bash_history 84 | - id: '90' 85 | steps: 86 | - id: '90.1' 87 | setup: 88 | watchers: 89 | - ../.bash_history 90 | - id: '100' 91 | steps: 92 | - id: '100.1' 93 | setup: 94 | watchers: 95 | - ./sql_reference/README.md 96 | - id: '110' 97 | steps: 98 | - id: '110.1' 99 | setup: 100 | watchers: 101 | - ../.bash_history 102 | - id: '120' 103 | steps: 104 | - id: '120.1' 105 | setup: 106 | watchers: 107 | - ../.bash_history 108 | - id: '130' 109 | steps: 110 | - id: '130.1' 111 | setup: 112 | watchers: 113 | - ../.bash_history 114 | - id: '140' 115 | steps: 116 | - id: '140.1' 117 | setup: 118 | watchers: 119 | - ../.bash_history 120 | - id: '150' 121 | steps: 122 | - id: '150.1' 123 | setup: 124 | watchers: 125 | - ../.bash_history 126 | - id: '160' 127 | steps: 128 | - id: '160.1' 129 | setup: 130 | watchers: 131 | - ../.bash_history 132 | - id: '170' 133 | steps: 134 | - id: '170.1' 135 | setup: 136 | watchers: 137 | - ../.bash_history 138 | - id: '180' 139 | steps: 140 | - id: '180.1' 141 | setup: 142 | watchers: 143 | - ../.bash_history 144 | - id: '190' 145 | steps: 146 | - id: '190.1' 147 | setup: 148 | watchers: 149 | - ../.bash_history 150 | - id: '200' 151 | steps: 152 | - id: '200.1' 153 | setup: 154 | watchers: 155 | - ../.bash_history 156 | - id: '210' 157 | steps: 158 | - id: '210.1' 159 | setup: 160 | watchers: 161 | - ./sql_reference/sql_reference.json 162 | - id: '220' 163 | steps: 164 | - id: '220.1' 165 | setup: 166 | watchers: 167 | - ../.bash_history 168 | - id: '230' 169 | steps: 170 | - id: '230.1' 171 | setup: 172 | watchers: 173 | - ../.bash_history 174 | - id: '240' 175 | steps: 176 | - id: '240.1' 177 | setup: 178 | watchers: 179 | - ../.bash_history 180 | - id: '250' 181 | steps: 182 | - id: '250.1' 183 | setup: 184 | watchers: 185 | - ../.bash_history 186 | - id: '260' 187 | steps: 188 | - id: '260.1' 189 | setup: 190 | watchers: 191 | - ../.bash_history 192 | - id: '270' 193 | steps: 194 | - id: '270.1' 195 | setup: 196 | watchers: 197 | - ../.bash_history 198 | - id: '280' 199 | steps: 200 | - id: '280.1' 201 | setup: 202 | watchers: 203 | - ./sql_reference/sql_reference.json 204 | - id: '290' 205 | steps: 206 | - id: '290.1' 207 | setup: 208 | watchers: 209 | - ../.bash_history 210 | - id: '300' 211 | steps: 212 | - id: '300.1' 213 | setup: 214 | watchers: 215 | - ../.bash_history 216 | - id: '310' 217 | steps: 218 | - id: '310.1' 219 | setup: 220 | watchers: 221 | - ../.bash_history 222 | - id: '320' 223 | steps: 224 | - id: '320.1' 225 | setup: 226 | watchers: 227 | - ../.bash_history 228 | - id: '330' 229 | steps: 230 | - id: '330.1' 231 | setup: 232 | watchers: 233 | - ../.bash_history 234 | - id: '340' 235 | steps: 236 | - id: '340.1' 237 | setup: 238 | watchers: 239 | - ../.bash_history 240 | - id: '350' 241 | steps: 242 | - id: '350.1' 243 | setup: 244 | watchers: 245 | - ../.bash_history 246 | - id: '360' 247 | steps: 248 | - id: '360.1' 249 | setup: 250 | watchers: 251 | - ../.bash_history 252 | - id: '370' 253 | steps: 254 | - id: '370.1' 255 | setup: 256 | watchers: 257 | - ../.bash_history 258 | - id: '380' 259 | steps: 260 | - id: '380.1' 261 | setup: 262 | watchers: 263 | - ../.bash_history 264 | - id: '390' 265 | steps: 266 | - id: '390.1' 267 | setup: 268 | watchers: 269 | - ./sql_reference/sql_reference.json 270 | - id: '400' 271 | steps: 272 | - id: '400.1' 273 | setup: 274 | watchers: 275 | - ../.bash_history 276 | - id: '405' 277 | steps: 278 | - id: '405.1' 279 | setup: 280 | watchers: 281 | - ../.bash_history 282 | - id: '410' 283 | steps: 284 | - id: '410.1' 285 | setup: 286 | watchers: 287 | - ../.bash_history 288 | - id: '420' 289 | steps: 290 | - id: '420.1' 291 | setup: 292 | watchers: 293 | - ../.bash_history 294 | - id: '430' 295 | steps: 296 | - id: '430.1' 297 | setup: 298 | watchers: 299 | - ../.bash_history 300 | - id: '435' 301 | steps: 302 | - id: '435.1' 303 | setup: 304 | watchers: 305 | - ../.bash_history 306 | - id: '440' 307 | steps: 308 | - id: '440.1' 309 | setup: 310 | watchers: 311 | - ../.bash_history 312 | - id: '450' 313 | steps: 314 | - id: '450.1' 315 | setup: 316 | watchers: 317 | - ../.bash_history 318 | - id: '460' 319 | steps: 320 | - id: '460.1' 321 | setup: 322 | watchers: 323 | - ../.bash_history 324 | - id: '470' 325 | steps: 326 | - id: '470.1' 327 | setup: 328 | watchers: 329 | - ../.bash_history 330 | - id: '480' 331 | steps: 332 | - id: '480.1' 333 | setup: 334 | watchers: 335 | - ../.bash_history 336 | - id: '490' 337 | steps: 338 | - id: '490.1' 339 | setup: 340 | watchers: 341 | - ../.bash_history 342 | - id: '500' 343 | steps: 344 | - id: '500.1' 345 | setup: 346 | watchers: 347 | - ../.bash_history 348 | - id: '510' 349 | steps: 350 | - id: '510.1' 351 | setup: 352 | watchers: 353 | - ../.bash_history 354 | - id: '520' 355 | steps: 356 | - id: '520.1' 357 | setup: 358 | watchers: 359 | - ./sql_reference/sql_reference.json 360 | - id: '530' 361 | steps: 362 | - id: '530.1' 363 | setup: 364 | watchers: 365 | - ../.bash_history 366 | - id: '535' 367 | steps: 368 | - id: '535.1' 369 | setup: 370 | watchers: 371 | - ../.bash_history 372 | - id: '540' 373 | steps: 374 | - id: '540.1' 375 | setup: 376 | watchers: 377 | - ../.bash_history 378 | - id: '550' 379 | steps: 380 | - id: '550.1' 381 | setup: 382 | watchers: 383 | - ../.bash_history 384 | - id: '560' 385 | steps: 386 | - id: '560.1' 387 | setup: 388 | watchers: 389 | - ../.bash_history 390 | - id: '570' 391 | steps: 392 | - id: '570.1' 393 | setup: 394 | watchers: 395 | - ../.bash_history 396 | - id: '580' 397 | steps: 398 | - id: '580.1' 399 | setup: 400 | watchers: 401 | - ../.bash_history 402 | - id: '590' 403 | steps: 404 | - id: '590.1' 405 | setup: 406 | watchers: 407 | - ../.bash_history 408 | - id: '600' 409 | steps: 410 | - id: '600.1' 411 | setup: 412 | watchers: 413 | - ../.bash_history 414 | - id: '610' 415 | steps: 416 | - id: '610.1' 417 | setup: 418 | watchers: 419 | - ./sql_reference/sql_reference.json 420 | - id: '620' 421 | steps: 422 | - id: '620.1' 423 | setup: 424 | watchers: 425 | - ../.bash_history 426 | - id: '630' 427 | steps: 428 | - id: '630.1' 429 | setup: 430 | watchers: 431 | - ../.bash_history 432 | - id: '640' 433 | steps: 434 | - id: '640.1' 435 | setup: 436 | watchers: 437 | - ../.bash_history 438 | - id: '650' 439 | steps: 440 | - id: '650.1' 441 | setup: 442 | watchers: 443 | - ../.bash_history 444 | - id: '670' 445 | steps: 446 | - id: '670.1' 447 | setup: 448 | watchers: 449 | - ../.bash_history 450 | - id: '680' 451 | steps: 452 | - id: '680.1' 453 | setup: 454 | watchers: 455 | - ../.bash_history 456 | - id: '690' 457 | steps: 458 | - id: '690.1' 459 | setup: 460 | watchers: 461 | - ./sql_reference/sql_reference.json 462 | - id: '700' 463 | steps: 464 | - id: '700.1' 465 | setup: 466 | watchers: 467 | - ../.bash_history 468 | - id: '710' 469 | steps: 470 | - id: '710.1' 471 | setup: 472 | watchers: 473 | - ../.bash_history 474 | - id: '720' 475 | steps: 476 | - id: '720.1' 477 | setup: 478 | watchers: 479 | - ../.bash_history 480 | - id: '730' 481 | steps: 482 | - id: '730.1' 483 | setup: 484 | watchers: 485 | - ../.bash_history 486 | - id: '740' 487 | steps: 488 | - id: '740.1' 489 | setup: 490 | watchers: 491 | - ../.bash_history 492 | - id: '750' 493 | steps: 494 | - id: '750.1' 495 | setup: 496 | watchers: 497 | - ../.bash_history 498 | - id: '755' 499 | steps: 500 | - id: '755.1' 501 | setup: 502 | watchers: 503 | - ../.bash_history 504 | - id: '760' 505 | steps: 506 | - id: '760.1' 507 | setup: 508 | watchers: 509 | - ../.bash_history 510 | - id: '770' 511 | steps: 512 | - id: '770.1' 513 | setup: 514 | watchers: 515 | - ../.bash_history 516 | - id: '780' 517 | steps: 518 | - id: '780.1' 519 | setup: 520 | watchers: 521 | - ../.bash_history 522 | - id: '790' 523 | steps: 524 | - id: '790.1' 525 | setup: 526 | watchers: 527 | - ../.bash_history 528 | - id: '800' 529 | steps: 530 | - id: '800.1' 531 | setup: 532 | watchers: 533 | - ./sql_reference/sql_reference.json 534 | - id: '810' 535 | steps: 536 | - id: '810.1' 537 | setup: 538 | watchers: 539 | - ../.bash_history 540 | - id: '820' 541 | steps: 542 | - id: '820.1' 543 | setup: 544 | watchers: 545 | - ../.bash_history 546 | - id: '830' 547 | steps: 548 | - id: '830.1' 549 | setup: 550 | watchers: 551 | - ../.bash_history 552 | - id: '840' 553 | steps: 554 | - id: '840.1' 555 | setup: 556 | watchers: 557 | - ../.bash_history 558 | - id: '850' 559 | steps: 560 | - id: '850.1' 561 | setup: 562 | watchers: 563 | - ../.bash_history 564 | - id: '860' 565 | steps: 566 | - id: '860.1' 567 | setup: 568 | watchers: 569 | - ./sql_reference/sql_reference.json 570 | - id: '870' 571 | steps: 572 | - id: '870.1' 573 | setup: 574 | watchers: 575 | - ../.bash_history 576 | - id: '880' 577 | steps: 578 | - id: '880.1' 579 | setup: 580 | watchers: 581 | - ../.bash_history 582 | - id: '890' 583 | steps: 584 | - id: '890.1' 585 | setup: 586 | watchers: 587 | - ../.bash_history 588 | - id: '900' 589 | steps: 590 | - id: '900.1' 591 | setup: 592 | watchers: 593 | - ../.bash_history 594 | - id: '910' 595 | steps: 596 | - id: '910.1' 597 | setup: 598 | watchers: 599 | - ../.bash_history 600 | - id: '930' 601 | steps: 602 | - id: '930.1' 603 | setup: 604 | watchers: 605 | - ../.bash_history 606 | - id: '940' 607 | steps: 608 | - id: '940.1' 609 | setup: 610 | watchers: 611 | - ../.bash_history 612 | - id: '950' 613 | steps: 614 | - id: '950.1' 615 | setup: 616 | watchers: 617 | - ./sql_reference/sql_reference.json 618 | - id: '953' 619 | steps: 620 | - id: '953.1' 621 | setup: 622 | watchers: 623 | - ../.bash_history 624 | - id: '956' 625 | steps: 626 | - id: '956.1' 627 | setup: 628 | watchers: 629 | - ../.bash_history 630 | - id: '958' 631 | steps: 632 | - id: '958.1' 633 | setup: 634 | watchers: 635 | - ../.bash_history 636 | - id: '960' 637 | steps: 638 | - id: '960.1' 639 | setup: 640 | watchers: 641 | - ../.bash_history 642 | - id: '970' 643 | steps: 644 | - id: '970.1' 645 | setup: 646 | watchers: 647 | - ../.bash_history 648 | - id: '980' 649 | steps: 650 | - id: '980.1' 651 | setup: 652 | watchers: 653 | - ./sql_reference/sql_reference.json 654 | - id: '990' 655 | steps: 656 | - id: '990.1' 657 | setup: 658 | watchers: 659 | - ../.bash_history 660 | - id: '1000' 661 | steps: 662 | - id: '1000.1' 663 | setup: 664 | watchers: 665 | - ../.bash_history 666 | - id: '1010' 667 | steps: 668 | - id: '1010.1' 669 | setup: 670 | watchers: 671 | - ../.bash_history 672 | - id: '1015' 673 | steps: 674 | - id: '1015.1' 675 | setup: 676 | watchers: 677 | - ./sql_reference/sql_reference.json 678 | - id: '1017' 679 | steps: 680 | - id: '1017.1' 681 | setup: 682 | watchers: 683 | - ../.bash_history 684 | - id: '1020' 685 | steps: 686 | - id: '1020.1' 687 | setup: 688 | watchers: 689 | - ../.bash_history 690 | - id: '1025' 691 | steps: 692 | - id: '1025.1' 693 | setup: 694 | watchers: 695 | - ../.bash_history 696 | - id: '1030' 697 | steps: 698 | - id: '1030.1' 699 | setup: 700 | watchers: 701 | - ../.bash_history 702 | - id: '1040' 703 | steps: 704 | - id: '1040.1' 705 | setup: 706 | watchers: 707 | - ../.bash_history 708 | - id: '1050' 709 | steps: 710 | - id: '1050.1' 711 | setup: 712 | watchers: 713 | - ../.bash_history 714 | - id: '1055' 715 | steps: 716 | - id: '1055.1' 717 | setup: 718 | watchers: 719 | - ../.bash_history 720 | - id: '1070' 721 | steps: 722 | - id: '1070.1' 723 | setup: 724 | watchers: 725 | - ../.bash_history 726 | - id: '1073' 727 | steps: 728 | - id: '1073.1' 729 | setup: 730 | watchers: 731 | - ../.bash_history 732 | - id: '1076' 733 | steps: 734 | - id: '1076.1' 735 | setup: 736 | watchers: 737 | - ../.bash_history 738 | - id: '1080' 739 | steps: 740 | - id: '1080.1' 741 | setup: 742 | watchers: 743 | - ../.bash_history 744 | - id: '1090' 745 | steps: 746 | - id: '1090.1' 747 | setup: 748 | watchers: 749 | - ../.bash_history 750 | - id: '1100' 751 | steps: 752 | - id: '1100.1' 753 | setup: 754 | watchers: 755 | - ../.bash_history 756 | - id: '1110' 757 | steps: 758 | - id: '1110.1' 759 | setup: 760 | watchers: 761 | - ../.bash_history 762 | - id: '1113' 763 | steps: 764 | - id: '1113.1' 765 | setup: 766 | watchers: 767 | - ../.bash_history 768 | - id: '1116' 769 | steps: 770 | - id: '1116.1' 771 | setup: 772 | watchers: 773 | - ../.bash_history 774 | - id: '1120' 775 | steps: 776 | - id: '1120.1' 777 | setup: 778 | watchers: 779 | - ../.bash_history 780 | - id: '1130' 781 | steps: 782 | - id: '1130.1' 783 | setup: 784 | watchers: 785 | - ../.bash_history 786 | - id: '1140' 787 | steps: 788 | - id: '1140.1' 789 | setup: 790 | watchers: 791 | - ../.bash_history 792 | - id: '1150' 793 | steps: 794 | - id: '1150.1' 795 | setup: 796 | watchers: 797 | - ../.bash_history 798 | - id: '1160' 799 | steps: 800 | - id: '1160.1' 801 | setup: 802 | watchers: 803 | - ../.bash_history 804 | - id: '1170' 805 | steps: 806 | - id: '1170.1' 807 | setup: 808 | watchers: 809 | - ../.bash_history 810 | - id: '1180' 811 | steps: 812 | - id: '1180.1' 813 | setup: 814 | watchers: 815 | - ../.bash_history 816 | - id: '1190' 817 | steps: 818 | - id: '1190.1' 819 | setup: 820 | watchers: 821 | - ../.bash_history 822 | - id: '1210' 823 | steps: 824 | - id: '1210.1' 825 | setup: 826 | watchers: 827 | - ../.bash_history 828 | - id: '1220' 829 | steps: 830 | - id: '1220.1' 831 | setup: 832 | watchers: 833 | - ../.bash_history 834 | - id: '1230' 835 | steps: 836 | - id: '1230.1' 837 | setup: 838 | watchers: 839 | - ../.bash_history 840 | - id: '1240' 841 | steps: 842 | - id: '1240.1' 843 | setup: 844 | watchers: 845 | - ../.bash_history 846 | - id: '1250' 847 | steps: 848 | - id: '1250.1' 849 | setup: 850 | watchers: 851 | - ../.bash_history 852 | - id: '1260' 853 | steps: 854 | - id: '1260.1' 855 | setup: 856 | watchers: 857 | - ../.bash_history 858 | - id: '1270' 859 | steps: 860 | - id: '1270.1' 861 | setup: 862 | watchers: 863 | - ../.bash_history 864 | - id: '1280' 865 | steps: 866 | - id: '1280.1' 867 | setup: 868 | watchers: 869 | - ../.bash_history 870 | - id: '1290' 871 | steps: 872 | - id: '1290.1' 873 | setup: 874 | watchers: 875 | - ../.bash_history 876 | - id: '1300' 877 | steps: 878 | - id: '1300.1' 879 | setup: 880 | watchers: 881 | - ../.bash_history 882 | - id: '1305' 883 | steps: 884 | - id: '1305.1' 885 | setup: 886 | watchers: 887 | - ../.bash_history 888 | - id: '1310' 889 | steps: 890 | - id: '1310.1' 891 | setup: 892 | watchers: 893 | - ../.bash_history 894 | - id: '1320' 895 | steps: 896 | - id: '1320.1' 897 | setup: 898 | watchers: 899 | - ../.bash_history 900 | - id: '1330' 901 | steps: 902 | - id: '1330.1' 903 | setup: 904 | watchers: 905 | - ./sql_reference/sql_reference.json 906 | - id: '1340' 907 | steps: 908 | - id: '1340.1' 909 | setup: 910 | watchers: 911 | - ../.bash_history 912 | - id: '1350' 913 | steps: 914 | - id: '1350.1' 915 | setup: 916 | watchers: 917 | - ../.bash_history 918 | - id: '1352' 919 | steps: 920 | - id: '1352.1' 921 | setup: 922 | watchers: 923 | - ./sql_reference/sql_reference.json 924 | - id: '1354' 925 | steps: 926 | - id: '1354.1' 927 | setup: 928 | watchers: 929 | - ../.bash_history 930 | - id: '1356' 931 | steps: 932 | - id: '1356.1' 933 | setup: 934 | watchers: 935 | - ../.bash_history 936 | - id: '1360' 937 | steps: 938 | - id: '1360.1' 939 | setup: 940 | watchers: 941 | - ../.bash_history 942 | - id: '1370' 943 | steps: 944 | - id: '1370.1' 945 | setup: 946 | watchers: 947 | - ./sql_reference/sql_reference.json 948 | - id: '1380' 949 | steps: 950 | - id: '1380.1' 951 | setup: 952 | watchers: 953 | - ../.bash_history 954 | - id: '1390' 955 | steps: 956 | - id: '1390.1' 957 | setup: 958 | watchers: 959 | - ../.bash_history 960 | - id: '1400' 961 | steps: 962 | - id: '1400.1' 963 | setup: 964 | watchers: 965 | - ../.bash_history 966 | - id: '1410' 967 | steps: 968 | - id: '1410.1' 969 | setup: 970 | watchers: 971 | - ../.bash_history 972 | - id: '1416' 973 | steps: 974 | - id: '1416.1' 975 | setup: 976 | watchers: 977 | - ../.bash_history 978 | - id: '1420' 979 | steps: 980 | - id: '1420.1' 981 | setup: 982 | watchers: 983 | - ../.bash_history 984 | - id: '1430' 985 | steps: 986 | - id: '1430.1' 987 | setup: 988 | watchers: 989 | - ./sql_reference/sql_reference.json 990 | - id: '1440' 991 | steps: 992 | - id: '1440.1' 993 | setup: 994 | watchers: 995 | - ../.bash_history 996 | - id: '1450' 997 | steps: 998 | - id: '1450.1' 999 | setup: 1000 | watchers: 1001 | - ../.bash_history 1002 | - id: '1460' 1003 | steps: 1004 | - id: '1460.1' 1005 | setup: 1006 | watchers: 1007 | - ../.bash_history 1008 | - id: '1470' 1009 | steps: 1010 | - id: '1470.1' 1011 | setup: 1012 | watchers: 1013 | - ../.bash_history 1014 | - id: '1480' 1015 | steps: 1016 | - id: '1480.1' 1017 | setup: 1018 | watchers: 1019 | - ./sql_reference/sql_reference.json 1020 | - id: '1490' 1021 | steps: 1022 | - id: '1490.1' 1023 | setup: 1024 | watchers: 1025 | - ../.bash_history 1026 | - id: '1495' 1027 | steps: 1028 | - id: '1495.1' 1029 | setup: 1030 | watchers: 1031 | - ../.bash_history 1032 | - id: '1500' 1033 | steps: 1034 | - id: '1500.1' 1035 | setup: 1036 | watchers: 1037 | - ../.bash_history 1038 | - id: '1510' 1039 | steps: 1040 | - id: '1510.1' 1041 | setup: 1042 | watchers: 1043 | - ./sql_reference/sql_reference.json 1044 | - id: '1520' 1045 | steps: 1046 | - id: '1520.1' 1047 | setup: 1048 | watchers: 1049 | - ../.bash_history 1050 | - id: '1530' 1051 | steps: 1052 | - id: '1530.1' 1053 | setup: 1054 | watchers: 1055 | - ../.bash_history 1056 | - id: '1533' 1057 | steps: 1058 | - id: '1533.1' 1059 | setup: 1060 | watchers: 1061 | - ../.bash_history 1062 | - id: '1536' 1063 | steps: 1064 | - id: '1536.1' 1065 | setup: 1066 | watchers: 1067 | - ../.bash_history 1068 | - id: '1539' 1069 | steps: 1070 | - id: '1539.1' 1071 | setup: 1072 | watchers: 1073 | - ../.bash_history 1074 | - id: '1540' 1075 | steps: 1076 | - id: '1540.1' 1077 | setup: 1078 | watchers: 1079 | - ../.bash_history 1080 | - id: '1542' 1081 | steps: 1082 | - id: '1542.1' 1083 | setup: 1084 | watchers: 1085 | - ../.bash_history 1086 | - id: '1545' 1087 | steps: 1088 | - id: '1545.1' 1089 | setup: 1090 | watchers: 1091 | - ../.bash_history 1092 | - id: '1548' 1093 | steps: 1094 | - id: '1548.1' 1095 | setup: 1096 | watchers: 1097 | - ./.freeCodeCamp/test/.next_command 1098 | - id: '1549' 1099 | steps: 1100 | - id: '1549.1' 1101 | setup: 1102 | watchers: 1103 | - ./.freeCodeCamp/test/.next_command 1104 | - id: '1551' 1105 | steps: 1106 | - id: '1551.1' 1107 | setup: 1108 | watchers: 1109 | - ../.bash_history 1110 | - id: '1554' 1111 | steps: 1112 | - id: '1554.1' 1113 | setup: 1114 | watchers: 1115 | - ../.bash_history 1116 | - id: '1557' 1117 | steps: 1118 | - id: '1557.1' 1119 | setup: 1120 | watchers: 1121 | - ../.bash_history 1122 | - id: '1560' 1123 | steps: 1124 | - id: '1560.1' 1125 | setup: 1126 | watchers: 1127 | - ./.freeCodeCamp/test/.next_command 1128 | - id: '1563' 1129 | steps: 1130 | - id: '1563.1' 1131 | setup: 1132 | watchers: 1133 | - ../.bash_history 1134 | - id: '1564' 1135 | steps: 1136 | - id: '1564.1' 1137 | setup: 1138 | watchers: 1139 | - ../.bash_history 1140 | - id: '1567' 1141 | steps: 1142 | - id: '1567.1' 1143 | setup: 1144 | watchers: 1145 | - ./.freeCodeCamp/test/.next_command 1146 | - id: '1570' 1147 | steps: 1148 | - id: '1570.1' 1149 | setup: 1150 | watchers: 1151 | - ./sql_reference/.git/rebase-merge/done 1152 | - id: '1572' 1153 | steps: 1154 | - id: '1572.1' 1155 | setup: 1156 | watchers: 1157 | - ../.bash_history 1158 | - id: '1575' 1159 | steps: 1160 | - id: '1575.1' 1161 | setup: 1162 | watchers: 1163 | - ../.bash_history 1164 | - id: '1576' 1165 | steps: 1166 | - id: '1576.1' 1167 | setup: 1168 | watchers: 1169 | - ../.bash_history 1170 | - id: '1578' 1171 | steps: 1172 | - id: '1578.1' 1173 | setup: 1174 | watchers: 1175 | - ../.bash_history 1176 | - id: '1580' 1177 | steps: 1178 | - id: '1580.1' 1179 | setup: 1180 | watchers: 1181 | - ./.freeCodeCamp/test/.next_command 1182 | - id: '1590' 1183 | steps: 1184 | - id: '1590.1' 1185 | setup: 1186 | watchers: 1187 | - ./sql_reference/.git/rebase-merge/done 1188 | - id: '1595' 1189 | steps: 1190 | - id: '1595.1' 1191 | setup: 1192 | watchers: 1193 | - ../.bash_history 1194 | - id: '1600' 1195 | steps: 1196 | - id: '1600.1' 1197 | setup: 1198 | watchers: 1199 | - ../.bash_history 1200 | - id: '1610' 1201 | steps: 1202 | - id: '1610.1' 1203 | setup: 1204 | watchers: 1205 | - ../.bash_history 1206 | - id: '1620' 1207 | steps: 1208 | - id: '1620.1' 1209 | setup: 1210 | watchers: 1211 | - ../.bash_history 1212 | - id: '1630' 1213 | steps: 1214 | - id: '1630.1' 1215 | setup: 1216 | watchers: 1217 | - ../.bash_history 1218 | - id: '1635' 1219 | steps: 1220 | - id: '1635.1' 1221 | setup: 1222 | watchers: 1223 | - ../.bash_history 1224 | - id: '1640' 1225 | steps: 1226 | - id: '1640.1' 1227 | setup: 1228 | watchers: 1229 | - ../.bash_history 1230 | - id: '1650' 1231 | steps: 1232 | - id: '1650.1' 1233 | setup: 1234 | watchers: 1235 | - ../.bash_history 1236 | - id: '1680' 1237 | steps: 1238 | - id: '1680.1' 1239 | setup: 1240 | watchers: 1241 | - ../.bash_history 1242 | - id: '1690' 1243 | steps: 1244 | - id: '1690.1' 1245 | setup: 1246 | watchers: 1247 | - ./sql_reference/sql_reference.json 1248 | - id: '1700' 1249 | steps: 1250 | - id: '1700.1' 1251 | setup: 1252 | watchers: 1253 | - ../.bash_history 1254 | - id: '1710' 1255 | steps: 1256 | - id: '1710.1' 1257 | setup: 1258 | watchers: 1259 | - ../.bash_history 1260 | - id: '1715' 1261 | steps: 1262 | - id: '1715.1' 1263 | setup: 1264 | watchers: 1265 | - ../.bash_history 1266 | - id: '1720' 1267 | steps: 1268 | - id: '1720.1' 1269 | setup: 1270 | watchers: 1271 | - ./.freeCodeCamp/test/.next_command 1272 | - id: '1730' 1273 | steps: 1274 | - id: '1730.1' 1275 | setup: 1276 | watchers: 1277 | - ./sql_reference/.git/rebase-merge/done 1278 | - id: '1735' 1279 | steps: 1280 | - id: '1735.1' 1281 | setup: 1282 | watchers: 1283 | - ../.bash_history 1284 | - id: '1737' 1285 | steps: 1286 | - id: '1737.1' 1287 | setup: 1288 | watchers: 1289 | - ../.bash_history 1290 | - id: '1740' 1291 | steps: 1292 | - id: '1740.1' 1293 | setup: 1294 | watchers: 1295 | - ../.bash_history 1296 | - id: '1750' 1297 | steps: 1298 | - id: '1750.1' 1299 | setup: 1300 | watchers: 1301 | - ../.bash_history 1302 | - id: '1760' 1303 | steps: 1304 | - id: '1760.1' 1305 | setup: 1306 | watchers: 1307 | - ../.bash_history 1308 | - id: '1770' 1309 | steps: 1310 | - id: '1770.1' 1311 | setup: 1312 | watchers: 1313 | - ../.bash_history 1314 | - id: '1780' 1315 | steps: 1316 | - id: '1780.1' 1317 | setup: 1318 | watchers: 1319 | - ../.bash_history 1320 | - id: '1790' 1321 | steps: 1322 | - id: '1790.1' 1323 | setup: 1324 | watchers: 1325 | - ../.bash_history 1326 | - id: '1800' 1327 | steps: 1328 | - id: '1800.1' 1329 | setup: 1330 | watchers: 1331 | - ../.bash_history 1332 | - id: '1810' 1333 | steps: 1334 | - id: '1810.1' 1335 | setup: 1336 | watchers: 1337 | - ./sql_reference/.env 1338 | - id: '1820' 1339 | steps: 1340 | - id: '1820.1' 1341 | setup: 1342 | watchers: 1343 | - ../.bash_history 1344 | - id: '1830' 1345 | steps: 1346 | - id: '1830.1' 1347 | setup: 1348 | watchers: 1349 | - ../.bash_history 1350 | - id: '1835' 1351 | steps: 1352 | - id: '1835.1' 1353 | setup: 1354 | watchers: 1355 | - ../.bash_history 1356 | - id: '1840' 1357 | steps: 1358 | - id: '1840.1' 1359 | setup: 1360 | watchers: 1361 | - ./sql_reference/.gitignore 1362 | - id: '1850' 1363 | steps: 1364 | - id: '1850.1' 1365 | setup: 1366 | watchers: 1367 | - ../.bash_history 1368 | - id: '1860' 1369 | steps: 1370 | - id: '1860.1' 1371 | setup: 1372 | watchers: 1373 | - ../.bash_history 1374 | - id: '1870' 1375 | steps: 1376 | - id: '1870.1' 1377 | setup: 1378 | watchers: 1379 | - ../.bash_history 1380 | - id: '1880' 1381 | steps: 1382 | - id: '1880.1' 1383 | setup: 1384 | watchers: 1385 | - ../.bash_history 1386 | - id: '1890' 1387 | steps: 1388 | - id: '1890.1' 1389 | setup: 1390 | watchers: 1391 | - ../.bash_history 1392 | - id: '1900' 1393 | steps: 1394 | - id: '1900.1' 1395 | setup: 1396 | watchers: 1397 | - ./sql_reference/sample.env 1398 | - id: '1930' 1399 | steps: 1400 | - id: '1930.1' 1401 | setup: 1402 | watchers: 1403 | - ../.bash_history 1404 | - id: '1940' 1405 | steps: 1406 | - id: '1940.1' 1407 | setup: 1408 | watchers: 1409 | - ../.bash_history 1410 | - id: '1945' 1411 | steps: 1412 | - id: '1945.1' 1413 | setup: 1414 | watchers: 1415 | - ../.bash_history 1416 | - id: '1950' 1417 | steps: 1418 | - id: '1950.1' 1419 | setup: 1420 | watchers: 1421 | - ./.freeCodeCamp/test/.next_command 1422 | - id: '1960' 1423 | steps: 1424 | - id: '1960.1' 1425 | setup: 1426 | watchers: 1427 | - ./sql_reference/.git/rebase-merge/done 1428 | - id: '1962' 1429 | steps: 1430 | - id: '1962.1' 1431 | setup: 1432 | watchers: 1433 | - ../.bash_history 1434 | - id: '1964' 1435 | steps: 1436 | - id: '1964.1' 1437 | setup: 1438 | watchers: 1439 | - ../.bash_history 1440 | - id: '1970' 1441 | steps: 1442 | - id: '1970.1' 1443 | setup: 1444 | watchers: 1445 | - ../.bash_history 1446 | - id: '1980' 1447 | steps: 1448 | - id: '1980.1' 1449 | setup: 1450 | watchers: 1451 | - ../.bash_history 1452 | - id: '1990' 1453 | steps: 1454 | - id: '1990.1' 1455 | setup: 1456 | watchers: 1457 | - ../.bash_history 1458 | - id: '1995' 1459 | steps: 1460 | - id: '1995.1' 1461 | setup: 1462 | watchers: 1463 | - ../.bash_history 1464 | - id: '2000' 1465 | steps: 1466 | - id: '2000.1' 1467 | setup: 1468 | watchers: 1469 | - ../.bash_history 1470 | --------------------------------------------------------------------------------