Unfence timer_policy example (follow-up to #3682)#3730
Merged
nickanderson merged 1 commit intoJul 8, 2026
Conversation
cfengine CLI 0.18.0 ships a syntax-description.json that includes timer_policy on classes: promises, so the example no longer needs the {skip TODO} fence to pass cfengine dev lint-docs. Dropping it means the example is syntax-checked like the others. Follow-up to cfengine#3682 (merged with the fence).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #3682: removes the
{skip TODO}fence from thetimer_policyexample incontent/reference/promise-types/classes.markdown.Why
#3682 fenced the example
```cf3 {skip TODO}because the cfengine CLI's bundledsyntax-description.jsondid not yet knowtimer_policyonclasses:promises, socfengine dev lint-docsrejected it. As of cfengine CLI 0.18.0 that syntax snapshot includes the attribute, so the fence is no longer needed. Dropping it means the example is syntax-checked and reformatted like every other block.Verified locally with cfengine CLI 0.18.0:
cfengine format --check,cfengine dev format-docs(idempotent, cleangit diff), andcfengine dev lint-docs(block now reportsPASS) all succeed.The 3.24 (#3728) and 3.27 (#3729) backports already carry this change.