Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pipeline-to-taskrun] Get ready to run presubmit tests 🏁 #790

Conversation

bobcatfish
Copy link
Contributor

Changes

In #770 I tried to add the custom task and OWNERS file - with @jerop's
help I realized it would be easier to add the OWNERS file first so that
OWNERS can review the custom task itself - but even after that I was
still changing a file in the top level test dir to add the custom task
to the list of tests kicked off which needs top level OWNERS approval -
so this commit is doing that separately. Looking at the script it should
be safe to add a directory that doesn't exist because it should just get
ignored

Submitter Checklist

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

  • [n/a] Includes docs (if user facing)
  • Commit messages follow commit message best practices
  • Commit messages includes a project tag in the subject - e.g. [OCI], [hub], [results], [task-loops]

See the contribution guide
for more details.

In tektoncd#770 I tried to add the custom task and OWNERS file - with @jerop's
help I realized it would be easier to add the OWNERS file first so that
OWNERS can review the custom task itself - but even after that I was
still changing a file in the top level test dir to add the custom task
to the list of tests kicked off which needs top level OWNERS approval -
so this commit is doing that separately. Looking at the script it should
be safe to add a directory that doesn't exist because it should just get
ignored
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Sep 1, 2021
@dlorenc
Copy link
Contributor

dlorenc commented Sep 1, 2021

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2021
@tekton-robot
Copy link

[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

Needs approval from an approver in each of these files:

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 2, 2021
@tekton-robot tekton-robot merged commit bed8bb7 into tektoncd:main Sep 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants