Ejemplos de Nombres de Ramas Git

# Valid Git Branch Names Following Conventions
# These branch names follow Git branch naming conventions and common workflow patterns

# Feature branches (new features development)
feature/add-user-authentication
feature/new-dashboard-ui
feature/payment-integration
feature/user-profile-page
feature/email-notifications
feature/search-functionality
feature/api-refactoring
feature/data-export-feature

# Bugfix branches (bug fixes)
bugfix/fix-login-validation
bugfix/memory-leak-fix
bugfix/resize-image-bug
bugfix/database-connection-issue
bugfix/ssl-certificate-fix
bugfix/loading-timeout-fix

# Hotfix branches (urgent production fixes)
hotfix/security-patch-2024
hotfix/critical-bug-fix
hotfix/emergency-deployment
hotfix/production-crash-fix
hotfix/performance-hotfix

# Release branches (release preparation)
release/v1.2.0
release/v2.0.0-beta
release/v1.5.0-rc1
release/v3.1.0-stable

# Development branches
develop/api-refactoring
develop/frontend-updates
develop/backend-optimization
develop/infrastructure-changes

# Fix branches
fix/navigation-bug
fix/currency-conversion
fix/session-timeout
fix/caching-issue

# Custom workflow branches
feature/JIRA-123-user-auth
bugfix/BUG-456-login-error
hotfix/HOT-789-security-fix
feature/EPIC-101-dashboard

# Invalid Git Branch Names - Forbidden Characters
# These branch names contain characters that Git does not allow or that cause issues

# Branch names with tilde (~) - Git reserves ~ for special operations
feature~test
bugfix~update
release~v1.0

# Branch names with at sign (@) - Git uses @ for reflog references
bugfix@123
feature@new
hotfix@urgent

# Branch names with spaces - Spaces cause command-line parsing issues
feature new-feature
bug fix/login-error
release v1.0.0

# Branch names with caret (^) - Git uses ^ for parent references
release^v1.0
feature^update
test^branch

# Branch names with colon (:) - Git uses : for deleting and updating refs
test:branch
feature:new-ui
release:v1.0

# Branch names with asterisk (*) - Shell wildcard character
feature*test
bugfix*fix
release*final

# Branch names with question mark (?) - Wildcard character
feature?test
bugfix?fix
release?candidate

# Branch names with square brackets - Can cause issues in some shells
feature[test-case]
bugfix[urgent]
release[v1.0]

# Branch names with backslash - Path separator on Windows
feature\test
bugfix\fix
release\final

# Branch names with vertical bar - Shell pipe character
feature|test
bugfix|urgent
release|candidate

# Branch names with semicolon - Command separator
feature;test
bugfix;fix
release;final

# Branch names with commas - Can cause parsing issues
feature,test
bugfix,fix
release,candidate

# Branch names with double quote - Escaping issues
feature"test
bugfix"fix
release"final

# Branch names with single quote - Escaping issues
feature'test
bugfix'fix
release'final

# Branch names with exclamation mark - History expansion in some shells
feature!test
bugfix!urgent
release!final

# Branch names with hash (#) - Comment character in some contexts
feature#123
bugfix#456
release#789

# Branch names with dollar sign ($) - Variable expansion
feature$test
bugfix$fix
release$final

# Branch names with percent sign (%) - Job control in some shells
feature%test
bugfix%fix
release%final

# Branch names with ampersand (&) - Background job character
feature&test
bugfix&fix
release&final

# Branch names with parentheses - Can cause shell parsing issues
feature(test)
bugfix(fix)
release(final)

# Branch names with braces - Expansion in some shells
feature{test}
bugfix{fix}
release{final}

# Branch names with equals sign - Assignment operator
feature=test
bugfix=fix
release=final

# Branch names with plus sign - Can be confused with merge operations
feature+test
bugfix+fix
release+final

# Branch names with less than/greater than - Redirection operators
feature<test>
bugfix<fix>
release<final>

# Invalid Git Branch Names - Slash Issues
# These branch names have problems with slash placement or consecutive slashes

# Branch names starting with slash (/) - Invalid in Git
/feature/test
/bugfix/fix
/release/v1.0
/hotfix/urgent
/develop/main

# Branch names ending with slash (/) - Invalid in Git
feature/test/
bugfix/fix/
release/v1.0/
hotfix/urgent/
develop/main/

# Branch names with consecutive slashes (//) - Causes confusion
feature//test
bugfix//fix
release//v1.0
hotfix//urgent
develop//main

# Branch names with multiple consecutive slashes
feature///test
bugfix////fix
release/////v1.0

# Branch names starting and ending with slash
/feature/test/
/bugfix/fix/
/release/v1.0/

# Branch names with slash in invalid positions
//feature/test
feature//test//
///test///

# Branch names with only slashes
//
///
////

# Branch names with slash followed by invalid character
/feature/test~
/bugfix/fix@
/release/v1.0!

# Branch names with spaces around slashes
feature / test
bugfix / fix
release / v1.0

# Branch names with tab or newline around slashes (shown as escape sequences)
feature/\ttest
bugfix/\nfix
feature/\rrelease

# Branch names with mixed slashes (though Git only uses forward slash)
feature\test
bugfix/fix\mixed
release\v1.0

# Empty branch name components between slashes
feature//test
bugfix/fix//
release//v1.0//
feature/:///test

# Branch names with dot after slash
feature/.test
bugfix/.fix
release/.v1.0

# Branch names with slash and dot sequence
feature/./test
bugfix/../fix
release/./v1.0

# Branch names with multiple dots after slash
feature/...test
bugfix/....fix
release/.....v1.0

# Branch names with slash and lock file extension
feature/test.lock
bugfix/fix.lock
release/v1.0.lock

# Branch names that look like Git paths
refs/heads/feature/test
refs/heads/main
refs/tags/v1.0
refs/remotes/origin/main

# Branch names with excessive nesting
feature/level1/level2/level3/level4/level5/test
bugfix/a/b/c/d/e/fix
release/v1/v2/v3/v4/v5/v6/0

# Git Reserved and Protected Branch Names
# These branch names are reserved by Git or commonly protected in repositories

# Git's built-in branch names
HEAD
FETCH_HEAD
ORIG_HEAD
MERGE_HEAD
CHERRY_PICK_HEAD
REVERT_HEAD
REBASE_HEAD
REVERT_HEAD

# Common protected main branches (when branch protection rules are enabled)
main
master
develop
dev
staging
production

# Git reference names (cannot be used as branch names)
heads/main
heads/feature/test
heads/develop
tags/v1.0
tags/v2.0.0

# Remote tracking names (cannot be used as local branch names)
origin/main
origin/develop
origin/master
upstream/main
github/main

# Git internal references
refs/heads/main
refs/heads/master
refs/heads/develop
refs/tags/v1.0.0
refs/remotes/origin/main
refs/stash
refs/notes/commits

# Special Git reflog references
HEAD@{1}
HEAD@{yesterday}
main@{1}
master@{0}

# Branch names ending in .lock (reserved by Git for lock files)
main.lock
master.lock
feature.lock
test.lock

# Branch names that look like Git objects
feature/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
bugfix/fake-hash-name-123456789012345678901234

# Branch names conflicting with Git commands
init
clone
add
commit
push
pull
merge
rebase
checkout
branch
tag
status
log
fetch

# Git configuration-related names
config
modules
info
hooks
objects
refs
packed-refs

# Git worktree-related names
worktrees
commondir

# Branch names with Git special prefixes
refs/
refs/heads/
refs/tags/
refs/remotes/
refs/notes/

# Common release branch names (often protected)
release
stable
production
prod

# Prefixes reserved for Git's internal use
refs/bisect/
refs/rewritten/
refs/replace/

# Branch names that are Git environment variables
GIT_HEAD
GIT_DIR
GIT_WORK_TREE

# Git special file and directory names
.git
.gitignore
.gitattributes
.gitmodules
.gitkeep
.gitreview

# Branch names that could conflict with git submodule operations
submodule
submodule-init
submodule-update

# Branch names used by common Git workflows
gh-pages
pages
heroku
preview
canary
next
premium

# Real-World Messy Git Branch Names
# Examples of actual problematic branch names found in real projects

