Closed Gekko0114 closed 4 months ago
github action testdata might have a issue
@Gekko0114 Can you investigate if it does have or not when get a chance?
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten /assign
What happened: There might be several issues. 1
testdata
action might not fail because there is no command checking if the PR includes all wasm files, likegit diff --exit-code
. 2 However, introducing a command likegit diff --exit-code
might lead to a new problem. wasm files seem to depend on developer's environment. For example, I am using mac environment. Even though I don't change any codes, wasm file I build is different from the file attached in the github repo. If we implement a command likegit diff --exit-code
, we might need to standardize the development environment.Please let me know if I misunderstand something.
(Previously I talked this issue with @kazukousen)
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment: github_actions