Skip to content

Branch naming #6

Description

@jhcole

When I setup this organization, I tried to keep the master branch matched with upstream because I imagined this would make for easier pulls from upstream. I now realize this was a poor choice. To follow convention, it will be better for our main branch(s) to be called master (instead of fozland). The branch that tracks with upstream should be called ... 'upstream'. To fix this I need to do some branch renaming in nearly every repo in the organization.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions