{"id":621,"date":"2021-07-23T12:34:11","date_gmt":"2021-07-23T12:34:11","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/guide-to-git-common-git-commands\/"},"modified":"2021-07-23T12:34:11","modified_gmt":"2021-07-23T12:34:11","slug":"guide-to-git-common-git-commands","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/guide-to-git-common-git-commands\/","title":{"rendered":"Guide to Git\u2122 – Common Git Commands"},"content":{"rendered":"<\/p>\n
\n
<\/div>\n
\n

Overview<\/h2>\n

You can access all of Git\u2122\u2019s functionality via the command line. This document lists common commands and options that may assist you when you learn Git.<\/p>\n

\n
Important:<\/div>\n
\n
    \n
  • \n

    This document is not<\/strong> comprehensive. It intentionally omits information about intermediate and advanced Git functionality. For more information about additional commands and options, read Git\u2019s documentation.<\/p>\n<\/li>\n

  • \n

    The terminology in this document assumes basic familiarity with the command line.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

    Common Git commands<\/h2>\n
    \n
    Note:<\/div>\n
    \n
      \n
    • \n

      To resolve Git errors, read our Guide to Git – For System Administrators documentation.<\/p>\n<\/li>\n

    • \n

      For general Linux commands, read our Getting Started with Linux Commands documentation.<\/p>\n<\/li>\n

    • \n

      For help to access the command line in order to run these commands, read our How to Access the Command Line documentation.<\/p>\n<\/li>\n

    • \n

      You can add the --help<\/code> option to any Git command in order to view the manual page for that command.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n

      git clone<\/h3>\n

      This command clones a repository into a new directory, creates remote-tracking branches, and forks a new working branch from the cloned repository\u2019s active branch.<\/p>\n

      \n
      git clone repositoryurl<\/code><\/pre>\n<\/div>\n
      In the example above, repositoryurl<\/code> represents the URL of the repository that you wish to clone.<\/p>\n
      \n
      Note:<\/div>\n
      \n
        \n
      • Use the git fetch<\/code> command to update the new repository\u2019s remote-tracking branches.<\/li>\n
      • Use the git pull<\/code> command to merge the remote master branch into the current master branch.<\/li>\n
      • cPanel\u2019s Git\u2122 Version Control<\/em> interface (cPanel >> Home >> Files >> Git\u2122 Version Control<\/em>) provides the URL to use to clone each of your account\u2019s repositories.<\/li>\n
      • To clone private repositories, you must perform additional steps. For more information, read our Guide to Git – Set Up Access to Private Repositories documentation.<\/li>\n<\/ul><\/div>\n<\/div>\n
        git add<\/h3>\n
        This command adds the current version of a file to the index of staged content for the next commit.<\/p>\n
        \n
        git add [options] filepath<\/code><\/pre>\n<\/div>\n
        In the example above, filepath<\/code> represents the file\u2019s absolute path or<\/strong> its path relative to the current working directory.<\/p>\n
          \n
        • \n
          To stage uncommitted changes for all<\/strong> tracked files, run this command with either of the -a<\/code> or -u<\/code> options (and without a specified file path).<\/p>\n<\/li>\n
        • \n
          This command only<\/strong> stages the current changes for the current commit. The next time that you create a commit, you must<\/strong> run the command for the file again in order to stage any new changes.<\/p>\n<\/li>\n<\/ul>\n
          git commit<\/h3>\n
          This command creates a new commit for the currently-staged changes.<\/p>\n
          \n
          git commit [options]<\/code><\/pre>\n<\/div>\n
          When you run this command (without the -m<\/code> option), Git immediately displays a text file, in which you can enter and save your commit message.<\/p>\n
            \n
          • \n
            To automatically stage modified and deleted files before Git creates the commit, run this command with the -a<\/code> option.<\/p>\n<\/li>\n
          • \n
            To specify a short commit message directly from the command line, run this command with the -m<\/code> option. For example:<\/p>\n<\/li>\n<\/ul>\n
            \n
            git commit -<\/span>m \"Commit message here.\"<\/span><\/code><\/pre>\n<\/div>\n
            \n
            Note:<\/div>\n
            \n
            To stage changes for inclusion in a commit, use the git add<\/code> or git rm<\/code> commands or provide individual filepaths as arguments to this command.<\/p>\n<\/p><\/div>\n<\/div>\n
            git checkout<\/h3>\n
            This command sets the specified branch as the current working branch.<\/p>\n
            \n
            git checkout [options] branchname<\/code><\/pre>\n<\/div>\n
            In the example above, branchname<\/code> represents the branch to check out.<\/p>\n
              \n
            • \n
              To check out only a specified file, run this command with a file path instead of a branch name.\n<\/p>\n
              \n
              git checkout mybranch files\/templates\/<\/span>2<\/span>.<\/span>html<\/code><\/pre>\n<\/div>\n
              In this example, mybranch<\/code> represents the branch that contains the version of the file that you wish to check out and files\/templates\/2.html<\/code> represents the file to check out. If you run this command, the system will replace the files\/templates\/2.html<\/code> file\u2019s contents in the current local working branch with the file\u2019s contents from the mybranch<\/code> branch.<\/p>\n
              \n
              Note:<\/div>\n
              \n
              If you omit the branch name, Git will check out that file from the HEAD of the current branch.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
            • \n
              To create a new branch with the specified branch name and then check it out, run this command with the -b<\/code> option.<\/p>\n<\/li>\n
            • \n
              To forcibly change branches, run the command with the -f<\/code> option. This option causes Git to overwrite local changes in order to match the working tree to the branch\u2019s HEAD commit.<\/p>\n<\/li>\n<\/ul>\n
              git rm<\/h3>\n
              This command removes files or directories from Git\u2019s index and working tree.<\/p>\n
              \n
              git rm [options] files_or_dirs<\/code><\/pre>\n<\/div>\n
              In the example above, files_or_dirs<\/code> represents the paths to the files or directories to remove, relative to the repository\u2019s main directory.<\/p>\n
              \n
              Important:<\/div>\n
              \n
                \n
              • \n
                To run this command, the specified file cannot<\/strong> contain uncommitted changes.<\/p>\n<\/li>\n
              • \n
                This command cannot<\/strong> retain the file in the index and<\/strong> remove the file from the working tree. To do this, use BASH\u2019s rm<\/code> command.<\/p>\n<\/li>\n
              • \n
                If you specify a directory name, you must<\/strong> also use the -r<\/code> option. This option allows the command to recursively remove the files in that directory.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n
                git fetch<\/h3>\n
                This command downloads branches, tags, and their histories from one or more other repositories.<\/p>\n
                \n
                git fetch [options] remotename<\/code><\/pre>\n<\/div>\n
                In the example above, remotename<\/code> represents the name of the remote repository.<\/p>\n
                git pull<\/h3>\n
                This command fetches and merges changes from a local branch or a remote or local repository. With most options, this command combines the git fetch<\/code> and git merge<\/code> commands.<\/p>\n
                \n
                git pull [options] repo-<\/span>or<\/span>-<\/span>branch<\/code><\/pre>\n<\/div>\n
                In the example above, repo-or-branch<\/code> represents the branch name or the repository name or URL.<\/p>\n
                git push<\/h3>\n
                This command adds your committed changes to the specified repository and branch.<\/p>\n
                \n
                git push [options] repository branch<\/code><\/pre>\n<\/div>\n
                In the example above, repository<\/code> represents the repository name or URL and branch<\/code> represents the remote branch on that repository.<\/p>\n
                  \n
                • \n
                  If you do not<\/strong> specify a repository, the command performs one of the following actions:<\/p>\n
                    \n
                  • If your current branch\u2019s configuration includes a remote repository, the command adds your changes to that repository.<\/li>\n
                  • If your current branch\u2019s configuration does not<\/strong> include a remote repository, the command adds your changes to the origin<\/code> repository.\n
                    \n
                    Important:<\/div>\n
                    \n
                    You must<\/strong> explicitly specify a repository in order to specify a branch. If you do not<\/strong> specify a branch, the command adds your changes to the remote repository\u2019s current branch.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
                  • \n
                    To push all<\/strong> commits from all<\/strong> local branches to their upstream repositories, run this command with the --all<\/code> option.<\/p>\n<\/li>\n
                  • \n
                    To add the specified repository to the branch as its upstream repository, run this command with the --set-upstream<\/code> option.<\/p>\n
                      \n
                    • This allows you to omit the repository on subsequent pushes to upstream.<\/li>\n
                    • You must specify a remote repository when you use this option.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n
                      \n
                      Note:<\/div>\n
                      \n
                      cPanel\u2019s cPanel\u2019s Git\u2122 Version Control<\/em> interface (cPanel >> Home >> Files >> Git\u2122 Version Control<\/em>) automatically adds a post-receive<\/code> hook that each push to cPanel-managed repositories triggers. For more information, read our Guide to Git – Deployment documentation or Git\u2019s githooks documentation.<\/p>\n<\/p><\/div>\n<\/div>\n
                      git branch<\/h3>\n
                      This command creates, lists, or deletes branches.<\/p>\n
                      \n
                      git branch [options] branchname<\/code><\/pre>\n<\/div>\n
                      In the example above, branchname<\/code> represents the branch name.<\/p>\n
                        \n
                      • \n
                        To create a new branch, run this command with the desired branch name.<\/p>\n
                        \n
                        Important:<\/div>\n
                        \n
                        Git does not<\/strong> automatically check out new branches when you create them. You must<\/strong> also run the git checkout<\/code> command in order to check out your new branch.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                      • \n
                        To retrieve a list of existing local branches, run this command without a branch name. Use the -a<\/code> option to retrieve a list of both local and remote branches.<\/p>\n<\/li>\n
                      • \n
                        To set the upstream branch for a specified branch, run this command with the -u<\/code> option.<\/p>\n<\/li>\n
                      • \n
                        To rename a specified branch, run this command with the -m<\/code> option and the current and new branch names. For example:\n<\/p>\n
                        \n
                        git branch -<\/span>m oldbranch newbranch<\/code><\/pre>\n<\/div>\n
                        In this example, oldbranch<\/code> represents the current branch name and newbranch<\/code> represents the new branch name.<\/li>\n
                      • \n
                        To delete a specified branch, run this command with the -d<\/code> option.<\/p>\n<\/li>\n<\/ul>\n
                        git merge<\/h3>\n
                        This command combines the history of one or more commits into the history of the current branch.<\/p>\n<\/p>\n
                        \n
                        git merge [options]<\/code><\/pre>\n<\/div>\n
                        \n
                        Note:<\/div>\n
                        \n
                        The git pull<\/code> command automatically performs this action.<\/p>\n<\/p><\/div>\n<\/div>\n
                        git blame<\/h3>\n
                        This command displays the specified file with the author, most-recent change date, and commit SHA-1 for each line of the file.<\/p>\n
                        \n
                        git blame [options] filepath<\/code><\/pre>\n<\/div>\n
                        In the example above, filepath<\/code> represents the file\u2019s absolute path or its path relative to the current working directory.<\/p>\n
                        When you run this command without additional options, the output will resemble the following example:<\/p>\n
                        \n
                        \n\n\n
                        \n
                        1\n<\/span>2\n<\/span>3\n<\/span>4\n<\/span>5\n<\/span>6\n<\/span>7\n<\/span><\/code><\/pre>\n<\/td>\n
                        		\n
                        5<\/span>f033c48d84a<\/span> (Jane<\/span> E<\/span>. Coder<\/span>        2017<\/span>-<\/span>05<\/span>-<\/span>24<\/span> 18<\/span>:25<\/span>:53<\/span> -<\/span>0600<\/span>  1<\/span>) <!DOCTYPE<\/span> HTML<\/span>>\n5<\/span>f033c48d84a<\/span> (Jane<\/span> E<\/span>. Coder<\/span>        2017<\/span>-<\/span>05<\/span>-<\/span>24<\/span> 18<\/span>:25<\/span>:53<\/span> -<\/span>0600<\/span>  2<\/span>) <html<\/span>>\n5<\/span>f033c48d84a<\/span> (Jane<\/span> E<\/span>. Coder<\/span>        2017<\/span>-<\/span>05<\/span>-<\/span>24<\/span> 18<\/span>:25<\/span>:53<\/span> -<\/span>0600<\/span>  3<\/span>)\n5<\/span>f033c48d84a<\/span> (Jane<\/span> E<\/span>. Coder<\/span>        2017<\/span>-<\/span>05<\/span>-<\/span>24<\/span> 18<\/span>:25<\/span>:53<\/span> -<\/span>0600<\/span>  4<\/span>) <body<\/span>>\n54222e949682<\/span> (John<\/span> B<\/span>. Developer<\/span>    2018<\/span>-<\/span>01<\/span>-<\/span>08<\/span> 10<\/span>:57<\/span>:07<\/span> +<\/span>0000<\/span>  5<\/span>)    <p<\/span>>Here<\/span>'<\/span>s<\/span> some<\/span> text<\/span>.<\/<\/span>p<\/span>>\n5<\/span>f033c48d84a<\/span> (Jane<\/span> E<\/span>. Coder<\/span>        2017<\/span>-<\/span>05<\/span>-<\/span>24<\/span> 18<\/span>:25<\/span>:53<\/span> -<\/span>0600<\/span>  6<\/span>)\n5<\/span>f033c48d84a<\/span> (Jane<\/span> E<\/span>. Coder<\/span>        2017<\/span>-<\/span>05<\/span>-<\/span>24<\/span> 18<\/span>:25<\/span>:53<\/span> -<\/span>0600<\/span>  7<\/span>) <script<\/span>><\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
                        In this example, on May 24th, 2017, Jane E. Coder committed changes to the file. On January 8th, 2018, John B. Developer committed changes to the file. Because John committed changes after Jane, this output does not<\/strong> display any changes that Jane made to line 5 or<\/strong> the history of the other lines before Jane\u2019s commit.<\/p>\n
                        git clean<\/h3>\n
                        This command removes untracked files (files that Git does not manage) from the working tree.<\/p>\n
                        \n
                        git clean [options]<\/code><\/pre>\n<\/div>\n
                          \n
                        • \n
                          To display a list of untracked files to remove but not<\/strong> remove them, run this command with the -n<\/code> option.<\/p>\n<\/li>\n
                        • \n
                          To also remove untracked directories, run this command with the -d<\/code> option.<\/p>\n<\/li>\n<\/ul>\n
                          git config<\/h3>\n
                          This command retrieves or updates Git\u2019s global and repository settings in its configuration files.<\/p>\n
                          \n
                          git config [options]<\/code><\/pre>\n<\/div>\n
                          Git stores your settings in the following files:<\/p>\n
                            \n
                          • \/path-to-git\/etc\/gitconfig<\/code> \u2014 Global settings.<\/li>\n
                          • \/path-to-git\/config<\/code> \u2014 Repository settings.<\/li>\n
                          • \/home-directory\/.gitconfig<\/code> \u2014 A user configuration file.<\/li>\n
                          • \/home-directory\/.config\/git\/config<\/code> \u2014 A user configuration file.<\/li>\n<\/ul>\n
                            \n
                            Note:<\/div>\n
                            \n
                              \n
                            • In the paths above, path-to-git<\/code> represents the Git installation\u2019s absolute path and home-directory<\/code> represents a cPanel account\u2019s home directory (for example, the \/home\/user\/.gitconfig<\/code> file).<\/li>\n
                            • If both user configuration files exist and their values conflict, the system uses the values in the .gitconfig<\/code> file.<\/li>\n
                            • This command accepts many options for each of Git\u2019s configurable settings. To use this command, read Git\u2019s git config documentation.<\/li>\n<\/ul><\/div>\n<\/div>\n
                              git diff<\/h3>\n
                              This command compares changes between two commits, a commit and the current working tree, two branches or working trees, or two files.<\/p>\n
                              \n
                              git diff [options]<\/code><\/pre>\n<\/div>\n
                              By default, this command returns a comparison of the working tree and your last commit (the changes that Git would commit if you ran the git commit -a<\/code> command).<\/p>\n
                              You may wish to use the following common options:<\/p>\n
                                \n
                              • \n
                                To view a comparison of two branches, run the following command, where branch1<\/code> and branch2<\/code> represent the branches to compare:\n<\/p>\n
                                \n
                                git diff branch1..<\/span>branch2<\/code><\/pre>\n<\/div>\n<\/li>\n
                              • \n
                                To view a comparison of two commits, run the following command, where FirstSHA<\/code> and SecondSHA<\/code> represent the SHA-1 values for the two commits:\n<\/p>\n
                                \n
                                git diff FirstSHA..<\/span>SecondSHA<\/code><\/pre>\n<\/div>\n<\/li>\n
                              • \n
                                To only view differences between two versions of one file in a working tree, branch, or commit, specify that filepath as an argument. For example:\n<\/p>\n
                                \n
                                git diff branch1..<\/span>branch2 filename<\/code><\/pre>\n<\/div>\n
                                In the example above, branch1<\/code> and branch2<\/code> represent the branches from which Git will compare the contents of the filename<\/code> file.<\/li>\n<\/ul>\n
                                git grep<\/h3>\n
                                This command searches the current working tree for one or more patterns (generally, strings or regular expressions).<\/p>\n
                                \n
                                git grep [options] \"pattern\"<\/span><\/code><\/pre>\n<\/div>\n
                                In the example above, pattern<\/code> represents the data to query.<\/p>\n
                                  \n
                                • \n
                                  To perform a case-insensitive search, run this command with the -i<\/code> option.<\/p>\n<\/li>\n
                                • \n
                                  To use Perl-Compatible Regular Expressions (PCREs) in your patterns, run this command with the --perl-regexp<\/code> option. cPanel & WHM\u2019s implementation of Git automatically includes the necessary dependencies for this option.<\/p>\n<\/li>\n
                                • \n
                                  To return only files that include all of the specified patterns (when you run the command with multiple patterns), run this command with the --all-match<\/code> option. For example:\n<\/p>\n
                                  \n
                                  git grep --<\/span>all-<\/span>match \"string one\"<\/span> \"string two\"<\/span> \"string three\"<\/span><\/code><\/pre>\n<\/div>\n
                                  This example would return files that contain string one<\/code>, string two<\/code>, and<\/strong> string three<\/code>, but would not<\/strong> return files that only contain string two<\/code>.<\/li>\n
                                • \n
                                  To return file paths relative to the repository\u2019s main directory rather than the current directory, run this command with the --full-name<\/code> option.<\/p>\n<\/li>\n<\/ul>\n
                                  git log<\/h3>\n
                                  This command queries the commit logs for your current branch.<\/p>\n
                                  \n
                                  git log [options]<\/code><\/pre>\n<\/div>\n
                                    \n
                                  • \n
                                    To view only results from a specific range of commits, run the following command:\n<\/p>\n
                                    \n
                                    git log FirstSHA..<\/span>SecondSHA<\/code><\/pre>\n<\/div>\n
                                    In this example, FirstSHA<\/code> and SecondSHA<\/code> represent the SHA-1 values for the two commits.<\/p>\n
                                    \n
                                    Note:<\/div>\n
                                    \n
                                    If you do not specify a range of commits to query, this command queries all commits between the origin<\/code> commit and HEAD for the current branch.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n
                                  • \n
                                    To view only a specific number of the most recent log entries, run the following command, where num<\/code> represents the number of entries to return:\n<\/p>\n
                                    \n
                                    git log -<\/span>num<\/code><\/pre>\n<\/div>\n<\/li>\n
                                  • \n
                                    To view only log entries before or after a specific date, run one of the following commands, where date<\/code> represents the specified date:\n<\/p>\n
                                    \n
                                    \n\n\n
                                    \n
                                    1\n<\/span>2\n<\/span><\/code><\/pre>\n<\/td>\n
                                    		\n
                                    git<\/span> log<\/span> --<\/span>before<\/span>=date<\/span>\ngit<\/span> log<\/span> --<\/span>after<\/span>=date<\/span><\/code><\/pre>\n<\/td>\n<\/tr>\n<\/table>\n<\/div>\n<\/div>\n
                                    For date formatting options, read Git\u2019s git log documentation.<\/li>\n
                                  • \n
                                    To view only log entries for commits from a specific author, run the following command, where authorname<\/code> represents the author\u2019s name in their .gitconfig<\/code> file:\n<\/p>\n
                                    \n
                                    git log --<\/span>author=<\/span>authorname<\/code><\/pre>\n<\/div>\n<\/li>\n
                                  • \n
                                    To view only log entries that contain a specific pattern (generally, a string), run the following command, where pattern<\/code> represents the pattern to query:\n<\/p>\n
                                    \n
                                    git log --<\/span>grep=<\/span>pattern<\/code><\/pre>\n<\/div>\n
                                    If you include multiple patterns to query, use the --all-match<\/code> option to limit output to log entries that match all<\/strong> of the specified patterns.<\/li>\n<\/ul>\n
                                    \n
                                    Note:<\/div>\n
                                    \n
                                      \n
                                    • This command also accepts formatting options from the git diff<\/code> command.<\/li>\n
                                    • If you only require summarized commit log information, you may wish to use the git shortlog<\/code> command.<\/li>\n<\/ul><\/div>\n<\/div>\n
                                      git revert<\/h3>\n
                                      This command reverts existing commits within a specified range and then allows you to edit their commit messages.<\/p>\n
                                      \n
                                      git revert [options] commit1..<\/span>commit2<\/code><\/pre>\n<\/div>\n
                                      In the example above, commit1<\/code> and commit2<\/code> represent the SHA-1 values for the range of commits to revert.<\/p>\n
                                      \n
                                      Important:<\/div>\n
                                      \n
                                      To run this command, your working tree cannot<\/strong> contain uncommitted changes.<\/p>\n<\/p><\/div>\n<\/div>\n
                                      git shortlog<\/h3>\n
                                      This command produces a shortened version of the output of the git log<\/code> command. You may wish to use this command if, for example, you need to generate a list of changes for release notes or a change log.<\/p>\n
                                      \n
                                      git shortlog [options]<\/code><\/pre>\n<\/div>\n
                                      git stash<\/h3>\n
                                      This command uses several options to create, manage, and retrieve sets of changes (stashes). When you run this command without specified options, it defaults to git stash<\/code> save functionality.<\/p>\n
                                      \n
                                      git stash [options]<\/code><\/pre>\n<\/div>\n
                                      Use the following options to manage stashes:<\/p>\n
                                        \n
                                      • To create a new stash and return the current branch to its state in the HEAD<\/code> commit, run this command with the save<\/code> option. When you use this option, you can also use the -message<\/code> option to add a description to the stash. For example:\n
                                        \n
                                        git stash save -<\/span>message \"Description\"<\/span><\/code><\/pre>\n<\/div>\n
                                        In the example above, Description<\/code> represents the stash description.<\/li>\n
                                      • To return a comparison of stashed changes with the HEAD<\/code> commit when you created the stash, run this command with the show mystash<\/code> option.<\/li>\n
                                      • To list your current stashes, run this command with the list<\/code> option.<\/li>\n
                                      • To apply stashed changes to the current working tree and and remove the stash, run this command with the pop mystash<\/code> option.<\/li>\n
                                      • To apply stashed changes to the current working tree but not<\/strong> remove the stash, run this command with the apply mystash<\/code> option.<\/li>\n
                                      • To remove all stashes, run this command with the clear<\/code> option.<\/li>\n<\/ul>\n
                                        \n
                                        Note:<\/div>\n
                                        \n
                                        In the options above, mystash<\/code> represents the reflog entry or stash index for the desired stashed changes.<\/p>\n<\/p><\/div>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"
                                        Overview You can access all of Git\u2122\u2019s functionality via the command line. This document lists common commands and options that may assist you when you learn Git. Important: This document is not comprehensive. It intentionally omits information about intermediate and advanced Git functionality. For more information about additional commands and options, read Git\u2019s documentation. The …<\/p>\n","protected":false},"author":1,"featured_media":622,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/621"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=621"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/621\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/622"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=621"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=621"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=621"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}