• I'd be willing to implement this feature (contributing guide)

Description

For users moving from lerna, lerna publish was creating and pushing release tag to remote origin (besides publishing to npm).

With nx release, one needs to handle things on his own if one has requirements to actually create the tag only from production pipeline.

Note: we dont(cant) use nx release changelog, nor github release ATM

Motivation

Suggested Implementation

nx release publish -g foo --git-tag

• create and push git tag based on actual version if release group uses "projectsRelationship": "fixed", if not fixed throw error
• if tag already exist, notify user and continue with publish

Alternate Implementations