Pull Request Review Time for Forked common.mjs?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

I created a pull request after forking the common.mjs. How long before it is reviewed and updated to my account?

2

Can you link me to your PR?

3

QuicksilverSlick-patch-1

4

I don’t see your PR in the Pipedream repo

5

I’m trying to push it to my PD account so I can use the new file

6

I have been unsuccessful installing CLI

7

Where are you getting hung up?

8

I’m slow today. I forked it: Update common.mjs by QuicksilverSlick · Pull Request #1 · QuicksilverSlick/pipedream · GitHub

9

I need to push the new common.mjs to my PD account for use.

10

I think maybe the target repo for your PR needs to be updated to PipedreamHQ/pipedream? That PR is trying to merge into your forked repo.

11

Is that necessary to publish to my PD account?

12

No, that’s just if you want to publish that change to the public version of the component (on the Pipedream registry)

13

Where are you getting hung up with getting the CLI installed?

14

OK. Then all I need to do is publish to my PD account. What are the remaining steps since I updated the common.mjs file in the ChatGPT folder for my repo?

15

What are the remaining steps for what?

16

As I understand it, I need to install CLI, then publish the new file to my PD account so that I can use the updated version of the file. Is that correct?

17

That’s right

18

Do I publish the new file from my repo or do I need to do a pull request to the master PD?

19

You can publish locally from your repo, that’s fine. No PR needed — that would just be if you wanted to publish this change to the official component in the Pipedream registry.

20

Is there a specific part of the publishing process w/ the CLI that isn’t working? Happy to help troubleshoot.