Add github-add-comment version 0.3

[vinamra28]

Changes

As of now github-add-comment task supports input of comments only via
params.

This PR adds support of workspaces if in case somebody wants to provide
the comments via some file. One such use case can be:-
In Catlin CI, logs are produced after executing catlin command on
changed files which can contain multiple warnings and these warnings can
be ingored by the user if not posted on the github PR as the CI is
green. So all the logs would be stored in a file with proper formatting
and then the shared workspace can be passed to the github-add-comment
task along with the filename containing the formatted logs.

Signed-off-by: vinamra28 vinjain@redhat.com

Submitter Checklist

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

• Includes docs (if user facing)
• Includes tests (if functionality of task changed or new task added)
• Commit messages follow commit message best practices
• Complies with Catalog Organization TEP, see example. Note An issue has been filed to automate this validation

  • File path follows <kind>/<name>/<version>/name.yaml

  • Has README.md at <kind>/<name>/<version>/README.md

  • Has mandatory metadata.labels - app.kubernetes.io/version the same as the <version> of the resource

  • Has mandatory metadata.annotations tekton.dev/pipelines.minVersion

  • mandatory spec.description follows the convention

      ```
    
      spec:
        description: >-
          one line summary of the resource
    
          Paragraph(s) to describe the resource.
      ```
    

See the contribution guide
for more details.

---

[vinamra28]

/cc @chmouel
/test .*

[chmouel]

Don't we want optional workspace instead of optional params?

[vinamra28]

Don't we want optional workspace instead of optional params?

I am very bad at python 😞 so don't know how to check whether workspace is bound or not 😅. So I did a workaround by adding one more step that will check whether file is passed or it's a comment. In any of the case it will be moved to a file comment_private.txt and in python script I am going to read that file and post the file contents as a comment.

[ghost]

how to check whether workspace is bound or not

In your script I think it would look like:

if "$(workspaces.foo.bound)" == "true":

[vinamra28]

how to check whether workspace is bound or not

In your script I think it would look like:

if "$(workspaces.foo.bound)" == "true":

ohh... I thought it would be handled other way. Thanks @sbwsg 👍

[chmouel]

/lgtm

thanks

[PuneetPunamiya]

/lgtm

[chmouel]

/lgtm
/approve

🥳

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chmouel

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [chmouel]

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