-
Notifications
You must be signed in to change notification settings - Fork 8.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Export and Import Workflow Tags #2653
Conversation
Nice! |
I'm not able to replicate the Codacy issues with |
Hello. Thanks for highlighting. Will take a look and prioritise for this week's release. |
3d0c727
to
7c1e65c
Compare
Support exporting and importing tags of workflows via frontend and cli. On export, all tag data is included in the json. - id - name - updatedAt - createdAt When importing a workflow json to n8n we: - first check if a tag with the same id and createdAt date exists in the database, then we can assume the tag is identical. Changes on the name of the tag are now preserved. - check if a tag with the same name exists on the database. - create a new tag with the given name.
7c1e65c
to
c903c52
Compare
update - I have started looking at this but there were a few issues on the FE when importing/exporting tags that needed addressing (started that here https://github.com/n8n-io/n8n/tree/lucaber-import-tags). |
Any updates on this? Anything we can do to expedite the code review on this? |
Closing PR in favor of #3130 which is based on this. |
Got released with |
Support exporting and importing tags of workflows via frontend and cli.
On export, all tag data is included in the json.
When importing a workflow json to n8n we:
database, then we can assume the tag is identical. Changes on the name
of the tag are now preserved.