Skip to content

docs: Add rules to not supported list for persisted variables

Qays H. Poonawala requested to merge (removed):ci-variable-use-docs into master

What does this MR do?

Add rules to not supported list for persisted variables

It is mentioned earlier in the documentation on this page, but not here.

Related issues

None.

Author's checklist

Possible violation of the style guide is that the information is on two different places on the same page, but that was the case before this mr so its up to your discretion if you think it should just be removed.

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  • Ensure a release milestone is set.
Edited by Qays H. Poonawala

Merge request reports

Loading