Skip to content

Feature Request: Just like publishing npm packages to a folder, it would be nice if we could publish to a branch or git patch file #1108

@dannyvv

Description

@dannyvv

At the moment I unfortunately don't have bandwidth to contribute, but thought I'd log it here anyways.

As we improve our security posture we'll get more and more repo's that won't allow bypass of pr policies by bots. This will affect beachball which relies on this.
Just like we recently added a way for beachball to emit the npm packages as .tgz files it would be nice if beachball could take the files it would push to the repo as a .patch file per: https://git-scm.com/docs/git-format-patch.

That way a pipeline can decide to apply the patch and create a PR to follow the repo's compliant policies.
Alternative it could be a branchname as well. But I think the .patch file is more approcheable.

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