Skip to content

Conversation

@IWDTestBot
Copy link

No description provided.

This lets the configuration disable the Signed-off-by check.
If the configuration disabled a check there is no reason to notify
the author that the check was skipped.
No sense in sending a check that was disabled by the config
This makes it clear on the Patchwork UI what checks are going to run
rather than each check updating to PASS/FAIL once it finishes.
If a test is disabled skip posting a comment to Github.
@Vudentz
Copy link
Collaborator

Vudentz commented Mar 18, 2024

@jprestwo Are these changes still relevant? @tedd-an it doesn't seem I have rights to push these changes myself, btw.

@jprestwo
Copy link

Its been quite a while, but it appears that the IWD CI's clone of this repo only has these 7 commits on top. So I would say yes, its still relevant. I would need to rebase/test as its been 2+ years 😄

@Vudentz
Copy link
Collaborator

Vudentz commented Mar 18, 2024

Its been quite a while, but it appears that the IWD CI's clone of this repo only has these 7 commits on top. So I would say yes, its still relevant. I would need to rebase/test as its been 2+ years 😄

Yeah, sorry about the delay, this being in the BlueZTestBot doesn't trigger my email filter for some odd reason, anyway I hope we can move the CI to BlueZ organization in the future so we have the issue tracking in one place.

Btw, in case of iwd where are the CI scripts/files store, in the main tree?

@jprestwo
Copy link

Everything is structured similar to bluez. The main repo is just a fork of git.kernel.org with the .github/workspace/ scripts on top. And there are various other repos we use for the CI.

https://github.com/IWDTestBot/iwd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants