Timeline for Understanding whether 'rebase' can be used in a team environment?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 4, 2023 at 0:07 | audit | Suggested edits | |||
| Jun 4, 2023 at 0:08 | |||||
| May 19, 2023 at 22:11 | answer | added | Guildenstern | timeline score: 3 | |
| May 19, 2023 at 21:46 | comment | added | Guildenstern | Not using rebase is fine until you learn more about it. Some people never use it. | |
| May 19, 2023 at 17:26 | review | Close votes | |||
| May 24, 2023 at 3:08 | |||||
| May 19, 2023 at 15:58 | answer | added | Jörg W Mittag | timeline score: 12 | |
| May 19, 2023 at 15:44 | comment | added | Laiv |
is to simply avoid using rebase altogether in the team, with us all being Git novices Unless you are all experts or well-versed in git, I would still advise against rebasing branches no matter how expert you or half of the team is. It only takes one of you to cause the chaos.
|
|
| May 19, 2023 at 14:32 | answer | added | DavidT | timeline score: 4 | |
| May 19, 2023 at 14:25 | comment | added | Caleth | A change is public if someone has fetched it. The answer will depend on whether the repo on your machine is accessed by your team, or you only go via a central location | |
| May 19, 2023 at 14:14 | answer | added | Stack Exchange Broke The Law | timeline score: 2 | |
| May 19, 2023 at 13:45 | history | asked | Andrew Stephens | CC BY-SA 4.0 |