Stream: git-wasmtime

Topic: wasmtime / issue #3166 Skip CI if only parts of the repo ...


view this post on Zulip Wasmtime GitHub notifications bot (Aug 09 2021 at 09:26):

tschneidereit opened issue #3166:

We currently run CI unconditionally on all changes, but there are parts of the repository that aren't tested, and never will be. It's possible that for now the only part this applies to is the newly-introduced meetings directory, though there may be others for all I know.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 09 2021 at 09:26):

tschneidereit labeled issue #3166:

We currently run CI unconditionally on all changes, but there are parts of the repository that aren't tested, and never will be. It's possible that for now the only part this applies to is the newly-introduced meetings directory, though there may be others for all I know.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 09 2021 at 09:26):

tschneidereit labeled issue #3166:

We currently run CI unconditionally on all changes, but there are parts of the repository that aren't tested, and never will be. It's possible that for now the only part this applies to is the newly-introduced meetings directory, though there may be others for all I know.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 19 2021 at 15:12):

alexcrichton commented on issue #3166:

I ended up inadvertently doing this in https://github.com/bytecodealliance/wasmtime/commit/9e8e0e8352a840df5d75d1385cb3144f9a3b13e7, so I think this is covered now.

view this post on Zulip Wasmtime GitHub notifications bot (Aug 19 2021 at 15:12):

alexcrichton closed issue #3166:

We currently run CI unconditionally on all changes, but there are parts of the repository that aren't tested, and never will be. It's possible that for now the only part this applies to is the newly-introduced meetings directory, though there may be others for all I know.


Last updated: Dec 23 2024 at 12:05 UTC