Not updating since new heads added

If you want to create a new branch to retain commits you create, you may do so (now or later) by using -b with the checkout command again.

Example: git checkout -b new_branch_name HEAD is now at 123be6a...

not updating since new heads added-63

It starts with web pages captured during previous crawl processes and adds in sitemap data provided by webmasters.

As it browses web pages previously crawled, it will detect links upon those pages to add to the list of pages to be crawled.

Once your website or blog is indexed, you’ll start to see more traffic from Google search.

Plus, getting your new content discovered will happen faster if you have set up sitemaps or have a RSS feed.

Initial ((123be6a...)) $ git log --oneline 123be6a Initial ((123be6a...)) $ cat .git/HEAD 123be6a76168aca712aea16076e971c23835f8ca ((123be6a...)) git checkout master Previous HEAD position was 123be6a...

Initial Switched to branch 'master' (master) $ cat .git/HEAD ref: refs/heads/master Working with (or on) a detached head isn't a problem.

Bear in mind, however, that finding a commit is dependent on what you do with that hash.

Typically, you will create a new branch (say, it's a bug fix for a previously released bit of code), or you end up tagging it with a hot fix identifier.

This occurs when you are dealing with bisects, or if you want to simply check out a specific version of a previous commit.

There's also nothing to stop you working on this unnamed branch, either; you can keep going and committing as long as you want.

Now we’ll take a look at how to get sitemaps on your website and links to it that will help the Googlebot discover new websites, blogs, and content.