Skip to content
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

[Feature Request] Add the capability of sync a subset of stories filtering by name or slug #51

Open
Segmentree opened this issue Jun 1, 2023 · 2 comments
Assignees
Labels
feature [Issue] New feature or request p4-important [Priority] Violate documented behavior or significantly improve performance (priority)

Comments

@Segmentree
Copy link

Description

Sometimes is useful to copy only stories with specific names or slugs. To achieve this, one approach could be to provide a list of names or slugs separate by commas in the command to sync stories:

sync --type stories --source 233308 --target 233311 --names-list name1,name2,name3
sync --type stories --source 233308 --target 233311 --slug-list slug1,slug2,slug3

@SebbeJohansson
Copy link
Contributor

+1 on this. I would love to be able to sync a specific slug/story.

@edvinasjurele
Copy link

+1

We have thousands of stories and full sync is not a way to go, we rather have to perform scoped sync or at least by slug list (exact match).

NOTE: starts-with does not cover the need because it could be some folder (f.e. starts-with=blog/) containing a lot of stories in it, although it makes a problem slightly smaller but still does not fully cover the need.

Btw, the filter_query also does not help because it is meant for filtering by story content internals and not the outer metadata.

@alvarosabu alvarosabu added feature [Issue] New feature or request and removed enhancement labels Aug 21, 2024
@alvarosabu alvarosabu added the p4-important [Priority] Violate documented behavior or significantly improve performance (priority) label Nov 4, 2024
@alvarosabu alvarosabu self-assigned this Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature [Issue] New feature or request p4-important [Priority] Violate documented behavior or significantly improve performance (priority)
Projects
None yet
Development

No branches or pull requests

5 participants