Doncuppjr
commented
6 days ago In my current architecture, using a "master" or "main" branch isn't practical. Those are just labels with no intrinsic meaning, and in my workflow, they don’t provide value.
Each branch in my system is versioned and serves as the authoritative source (or "master") for its respective major.minor release. This approach ensures that the installer for a given release always references the correct branch, avoiding disruptions caused by changes in other releases. Using tags, while an option, would require constantly moving them around to reflect updates—an unnecessarily tedious process for my needs.
Right now, my focus is on making all the features of the software work seamlessly, rather than restructuring my Git repository to align with prevailing conventions. Too often, opinions become doctrine, and that doctrine can dictate actions, steering everyone to the same, potentially limiting, outcomes. Challenging norms to create something better has always been one of my core values.
Dear @Doncuppjr,
I have seen a problem of branches:
First: the current default branch is old.
Second: It is possible to use main branch: master/main? It will be nice to import all from old branches into and add good tag in main branch.
In more: The tree of files section in SF is mixed, some folders with numbers, some folders with texts, etc.:
It is possible to move easily with FileZilla for example (without removal), the goal is to have good order
The goal is to have good tree for all, you and all people.
Of course, I can help you.
Thanks in advance.