chore(repo): Add backport script#1959
Conversation
|
|
|
||
| We're still considering whether switching the repo into a `canary` mode for big, experimental features makes sense. There is no use case for this right now, however, we might experiment with the [changesets prerelease mode](https://github.com/changesets/changesets/blob/main/docs/prereleases.md) in the future. | ||
|
|
||
| ## Backporting PRs |
There was a problem hiding this comment.
Lemme know if you'd want any more details on this for that section
| owner, | ||
| repo, | ||
| issue_number: pr.data.number, | ||
| labels: [`cherry`], |
There was a problem hiding this comment.
Short-form of "cherry-picking"
nikosdouvlis
left a comment
There was a problem hiding this comment.
@LekoArts Good job automating this one :) Do you think we could turn this into a GH workflow using the workflow_dispatch trigger so it can be manually triggered while also accepting inputs?
Or maybe even going a bit further, another similar idea would be to create a special tag (eg backport) and have your script run after merge for every tagged PR
|
The script in its current form wouldn't be ready for that as it doesn't handle any error cases / things besides the happy path. Once you have merge conflicts the script won't finish successfully so it's better to run this locally so that you can also resolve it locally directly. |
Description
This adds a
backportscript insidescripts. You'll be able to do:cd scripts node backport.mjs main-v4 1234Example backport PR: #1958
If you have access to it, use the
CLERK_COOKIE_PATso that the bot user creates the PR.Checklist
npm testruns as expected.npm run buildruns as expected.Type of change
Packages affected
@clerk/clerk-js@clerk/clerk-react@clerk/nextjs@clerk/remix@clerk/types@clerk/themes@clerk/localizations@clerk/clerk-expo@clerk/backend@clerk/clerk-sdk-node@clerk/shared@clerk/fastify@clerk/chrome-extensiongatsby-plugin-clerkbuild/tooling/chore