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

Add option keep-current to clearsource_history command #484

Conversation

seitenbau-govdata
Copy link
Member

Based on #397 we added the option to keep the latest related objects to a harvest source when running clearsource_history.

@metaodi
Copy link
Member

metaodi commented Dec 21, 2021

I think this option should be called "keep-current" instead of "keep-actual", since you want to keep the current active object. WDYT?

@seitenbau-govdata
Copy link
Member Author

@metaodi Yes, I think same. Our intention was changing as less as possible from the pull request this one is based on. But you have convinced me to make the changes. If nobody else wants to keep the current naming of the variable we will rename it to keep-current.

@seitenbau-govdata seitenbau-govdata changed the title Add option keep-actual to clearsource_history command Add option keep-current to clearsource_history command Dec 23, 2021
@amercader amercader merged commit b702bf9 into ckan:master Jan 24, 2022
@seitenbau-govdata seitenbau-govdata deleted the fix-clearsourcehistory-command-keep-latest-objects branch January 24, 2022 19:57
LittleRed945 pushed a commit to LittleRed945/ckanext-harvest that referenced this pull request Sep 22, 2022
…ry-command-keep-latest-objects

Add option keep-current to clearsource_history command
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants