-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Fixes #18907, pass in correct cwd value for hooks exe #18921
Fixes #18907, pass in correct cwd value for hooks exe #18921
Conversation
0e32cc7
to
3e95216
Compare
Signed-off-by: Fang-Pen Lin <[email protected]>
3e95216
to
dd81f7a
Compare
Updated PR with the new methods in common. Still waiting for a new common release. Do I need to add vendor changes in this PR by the way? |
No you do not have to wait for the vendoring. LGTM |
@containers/podman-maintainers PTAL |
@vrothberg @Luap99 PTAL |
@giuseppe PTAL |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fangpenlin, rhatdan, vrothberg 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 |
Fixes #18907
This PR depends on containers/common#1514 to be merged. Sorry first time contributor, I am not sure what's the correct workflow to make changes in upstream
common
repo. I assume I should create a new PR in common repo first, then wait for a new release fromcommon
then update the vendor file in this repo to make it depends on the changes I made in common?Does this PR introduce a user-facing change?