Skip to content

Allow pushing from different branches than "main" or "master" #198

Description

@iduuck

I would like to suggest that it would be configurable where to push from for production.
I was recently working on a project, which has a development and a production branch. However, (trying) to deploy with production deploy results in the following:

❯ production deploy
error: src refspec master does not match any
error: failed to push some refs to 'https://git.heroku.com/XXX.git'

While I understand, that this is also a "security" issue, for not pushing wrong branches to production environments, it would be nice to configure, how to push to production.


Lines, where the magic happens: https://github.com/thoughtbot/parity/blob/main/lib/parity/environment.rb#L42-L63

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions