A way to manually force a specific target (or branch) to be regarded as up-to-date despite code change?

[koefoeden]

Help

• I understand and agree to https://books.ropensci.org/targets/help.html.

Description

Hi!

Does anyone know of a way to manually force a specific target to be regarded as up-to-date, and thus skipped, on the next tar_make()-prcoess? Kind of like tar_invalidate(), but inversed?

For context, it happens quite often that I need to make changes to targets which shouldn't need to invalidate already computed targets, such as adjusting number of allocated CPU cores. Similarly, I run my pipeline on several nearly-identical datasets using tar_map, which sometimes needs to handle new edge-cases/peculiarities of that specific dataset, which shouldn't affect the other datasets.

I have experiemented with temporary tar_cue("never")-arguments in the specific targets after having changed the code (potentially using tar_invalidate() on the branches that actually needs updating), but it seems that all targets re-run after removing the tar_cue() again.

I realize it could introduce a lot of problems if used recklessly, but I think it would be quite powerful and time-saving to have!

[wlandau]

c.f. ropensci-books/targets#86 (comment)