Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is only my second post on stackoverflow, I hope it is helpful.</p> <p><strong>master branches</strong></p> <p><em>inside repo switch to master branch</em></p> <pre><code>git checkout master </code></pre> <p><em>now create a copy of the master branch sitting at tag 1.0</em></p> <pre><code>git checkout 1.0 git checkout -b master_1.0 </code></pre> <p><em>switch back to master branch</em></p> <pre><code>git checkout master </code></pre> <p><em>now create a copy of the master branch sitting at tag 1.1</em></p> <pre><code>git checkout 1.1 git checkout -b master_1.1 </code></pre> <p><strong>dev branches</strong></p> <p><em>switch back to master branch</em></p> <pre><code>git checkout master </code></pre> <p><em>now create a dev branch from master sitting at tag 1.0</em></p> <pre><code>git checkout 1.0 git checkout -b dev_1.0 </code></pre> <p><em>switch back to master branch</em></p> <pre><code>git checkout master </code></pre> <p><em>now create a dev branch from master sitting at tag 1.1</em></p> <pre><code>git checkout 1.1 git checkout -b dev_1.1 </code></pre> <p><em>if ok push changes to the remote</em></p> <pre><code>git push </code></pre> <p>At this point you would have 6 branches total. Your original master and dev plus the new copies. Development can take place on the newly created branches without impacting master. It may not be conventional to have a tag number in the branch name but it will accomplish the task of communicating quickly the branches origin or purpose. Further you can remove, merge, or re-create the branches easily.</p> <p><strong>To remove branches</strong></p> <p>remote - (don't forget the ":")</p> <pre><code>git push origin :BranchName </code></pre> <p>local - cannot be on the branch you are trying to delete, -D for un-merged branch</p> <pre><code>git branch -D BranchName </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POI really need help understanding how my git server is set up and what my branches are doing
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USdmasi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POI really need help understanding how my git server is set up and what my branches are doing
      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
    1. COThanks for the walk-through. Your post makes sense but I think my repo is messed up? When I go into my working directory, just for reference, and perform `git branch -a` I get `* devel` ` master` ` remotes/origin/devel` ` remotes/origin/master` Back in my master repo, `git branch -l` returns ` devel` `* master` which is what I'd expect. When I issue `git checkout master`, I get this error: `fatal: This operation must be run in a work tree`. Reviewing this error says "clone it locally" or "tell it work-tree" but why clone it (it's the master repo, isn't it?) and what's my work tree?
      singulars
      1. PO
      1. USharperville
    2. COI wish I could help more, but I haven't encountered that issue before. I did a quick google search for "git fatal: This operation must be run in a work tree". The first 3 search results are from stackoverflow. I quickly reviewed them and there may be more helpful info in those tickets. Best of luck, and please post back your resolution for the working tree issue. I'd like to understand it better as well.
      singulars
      1. PO
      1. USdmasi
    3. COShould I perform these steps in the repo on my server or my local repo? I can't do it on my server because my repo is bare, which according to what I've read, I want a bare repo so I can collaborate with others. If I try `git checkout 1.0` on my local repo, it says `error: pathspec '1.0' did not match any file(s) known to git.` Stuck again.
      singulars
      1. PO
      1. USharperville
 

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