Databases
StackOverflow2013
Postsdbo
POHow to prevent phabricator from eating my commit history
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to prevent phabricator from eating my commit history
    primarykey
    data
    text
    <p>Here is the scenario that is pretty much annoying me.</p> <p>Jack works in foobar a software house, Jack is a <a href="http://www.codinghorror.com/blog/2009/04/the-eight-levels-of-programmers.html">Working Programmer</a>, he loves coding and commits frequently. Paul who is jack's manager tells him that we are going to start using a new code review tool, phabricator. Jack complies, Jack creates a local branch and starts working. He adds features and commits to his local branch very frequently. Now at the end of the day he sends a phabricator request.</p> <pre><code>arc diff development </code></pre> <p>John who is jacks team member reviews his code and accepts his changes. Now Jack opens the terminal and moves to his repository directory. Jack types the following command to close the revision and merge his code with the development branch.</p> <pre><code>arc land --onto development </code></pre> <p>He sees the following message</p> <pre><code>Landing current branch 'feature-awesome-features'. Switched to branch development. Updating branch... The following commit(s) will be landed: b2ff76e Added the foo to bar 33f33ba Added a really important check which can destroy the project or save it 31a4c9a Added that new awesome feature 8cae3bf rewrote that awful code john wrote bc54afb bug fixes Switched to branch feature-awesome-features. Identifying and merging... Landing revision 'D1067: Added the awesome feature'... Rebasing feature-awesome-features onto development Already up-to-date. Pushing change... </code></pre> <p>Now jack opens Github to see his code , his beautiful commits. but what he sees is pure horror all of his commits have been replaced by a single commit which basically says something like this</p> <pre><code>Summary: Added the awesome feature Test Plan: do foo bar testing Reviewers: John Reviewed By: John CC: Paul Differential Revision: http://phabricator.foobar.com/D1067 </code></pre> <p>Now jack is sad, because he wants to see all of his commits, jack thinks that this commit makes him look like <a href="http://www.aaronstannard.com/post/2013/12/19/The-Taxonomy-of-Terrible-Programmers.aspx">The Hoarder</a> which he is not. He wants to fix this so he goes to ask a question on stackoverflow.</p> <pre><code>That how may he prevent phabricator from eating his commit history. </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMatthias
    1. USxeon111
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to prevent phabricator from eating my commit history
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to prevent phabricator from eating my commit history
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to prevent phabricator from eating my commit history
      1. This table or related slice is empty.
      1. VTUpMod
    1. COIf that's how everyone's merges look, why do you think you will be singled out? Anyway, the workaround is to have more smaller branches. In particular, don't commit unrelated changes on feature branches.
      singulars
      1. POHow to prevent phabricator from eating my commit history
      1. UStripleee
    2. CO+1 For question. Nice and suitable explanation. :)
      singulars
      1. POHow to prevent phabricator from eating my commit history
      1. USmrutyunjay
 

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