-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
PullRequestResource resource usage #1275
Comments
It seems like users may not able able to understnad how to use the `PullRequestResource` with secrete configuration This patch adds an example TaskRun/Task to demonstrate how to use the PR Resoucre. Fixes tektoncd#1275
It seems like users may not able able to understand how to use the `PullRequestResource` with secrete configuration This patch adds an example TaskRun/Task to demonstrate how to use the PR Resource. Fixes tektoncd#1275
@hrishin |
It seems like users may not able able to understand how to use the `PullRequestResource` with secrete configuration This patch adds an example TaskRun/Task to demonstrate how to use the PR Resource. Fixes tektoncd#1275
@vincent-pli that sounds nice idea. Just wondering where shall we add the example? @sbwsg ^ |
A better way we can address it in the followup PR? @vincent-pli @sbwsg |
If a working example is required I'd personally tackle it in a separate PR from #1276. Seems like it's going to need more thought on how exactly to make that work with the YAML tests. |
It seems like users may not able able to understand how to use the `PullRequestResource` with secret configuration. This patch updates the docs with example Task with Secret to demonstrate how to use the PR Resource. Fixes tektoncd#1275
@sbwsg 👍 |
It seems like users may not able able to understand how to use the `PullRequestResource` with secret configuration. This patch updates the docs with example Task with Secret to demonstrate how to use the PR Resource. Fixes #1275
Looks like users are not able to understand how to use the
PullRequestResource
with secrete configuration.Maybe it's a bit confusing with respect to documentation.
The text was updated successfully, but these errors were encountered: