-
Notifications
You must be signed in to change notification settings - Fork 1
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
Enable Ci Debugger in bazel action #17
Conversation
a6826b4
to
ebc8e34
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See one note. Also we can close this out https://linear.app/trunk/issue/TRUNK-10103/add-ci-debugger-support-to-bazel-action
action.yaml
Outdated
uses: trunk-io/breakpoint@v1 | ||
with: | ||
breakpoint-id: ${{ inputs.trunk-ci-debugger-breakpoint-name }} | ||
trunk-token: ${{ env.TRUNK_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we usually specify to use this from secrets.
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but an action can't access secrets from the og repo, maybe I'll just add it as in input
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually completely missed that the action already takes a token as an input, modified
No description provided.