On 2026-01-22 23:23 (-4), Shay wrote:
> 
> You’re making it hard. Why are you branching at all? Don’t get caught up in
> trying to do what “advanced users” do, because advanced isn’t linear. Learn to
> use the parts *you* need, because you may never use the parts you imagine you
> *might* need, even if you *do* become advanced.

I'm branching because I have future plans and tentative ideas for some
of my projects that I'm not ready to incorporate into the main project.
I also have user manuals and READMEs for my Object Collection
contributions that will need to be updated once the Object Collection is
rebooted.  Up till now, I've been renaming files or keeping them in
separate directories--or, in the case of the user manuals and READMEs,
having to revert the files every time I push an update to GitHub.  This
is rather cumbersome, and git branches seems (to me) to be suitable for
this sort of workflow.

> Branching itself is easy enough. Maybe find a workflow where it’s required. Fork
> a repo, make a change, then submit a pull request. You don’t even need to be
> able to code. Submit a request for typos in the README if you like. That is
> straightforward, done the same way by thousands, clearly documented online, and
> a way to use tools for the exact purpose they were designed.

Branching seems super simple on paper, but in practice, it doesn't
behave the way I expect it to.  There is something conceptually
fundamental about git that I do not understand, and I feel that until I
do understand whatever it is that I'm missing, I will continue to be
frustrated with git, no matter how easy or "advanced" the feature.

I think I need to take a class.  Not a video, not a tutorial, but an
actual class.

Post a reply to this message