Add sync config for Tekton Pruner documentation

[infernus01]

Changes

This PR adds sync/config/pruner.yaml to sync documentation from tektoncd/pruner to the website.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide
for more details.

[infernus01]

/hold

[infernus01]

/unhold

[vdemeester]

Can you squash your commits ? Also, do we need the image in this PR ?

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [vdemeester]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[AlanGreene]

do we need the image in this PR ?

Generally images should be loaded from the project repo, i.e. tektoncd/pruner, rather than adding them directly in the website repo.
If you take a look at the config for some of the other projects you'll see they copy images from the source repo alongside the markdown files.

[infernus01]

@vdemeester @AlanGreene I tried that approach, it seems Hugo doesn't serve files from content/ at URL paths.
We could do one thing, we need to do changes in Pruner repo, if we could reference the image from the root directory of Pruner itself (such as Chains did here.

[AlanGreene]

Suggested change

	include: ['*.md']
	include: ['*.md', '*.png']

If you include images here they'll be copied correctly, including from any sub-directories.

It's then a matter of updating the doc in the pruner repo to reference it correctly.

One option that may help simplify this is to move your README.md from the root of the repo into the docs folder. GitHub will still display it on the repo landing page, so there will be no impact on users viewing the repo directly. This is the approach taken by both Dashboard and Results.