Timeline for rebase your own branch and force push
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2019 at 8:22 | vote | accept | Antony Makaruk | ||
| Feb 12, 2018 at 19:12 | history | edited | Peter Green | CC BY-SA 3.0 |
added 14 characters in body
|
| Sep 13, 2017 at 16:18 | history | edited | Peter Green | CC BY-SA 3.0 |
added 8 characters in body
|
| Sep 13, 2017 at 11:44 | vote | accept | Antony Makaruk | ||
| Sep 13, 2017 at 11:44 | |||||
| Sep 13, 2017 at 11:40 | comment | added | Antony Makaruk | In my branch only I do changes, so I push my changes in this branch to remote server only for backup my work and then merge it to master when I finished. As I understand - the only two option exist to squash my commits... the first is - in process of merging by another team member(but it's not very convenient in our case) and the second - is to do it by myself and then provide for merge a finished branch. | |
| Sep 13, 2017 at 11:24 | history | answered | Peter Green | CC BY-SA 3.0 |