branching

To create a Git branch without inheriting upstream tracking, you must ensure the branch originates from a local reference. This approach fetches the latest changes, checks out a local source, and creates a local branch with no upstream link, requiring explicit confirmation before the first push.

Your new Git branch tracks a remote upstream automatically when it inherits tracking configuration from the source branch. To prevent this, you must create branches exclusively from local refs and verify that no upstream tracking is configured before pushing.

The safest workflow for branching off a non-main Git branch involves prompting warnings when the source is non-main and requiring explicit user confirmation of intent. This ensures you safely create feature or fix branches from local sources without unintended upstream inheritance.

To enforce folder-based naming conventions when starting a new feature branch, you can apply policy-driven rules that generate safe, folder-based branch names with type prefixes. This requires asking for the branch purpose and source before proposing a name.

Yes, you can prevent accidental upstream pushes when creating local Git feature branches by verifying no upstream is configured after branch creation. This deterministic branching step requires explicit user confirmation before proceeding with the first push.

Creating Git branches directly from remote tracking refs carries the limitation of dangerous upstream tracking inheritance. This risk necessitates a workflow that checks out a local source first, ensuring no upstream is inherited and requiring confirmation before pushing.