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

TEP-0103: Skipping Reason - Implemented #700

Merged
merged 1 commit into from
May 6, 2022

Conversation

jerop
Copy link
Member

@jerop jerop commented May 5, 2022

Marking TEP-0103 as implemented (tektoncd/pipeline#4829), thank you @chitrangpatel!

Also, changing the slack thread link into an image (we may lose the thread because the community slack is in the free tier)

@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 5, 2022
Marking TEP-0103 as implemented, thank you @chitrangpatel!
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lbernick

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 May 5, 2022
@dibyom
Copy link
Member

dibyom commented May 6, 2022

Thanks @chitrangpatel 🎉

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label May 6, 2022
@tekton-robot tekton-robot merged commit 017c410 into tektoncd:main May 6, 2022
@jerop jerop added the kind/tep Categorizes issue or PR as related to a TEP (or needs a TEP). label May 26, 2022
@jerop jerop deleted the tep-0103-implemented branch June 11, 2022 01:57
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. kind/tep Categorizes issue or PR as related to a TEP (or needs a TEP). lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants