Skip to content

tags named refs/head/master create git confusion #146

@stnava

Description

@stnava

Describe the bug
Creating a tag with the same name as the master branch is bad practice.

The issue is created by a GitHub action that pushes to neuroconductor releases automatically. It would be better if the created tag was only pushed if it was an actual tag - instead of all commits.

To Reproduce
Try to make a git push origin master commit after the refs/head/master tag is created ... then you will get

error: dst refspec refs/heads/master matches more than one
error: failed to push some refs to 'github.com:ANTsX/ANTsRCore.git'

Expected behavior

Should be able to push to master branch.

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