# Incorrect capitalization (mixing cases)
FEATURE/add-user-123
Feature/New-Dashboard
BuGfIx/Login-Error
HOTFIX/security-patch-2024
ReLeAsE/v1.0.0

# Branch names with parentheses (common in corporate environments)
feature(add user)
bugfix(fix login)
hotfix(urgent fix)
release(version 1.0)
test(branch name)

# Branch names with issue tracker formatting variations
fix bug#123
feature#456-new-ui
bugfix#789-login-error
hotfix#101-security
release#202-v2.0

# Branch names with special characters and symbols
feature/..test
bugfix/...fix
feature/@@urgent
hotfix/@@@emergency
test/..branch..

# Branch names with lock file extensions (accidentally added)
feature/test.lock
release/v1.0.lock
bugfix/fix.lock.lock
hotfix/urgent.lock.bak

# Branch names with square brackets (JIRA-style tags)
feature/[TEST-123]add-user
bugfix[BUG-456]fix-login
hotfix[HOT-789]security-fix
release[REL-101]v2.0
feature[PROJ-202]new-feature

# Branch names with question marks (uncertainty markers)
feature?test
bugfix?maybe-fix
hotfix?urgent-fix
release?version-number
feature/what-is-this

# Branch names with unintended spaces (not properly escaped)
feature add user authentication
bug fix login validation error
hot fix security patch 2024
release version 1.0.0 beta
develop api refactoring work

# Branch names with underscores instead of hyphens (non-standard)
feature/add_user_authentication
bugfix/fix_login_validation
hotfix/security_patch_2024
feature/new_dashboard_ui
develop/api_refactoring

# Branch names with camelCase (inconsistent naming)
feature/addUserAuthentication
bugfix/fixLoginValidation
hotfix/securityPatch2024
feature/newDashboardUI
develop/apiRefactoring

# Branch names with mixed separators
feature/add-user_authentication
bugfix/fix.login-validation
hotfix/security_patch-2024
feature/new_dashboard-ui
develop/api-refactoring_work

# Branch names with unnecessary prefixes
my-feature/add-user
test-branch/fix-bug
wip/work-in-progress
backup/save-point
tmp/temporary-work

# Branch names with descriptive but problematic characters
feature/user@authentication
bugfix/login#validation
hotfix/security!patch
release/version~1.0
feature/test:case

# Branch names with sequential numbering done incorrectly
feature/add-user-1
feature/add-user-2
feature/add-user-3
bugfix/fix-1
bugfix/fix-2

# Branch names with employee initials or names (privacy concern)
feature/jk-user-auth
feature/ab-dashboard-ui
bugfix/md-login-fix
hotfix/xyz-security-patch
feature/qs-api-refactor

# Branch names with corporate terminology
feature/Q1-add-user
bugfix/Q2-fix-login
hotfix/Q3-security-patch
release/Q4-v1.0
feature/H1-planning

# Branch names with status indicators that are confusing
feature/WIP-add-user
bugfix/DONE-fix-login
hotfix/INPROGRESS-security
feature/REVIEW-dashboard
feature/MERGE-api-work

# Branch names with long descriptions
feature/add-user-authentication-with-oauth2-and-social-login-integration
bugfix/fix-validation-error-in-login-form-when-user-enters-special-characters
hotfix/emergency-security-patch-for-cve-2024-12345-vulnerability-in-authentication-system
release/final-release-version-1.2.3.4.5-with-all-bug-fixes-and-new-features

# Branch names with copy-paste errors
featurefeature/add-user
bugfixbugfix/fix-login
hotfixhotfix/security-patch
release/release/v1.0
origin/feature/test

# Branch names with escape characters showing through
feature/add\\user
bugfix/fix\\login
hotfix/security\\patch
release/version\\1.0
feature/\"test\"

# Branch names with URL encoding remnants
feature%2Fadd-user
bugfix%3Afix-login
hotfix%20security-patch
release%3Fv1.0
feature%40test

# Branch names with emoji and unicode (while supported, can cause issues)
feature/✨add-user
bugfix/🐛fix-login
hotfix/🔥security-patch
feature/🎉new-dashboard
release/🚀v1.0