Skip to content

Policy on merging / rebase / squash #201

@consideRatio

Description

@consideRatio

In order to keep git version history tidy, I think it makes sense to always rebase->merge or squash->merge, and disable the plain merge button in repo settings.

I'm happy with either options of rebase/squash, but would like to see us do our best to keep PRs tightly scoped if we only do squashes.

example of tidy example of not tidy
Image Image

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