Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <h2>Update:</h2> <p>Because of changes to how tracking branches are created and pushed I no longer recommend renaming branches. This is what I recommend now:</p> <p>Make a copy of the branch at its current state:</p> <pre><code>git branch crazyexperiment </code></pre> <p>(The <a href="http://git-scm.com/docs/git-branch" rel="noreferrer"><code>git branch &lt;name&gt;</code></a> command will leave you with your current branch still checked out.)</p> <p>Reset your current branch to your desired commit with <a href="http://git-scm.com/docs/git-reset" rel="noreferrer"><code>git reset</code></a>:</p> <pre><code>git reset --hard c2e7af2b51 </code></pre> <p>(Replace <code>c2e7af2b51</code> with the commit that you want to go back to.)</p> <p>When you decide that your crazy experiment branch doesn't contain anything useful, you can delete it with:</p> <pre><code>git branch -D crazyexperiment </code></pre> <p>It's always nice when you're starting out with history-modifying git commands (reset, rebase) to create backup branches before you run them. Eventually once you're comfortable you won't find it necessary. If you do modify your history in a way that you don't want and haven't created a backup branch, look into <a href="http://git-scm.com/docs/git-reflog" rel="noreferrer"><code>git reflog</code></a>. Git keeps commits around for quite a while even if there are no branches or tags pointing to them.</p> <h2>Original answer:</h2> <p>A slightly less scary way to do this than the <code>git reset --hard</code> method is to create a new branch. Let's assume that you're on the <code>master</code> branch and the commit you want to go back to is <code>c2e7af2b51</code>.</p> <p>Rename your current master branch:</p> <pre><code>git branch -m crazyexperiment </code></pre> <p>Check out your good commit:</p> <pre><code>git checkout c2e7af2b51 </code></pre> <p>Make your new master branch here:</p> <pre><code>git checkout -b master </code></pre> <p>Now you still have your crazy experiment around if you want to look at it later, but your master branch is back at your last known good point, ready to be added to. If you really want to throw away your experiment, you can use:</p> <pre><code>git branch -D crazyexperiment </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POHow do you roll back (reset) a Git repository to a particular commit?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USNeall
    1. USNeall
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks - might not have been what the poster asked for, but much less anxiety-inducing for me.
      singulars
      1. PO
      1. USMatt Parker
    2. CODealing with a remote repository (such as Github), you may have to do a 'git push -f origin master' because of the non-fastforwards to get master to look like it did at the specified commit, but this method is much cleaner than reset.
      singulars
      1. PO
      1. USjcalvert
    3. COgit reset --hard is not that particularly dirty. It is introduced in nearly every git tutorial available as the proper method to undo changes in your own tree. If not in basic features, at least in intermediate ones. If you somehow get into an unknown state/HEAD, there's always git reflog which tells the history of HEAD regardless of branches. Pick a proper commitid from there, and branch from it or git reset --hard with that.
      singulars
      1. PO
      1. USkauppi
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload