Syncing Fork - Best Practice

Questions
,
1

Describe the problem/error/question

What is the best practice when having a forked version and synching it with main branch?

What is the error message (if any)?

the problem I have is that I change source code on my side to fit my needs, however when it comes time to sync there are always thousands of file to merge. Is there an easier way to manage the source code, not missing on new or updated files but still having my own changes not be affected?

Please share your workflow

N/A

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version: latest
  • Database (default: SQLite): Postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): main with workers
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: ubuntu
2

@gordonlotter , why are you asking n8n community this question? You should be checking GitHub documentation. No part of your question relates to n8n. Here’s GitHub community and here’s Git Book you can read online or download as PDF version.

1 Like
3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.