Skip to content

feat: publish to two different remote VCS #149

@Sieboldianus

Description

@Sieboldianus

My situation may appear a little bit untypically, but perhaps this is already implemented:

  • we have a closed Gitlab instance that we use for internal software development
  • we publish some of our branches/tools to Github, for external code collaboration

So far, I've only released releases in Github, because it was not possible in python-semantic-release to setup custom Gitlab instances.

Since GL_TOKEN became available, I'd also like to publish releases to the master branch on our custom Gitlab instance.

However, python-semantic-release seems to only use the remote that is set as default git remote. Is there any way to have it simultaneously publish releases to both Github and Gitlab using GH_TOKEN (e.g. remote origin) and GL_TOKEN (e.g. remote gl_origin)?

Alternatively, manually publishing/updating all releases to Gitlab would be totally ok for me, if there was such an option..

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmedPrevent from becoming stalefeatureA new feature or a feature requestneeds-updateNeeds status update from maintainers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions