I am using the source control and environments feature to connect my self-hosted n8n instance to a Git repository.
My initial test of pushing a single workflow was successful and created a commit in Git as expected. However, I then encountered an issue when I attempted to push approximately 200 workflows at once. The push failed with an error in the n8n interface (I unfortunately do not recall the exact error message), and no workflows were committed.
Now, when I open the “Push” dialog, it no longer shows the original 200 workflows that failed to sync. Instead, it only displays newly created or recently modified workflows. As the screenshot shows, I only see 24 workflows listed, even though I have over 200 in my instance.
This behavior seems like a bug. Has anyone else encountered this issue or found a resolution?
Replying to myself from future: I found that this is a bug in n8n.
All the workflows and personal ones are displayed to admin in push modal. But they are pushed, it throws error.
Steps To Reproduce
Create a couple of private credentials from a account 1, or personal workflow and couple of team workflows
From account 2 (instance admin), click push button to open push modal. As an instance admin, you will see all private workflows and credentials along with team workflows and credentials.
Select team workflow/credential and select at least one private workflow/credential.
Add a commit message and click push button
Boom. You will see and error Failed to export credentials…
Open the push modal again, you wont see that team workflow anymore
But Open your git repository, the changes was not pushed.
Just left a comment there asking for a status update since it seems to have gone quiet after a team restructure. If you want to +1 the issue directly that would help push it up the priority list.
In the meantime the safest workaround is to only push team workflows, never mix personal and private ones in the same commit.
