Scribd Logo
Upload

Welcome to Scribd!

  • Ankit Pangasa: Become Better at

    Uploaded by

    INV SHR
    15 views8 pages
    The document provides 5 tips for better Git branch naming: 1) Avoid only numeric names and use descriptive names to indicate what the branch deals with. 2) Keep branch names short and simple to avoid long ugly names. 3) Use hyphens or underscores to separate words and make branch names more readable. 4) Specify the branch intent such as "feature" or "bug" to help others understand what the branch is for. 5) Include the author name to help identify who created the branch from the name.

    Original Description:

    git instructions

    Original Title

    git

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document provides 5 tips for better Git branch naming: 1) Avoid only numeric names and use descriptive names to indicate what the branch deals with. 2) Keep branch names short and simple to avoid long ugly names. 3) Use hyphens or underscores to separate words and make branch names more readable. 4) Specify the branch intent such as "feature" or "bug" to help others understand what the branch is for. 5) Include the author name to help identify who created the branch from the name.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    15 views8 pages

    Ankit Pangasa: Become Better at

    Uploaded by

    INV SHR
    The document provides 5 tips for better Git branch naming: 1) Avoid only numeric names and use descriptive names to indicate what the branch deals with. 2) Keep branch names short and simple to avoid long ugly names. 3) Use hyphens or underscores to separate words and make branch names more readable. 4) Specify the branch intent such as "feature" or "bug" to help others understand what the branch is for. 5) Include the author name to help identify who created the branch from the name.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    of 8

    Become better at

    GIT
    Ankit Pangasa
    5 TIPS
    FOR BETTER
    GIT
    BRANCHES
    NAMES

    Ankit Pangasa
    Avoid only
    Numeric
    names
    Only numbers will make
    it difficult to deduce
    what the branch deals
    with.

    980909099
    Would you like seeing a branch name like
    above?

    Ankit Pangasa
    Short and
    Simple
    Having non precise
    and long names just
    makes the name look
    more ugly

    branch_234_add_support_to_sort_all_the_nu
    mbers_in_ascending_order

    Ankit Pangasa
    Use hyphen
    or
    underscore
    Using these
    characters make the
    names more readable.

    bug234addingdependencies

    bug_234_adding_dependencies

    Ankit Pangasa
    Specify
    branch
    intent
    Using branch intent
    helps anyone
    understand what the
    branch is dealing with

    123_adding_ui_elements

    feature_123_adding_ui_elements

    Ankit Pangasa
    Use Author
    Name
    Branches with Author
    name helps people to
    quickly identify author
    from the branch name
    itself

    <authorName>_<ChangeType>_<ShortName>
    john_bug_fixBannerPosition

    Ankit Pangasa
    THANK YOU

    Ankit Pangasa

    You might also like