4 ms·

I think a lot of people drop any wrong information. It's a waste of time to think about wrong information. This comic presents a scenario where someone believe

by csours 3y ago

I think a lot of people drop any wrong information. It's a waste of time to think about wrong information. This comic presents a scenario where someone believes wrong information: git branches have rules. Git branches do not in fact have rules. This is wrong information. Why would we talk about wrong information? We talk about wrong information because other people do not have up to date and correct information. We can try to just update their information to be correct, but that does not always work. In some cases they have built a structure of reasoning based on their belief. It is traumatic to destroy this structure of reasoning without providing a replacement. Thus it can be helpful to understand the bad reasoning (based on wrong information) in order to communicate more effectively.

cryptonector 3y ago
Git branches do have rules. The most basic rule is that if you have a branch checked out and you add a commit, then the branch name moves. Upstreams can also have rules like "no history rewriting".
- csours 3y ago
  Thank you for more correct information.
- jgavris 3y ago
  Git ‘remotes’ can have rules (hooks that run on push, and decline). GitHub has ‘branch protection’ which prevents various changes. But GitHub is not Git. A common misconception lately due to its popularity. Git itself is nothing more than a set of tools to manage the versions of a repository. How you choose to use it is up to you, and what you allow. Solo developer? Rebase, or don’t. Do you collaborate? Maybe consider using a SaaS product like GitHub and setup your rules.
  - cryptonector 3y ago
    > Git itself is nothing more than a set of tools to manage the versions of a repository. "Git" is also the protocol, not just the implementation. Indeed, here I'm referring to the Git protocol more than to the Git implementation. There are multiple implementations of the Git protocol. GitHub is but one of several. > But GitHub is not Git. To the client it's indistinguishable.

by csours 3y ago

cryptonector 3y ago

Git branches do have rules. The most basic rule is that if you have a branch checked out and you add a commit, then the branch name moves. Upstreams can also have rules like "no history rewriting".

csours 3y ago
Thank you for more correct information.
jgavris 3y ago
Git ‘remotes’ can have rules (hooks that run on push, and decline). GitHub has ‘branch protection’ which prevents various changes. But GitHub is not Git. A common misconception lately due to its popularity. Git itself is nothing more than a set of tools to manage the versions of a repository. How you choose to use it is up to you, and what you allow. Solo developer? Rebase, or don’t. Do you collaborate? Maybe consider using a SaaS product like GitHub and setup your rules.
- cryptonector 3y ago
  > Git itself is nothing more than a set of tools to manage the versions of a repository. "Git" is also the protocol, not just the implementation. Indeed, here I'm referring to the Git protocol more than to the Git implementation. There are multiple implementations of the Git protocol. GitHub is but one of several. > But GitHub is not Git. To the client it's indistinguishable.