This topic was automatically generated from Slack. You can find the original thread here.
can I move one workflow from a regular project to a project integrated with GitHub?
Yes, you can move a workflow from a regular project to a project integrated with GitHub, but there is an important limitation: - You cannot move workflows out of GitHub Synchronized Projects. However, you can move workflows into a GitHub Synchronized Project from a regular project. ### How to move a workflow to a GitHub-integrated project 1. Go to the workflows listing page. 2. Select the workflow(s) you want to move by checking them. 3. Click Move in the top action menu. 4. Select the GitHub-integrated project from the dropdown. 5. Click Move again to complete the process. > Note: If any moved workflows have undeployed changes, those changes will be staged in a branch prefixed with undeployed-changes (e.g., undeployed-changes-27361). #### Reference - You can find more details in the Pipedream Projects documentation. If you have any issues or see limitations, please visit Pipedream for more support options.
I followed your steps, but I got an error “git projects not supported” in the UI.
I’m sorry you’re running into this issue. The error message “git projects not supported” means that moving workflows into or out of GitHub-integrated (synchronized) projects is currently not supported in the Pipedream UI. Key points: - You cannot move workflows into or out of GitHub Synchronized Projects using the UI at this time. - This is a known limitation of Pipedream’s GitHub integration. What you can do: - If you need to migrate a workflow to a GitHub-integrated project, you’ll need to manually recreate the workflow in the new project. - Copy the code and configuration from your existing workflow, and set it up in the GitHub project. If this limitation is blocking your work or you need further help, please visit Pipedream for more support options.
that’s weird. First you said that I can. Then you said I cannot. Which one is correct?
I’m sorry for the confusion in my previous responses. To clarify: You cannot move workflows into or out of GitHub-integrated (synchronized) projects in Pipedream. This is a current limitation of the platform. If you try to move a workflow, you’ll see an error like “git projects not supported.” If you need to migrate a workflow, you’ll have to manually recreate it in the GitHub-integrated project. If this limitation is blocking your work, or if you need more help, please visit Pipedream for more support options.
If I manually recreate a workflow its trigger URL will change and it will create a lot of problems.
You’re absolutely right—if you manually recreate a workflow in Pipedream, the trigger URL (such as for HTTP/Webhook triggers) will change. This can cause significant issues if you have external systems or services pointing to the old URL, as they would need to be updated everywhere to use the new trigger URL. Unfortunately, due to current platform limitations, moving workflows between regular and GitHub-integrated projects is not supported, and there is no automated way to preserve the original trigger URL when recreating the workflow in a new project. ### What can you do? - If you must move the workflow, you will need to update all external systems to use the new trigger URL. - If this is a blocker for your use case, or if you need to discuss possible workarounds or feature requests, please visit Pipedream for more support options. I’m sorry for the inconvenience—this is a known pain point for users. If you need help with a specific migration scenario, please let me know, or reach out to Pipedream Support directly.