This issues tracks the initial work to be done to onboard manual-approval custom task on konflux.

• Repository: openshift-pipelines/… (to be decided if we use pipelines-as-code directly)
• konflux resources present (application, components, test, …)
• tekton resources present (push/pull-request pipelinerun and pipelines)
• GitHub workflows present (update upstream, …)

Requirements

• Builds are green
• Ideally, tests are green (entreprise-contract) one

Steps

1. 

• Create a PR to hack
  • https://github.com/openshift-pipelines/hack/pull/23

2.

• git clone https://github.com/openshift-pipelines/pipelines-as-code
• mkdir -p patches openshift/dockerfiles .tekton .github/workflows .konflux
• create readme in openshift

  cat > openshift/README.md <<EOF
    # \`openshift\` specific files
  EOF

• create readme in konflux

  cat > .konflux/README.md <<EOF
    # \`konflux-ci\` manifests  This folder contains [\`konflux-ci\`](konfluxci) configuration that is synced with the konflux-ci cluster.
     
    [konfluxci]: https://konflux-ci.dev/
  EOF 

• touch openshift/dockerfiles/.placeholder patches/.placeholder .tekton/.placeholder .github/workflows/.placeholder
• git add -A
• git commit -s -m "Bootstrap the repository structure"
• git remote add savita https://github.com/savitaashture/pipelines-as-code
• git checkout -b pac-konflux-changes
• git push savita pac-konflux-changes
• add GitHubApp `Red Hat Konflux` 
• add openshift-pipelines-bot under collaborators and teams with write permission
  • go to settings -> collaborators and teams
• sample PR: https://github.com/openshift-pipelines/pipelines-as-code/pull/1795

3.

• Write a dockerfile and send a PR to pac
  • sample PR : https://github.com/openshift-pipelines/pipelines-as-code/pull/1795