-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
doc: Mark TriggerMesh as Defunct #6154
doc: Mark TriggerMesh as Defunct #6154
Conversation
Welcome @zacheryph! It looks like this is your first PR to knative/docs 🎉 |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: zacheryph The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for knative ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
Thanks @zacheryph, I would remove them. In the meantime, we're working on replacements and we would love feedback on which one you would be using here: knative/eventing#8185 |
7335a7c
to
4a04d9e
Compare
@pierDipi apologize, I missed notification for this one. Updated to remove Triggermesh. I will have to take a look at that issue. |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
So much for that... |
Proposed Changes
Sadly Triggermesh shuttered a year ago, last fall. It is sad to see them gone, though these probably should not be marked as active anymore.
I wonder if these should simply be removed or possibly add a 3rd section for..
Historic
?Defunct
? not sure what to name it 🤔