Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 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 Commented May 19, 2023 at 14:25
  • 2
    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. Commented May 19, 2023 at 15:44
  • 2
    Not using rebase is fine until you learn more about it. Some people never use it. Commented May 19, 2023 at 21:46