Skip to content

Ignore private workspaces for versioning and changelogs #2485

@jackw

Description

@jackw

Is your feature request related to a problem? Please describe.

TLDR; Due to devs forgetting to apply labels we have private package changes appearing in changelogs which we don't want.

We use auto for publishing our npm monorepo of Grafana developer tools. Within this repo is a private workspace for our documentation website. As it's private it never makes its way to NPM but occasionally (due to contributors not remembering to include the label we've configured for omit-commits) our changelogs include entries pointing to versions of the website.

Describe the solution you'd like

Not really sure how best to handle it but maybe we can provide an option to omit-commits (such as workspace name or package.json has "private": true) which would guarantee changes to a workspace never make their way into version calculations or the changelog?

Describe alternatives you've considered

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions