Skip to content

Better way to handle merge conflicts #2

@aditeyabaral

Description

@aditeyabaral

Currently, the most latest version of files being committed is used to overwrite the remote. Is there is a way to handle merges and conflicts?

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions