Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This method will only give you the successful pushes, but it may still be useful to you:</p> <p>When you push to a branch in a remote that corresponds to one of your remote-tracking branches, and that push is successful, the remote-tracking branch will be updated. In the default case where you've cloned from a repository this typically means that successful pushes to <code>master</code> in the remote <code>origin</code> will update the remote-tracking branch <code>origin/master</code>. Changes to <code>origin/master</code> are recorded in the reflog, so you can find the successful pushes with:</p> <pre><code> git reflog show origin/master </code></pre> <p>For example, in one of my repositories, you'll see:</p> <pre><code>17f2303 refs/remotes/origin/master@{0}: fetch origin: fast-forward dd7e0ac refs/remotes/origin/master@{1}: fetch origin: fast-forward 1788ffe refs/remotes/origin/master@{2}: fetch origin: fast-forward 9763bbc refs/remotes/origin/master@{3}: fetch origin: fast-forward 058d0d6 refs/remotes/origin/master@{4}: fetch origin: fast-forward 921f0f1 refs/remotes/origin/master@{5}: fetch origin: fast-forward 8483afd refs/remotes/origin/master@{6}: update by push 18d527f refs/remotes/origin/master@{7}: update by push 1a0fc4a refs/remotes/origin/master@{8}: fetch origin: fast-forward b19afc6 refs/remotes/origin/master@{9}: fetch origin: fast-forward 9253285 refs/remotes/origin/master@{10}: fetch origin: fast-forward dfa664f refs/remotes/origin/master@{11}: fetch origin: fast-forward 30ee7c0 refs/remotes/origin/master@{12}: update by push ad11e76 refs/remotes/origin/master@{13}: fetch origin: fast-forward c337975 refs/remotes/origin/master@{14}: update by push 1ff03bd refs/remotes/origin/master@{15}: update by push 7fb1c8d refs/remotes/origin/master@{16}: fetch origin: fast-forward 452c8fa refs/remotes/origin/master@{17}: fetch origin: fast-forward 6c79a16 refs/remotes/origin/master@{18}: update by push 11d9c4a refs/remotes/origin/master@{19}: fetch origin: fast-forward </code></pre> <p>For example, you can tell from this that my most recent push updated <code>origin/master</code> from <code>18d527f</code> to <code>8483afd</code>.</p> <p>If you need to rely on this, you'll need to stop the reflog from expiring after the default time (90 days IIRC).</p>
    singulars
    1. This table or related slice is empty.
    1. POGet a List of all Pushes with Git
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMark Longair
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGet a List of all Pushes with Git
      singulars
      1. PTQuestion
    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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COPerfect! Thank you. FWIW, my reflog is showing entries from the last 9 months, and I haven't done anything to affect its behavior since I first installed.
      singulars
      1. PO
      1. USClayton
    2. CO@Clayton: That probably just means you haven't had `gc --auto` trigger yet; it'll expire reflogs older than that default 90 days. Just set `gc.reflogExpire` to `never` (or something larger) if you want things to stay that way.
      singulars
      1. PO
      1. USCascabel
 

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