Picture

Ivan @markupdev_I

Joined June 2015
  • Tweets
    11K
  • Followers
    94
  • Following
    3K
  • Likes
    4K
markupdev_I Profile Picture

Ivan @markupdev_I

8 years ago

Free bootstrap admin template - Matrix admin | Wrappixel wrappixel.com/templates/matr… via @WrapPixel

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

For example, take the following commits on master:

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

This is not an error message and is nothing to be worried about. This is simply a notice that you are not attached to an actual branch.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

state without impacting any branches by performing another checkout.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

You are in 'detached HEAD' state. You can look around, make experimental changes and commit them, and you can discard any commits you make

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

What is a "detached head"?

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

See also What is local history/shared history?

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

everybody you need to in order to make sure important changes are pushed before a history modification.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

Problems occur because you can rarely be sure you’ve communicated with

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

changing history is very problematic and should only be done in extreme cases where the cost is understood.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

On mainline branches that anyone could base off of for any arbitrary work (eg “master” or “develop”),

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

This is also usually not a problem if you expect branches to be short lived and highly collaborative (assuming high communication).

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

On shared feature branches, the burden of communication increases to the people who are developing with you on that branch.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

number of people you need to communicate with is usually limited to just you.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

Rewriting local history up to the point of shared changes is rarely a problem. The

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

It is important that changes are resolved before history is rewritten and that usually means waiting for all important work to be pushed.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

have already based development off the history that is to be changed.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

Rewriting history has a number of legitimate uses but requires communication proportional to the number of people who

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

the same changes now look to be two different changes at different times.

markupdev_I Profile Picture

Ivan @markupdev_I

9 years ago

the SHAs have changed and commits that should refer to

Trends for United States

Iowa
21,4 B posts
Karen
198 B posts
San Jose State
2.757 posts
#UFCParis
14,5 B posts
Baylor
5.599 posts
Duke
22 B posts
Drew Allar
Livingstone
2.323 posts
Davey Johnson
6.552 posts
SJSU
1.667 posts
Sam Patterson
Elizabeth Warren
49,4 B posts
Duce Robinson
Sperry
UConn
2.688 posts
Gronowski
Anthony Hill
Thug
133 B posts
Gophers
1.544 posts
#Illini

You might like

Aforizma cümleler,Serap Köşkdere sözleri📚 Takip önerisi @LahzaOkuyoruz #takibetakip
Merkürr
@yrndnhbrsz
290 Followers
Anass Amrani
@yuthemess
196 Followers