Skip to content

Fix missing '>' in shell command

This is my first MR to a bigger project, so please feel free to give advice if anything is filled sparely or wrong, or requires improvement.

What does this MR do?

This MR fixes a small typo in the documentation of creating a patch.

Related issues

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

  • MR title and description are up to date, accurate, and descriptive.
  • MR targeting the appropriate branch.
  • Latest Merge Result pipeline is green.
    • did not check this, however, the change in the documentation should not affect the build pipeline.
  • When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

  • The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
  • If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
  • If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
  • If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

  • Test plan indicating conditions for success has been posted and passes.
    • only documentation affected
  • Documentation created/updated.
  • Tests added.
    • only documentation affected
  • Integration tests added to GitLab QA.
    • only documentation affected
  • Equivalent MR/issue for the GitLab Chart opened.
    • did not find the equivalent file
  • Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.
    • only documentation affected

Merge request reports