import { ConfigurationError } from "@pipedream/platform";
import github from "../../github.app.mjs";
export default {
key: "github-create-pull-request",
name: "Create Pull Request",
description: "Creates a new pull request for a specified repository. [See the documentation](https://docs.github.com/en/rest/pulls/pulls#create-a-pull-request)",
version: "0.1.1",
type: "action",
props: {
github,
repoFullname: {
propDefinition: [
github,
"repoFullname",
],
label: "Base Repository",
description: "The base repository, where the pull request will be created.",
},
base: {
propDefinition: [
github,
"branch",
(c) => ({
repoFullname: c.repoFullname,
}),
],
label: "Base Branch",
description: "The base branch, where the changes will be received.",
},
headRepo: {
propDefinition: [
github,
"repoFullname",
],
label: "Head Repository",
description: "The head repository, where the changes originate from. This can, but does not have to, be the same repository.",
},
head: {
propDefinition: [
github,
"branch",
(c) => ({
repoFullname: c.headRepo,
}),
],
label: "Head Branch",
description: "The head branch, where the changes originate from",
},
body: {
label: "Body",
description: "The text description of the pull request.",
type: "string",
optional: true,
},
maintainerCanModify: {
label: "Maintainers Can Modify",
description: "Indicates whether [maintainers can modify](https://docs.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/) the pull request.",
type: "boolean",
optional: true,
},
draft: {
label: "Is Draft",
description: "Indicates whether the pull request is a draft. See \"[Draft Pull Requests](https://docs.github.com/articles/about-pull-requests#draft-pull-requests)\" in the GitHub Help documentation to learn more.",
type: "boolean",
optional: true,
},
title: {
label: "Title",
description: "The title of the pull request.",
type: "string",
optional: true,
},
issue: {
propDefinition: [
github,
"issueNumber",
(c) => ({
repoFullname: c.repoFullname,
}),
],
label: "Issue",
description: "An issue in the repository to convert to a pull request. The issue title, body, and comments will become the title, body, and comments on the new pull request.",
min: 1,
optional: true,
},
},
async run({ $ }) {
if (!this.issue && !this.title) {
throw new ConfigurationError("Title is required if Issue is unspecified. You can either specify a new pull request with Title or convert an existing issue to a pull request with Issue.");
}
if (this.issue && this.title) {
throw new ConfigurationError("You can't specify both Title and Issue at the same time.");
}
const data = {
title: this.title,
head: this.head.split("/")[1],
base: this.base.split("/")[1],
head_repo: this.headRepo,
body: this.body,
maintainer_can_modify: this.maintainerCanModify,
draft: this.draft,
issue: this.issue,
};
const response = await this.github.createPullRequest({
owner: this.owner,
repoFullname: this.repoFullname,
data: data,
});
$.export("$summary", `Successfully created pull request: ${response.title}.`);
return response;
},
};
Chase Roberts@chsrbrts@benedictevans If you haven’t used @pipedream yet, then you haven’t lived.
✨Ellie Day✨@heyelliedayEvaluation update: @pipedream has quite literally been a dream to work with! I’m excited to leverage this tool for all the various workflows I need to write. I’m currently at 11k invocations a day from the initial workflows I’ve written in the past couple weeks.
Michael Braedley@MBraedleyUpdate: I got it working properly, and it's working so well that I'm dropping IFTTT. @pipedream can do everything that IFTTT basic can, and most (if not all things) IFTTT pro can for free or at a reasonable price if you need it. I am recommending it for basically any power user.
Thomas Cutting@mrthomascuttingWant quick+dirty integrations for a serverless workflow - @pipedream is my new go-to 😃
Matthew Roberts@mattdotrobertsday 013 - finally hit node js. This is the secret sauce of taking #nocode projects that one step further. Pumped about getting deeper into @pipedream now
Kenneth Auchenberg 💭@auchenbergYahoo Pipes is back! Kinda 😍 @pipedream
Raymond Camden 🥑@raymondcamdenAwesome video by the @pipedream folks showing real time twitter sentiment analysis integrated with Google Sheets. This is where Pipedream *really* shines, connecting systems together in easy workflows.
Nacho Caballero@nachocaballeroI couldn't recommend @pipedream more. It's an amazing service to integrate different APIs. Much more powerful than Zapier and more user-friendly than AWS Lambda. I'm very proud to wear this t-shirt #NoCode
Jason Snow@jyksnwDeveloped a working prototype environmental sensor IoT solution with @particle Photon, @pipedream, and @MongoDB with full graphing and alerting in less than a day! All amazing technology, will def. be exploring these more.
Steven Terrana@steven_terrana@burgwyn you've inspired me to finally set up my own blog. I'll make sure my first blog post explains the tech behind the setup. think @obsdmd + @GatsbyJS + @pipedream.
🚄 James Augeri, PhD@DotDotJamesWant to low-code your back end, need more horsepower than @Bubble / @KnackHQ, or just miss Yahoo! Pipes? Check out @PipeDream
Sébastien Chopin@AtinuxGitHub issues should be like @linear_app for maintainers. Looking forward more integrations with GH actions or tools like @pipedream 👀
Raul@raul_predescuIf you're a dev and not using @pipedream, you're missing out. Been using it for months, daily. FREE for devs. Plenty of integrations and good limits. Absolutely love it.
Bruno Skvorc@bitfallsSo @pipedream is pretty amazing. In 3 minutes I just made a flow which adds @rickastley's Never Gonna Give You Up to my @spotify playlist whenever a new pull request arrives in an old repo of mine.
Zach Lanich@ZachLanichUm, wow 🤯 @pipedream
Steven Bell@bellontechI just used @pipedream to build a Shopify App. Wow, they make small backed tasks easy.
Jay Hack 🎩🇺🇸@_jayhack_Very impressed with this bad boi - it reminds me of a @PalantirTech internal tool, but geared towards integrations instead of data analysis and far more customizable. Great expectations here 🚀🤩
Tree Sturgeon 🔥🚴♂️🌳@philsturgeonFor context this is day 2 of a really challenging and stupid migration from Notion to @airtable with disparate/missing data. It's going better than expected and thanks to @pipedream I don't have to bother the iOS dev to add W3W.