microsoft / microsoft/beachball
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
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 815
- Forks
- 93
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 12
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the existing .tgz emission path and the current repository-publishing flow. Compare the desired output with git format-patch; done means a pipeline can consume the generated patch, or an agreed branch output, and create a policy-compliant PR, with tests covering the chosen output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100