StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20830564
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-29T22:01:16.467
FavoriteCount
0
LastActivityDate
2013-12-29T22:01:16.467
LastEditDate
LastEditorUserId
0
OwnerUserId
1870481
ParentId
20829165
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
I seems like you are trying to emulate the old clearcase induced workflow by means of git. This is usually not a good idea. (Even though your team is used to the good old workflow.) If clearcase works fine for you, just stick with clearcase. If you had a good reason to switch to git, use the chance to look at you business workflows and build a suitable git workflow around it. Ask yourself some questions: <ul> <li>What kind of files are you working with? (code, documentation, ...)</li> <li>Why do you need to change the files at all? (new features, bug fixes, ...)</li> <li>Why do different team members need to work on the same files? (Maybe you could improve the assignment of your tasks or the structure of your project?)</li> </ul> Next set up some meaningful branches. Currently it seems like you are doing all your work on one single master branch, but branches in git are extremely lightweight you really should think about developing features in separate branches and do explicit merges. Please don't abuse your CI system to push commits around and enforce automatic merges unless you have a very good reason for this. A "push" usually means, you have finished your work and are ready to share it with your other team members. Your CI system usually cannot decide whether the work is finished or in some buggy experimental state. I would recommend setting up a some branches, give them a good semantic and set up you CI system to check those branches whenever they are updated. - Things like push and merge should always be done explicitly and intentional by a real person. Otherwise strange things will happen, sooner or later. But all of this depends on your specific situation. There is no recipe which works for everyone.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGIT & Jenkins - how to dilemma
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USmichas
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POGIT & Jenkins - how to dilemma
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

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.