-
Notifications
You must be signed in to change notification settings - Fork 275
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ci: add zepter and propagate features (#1951)
* ci: add zepter and propagate features * Update .config/zepter.yaml Co-authored-by: DaniPopes <[email protected]> --------- Co-authored-by: DaniPopes <[email protected]>
- Loading branch information
Showing
10 changed files
with
116 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
version: | ||
format: 1 | ||
# Minimum zepter version that is expected to work. This is just for printing a nice error | ||
# message when someone tries to use an older version. | ||
binary: 0.13.2 | ||
|
||
# The examples in the following comments assume crate `A` to have a dependency on crate `B`. | ||
workflows: | ||
check: | ||
- [ | ||
"lint", | ||
# Check that `A` activates the features of `B`. | ||
"propagate-feature", | ||
# These are the features to check: | ||
"--features=std,serde,ssz", | ||
# Do not try to add a new section into `[features]` of `A` only because `B` expose that feature. There are edge-cases where this is still needed, but we can add them manually. | ||
"--left-side-feature-missing=ignore", | ||
# Ignore the case that `A` it outside of the workspace. Otherwise it will report errors in external dependencies that we have no influence on. | ||
"--left-side-outside-workspace=ignore", | ||
# limit to the workspace | ||
"--workspace", | ||
"--show-path", | ||
"--quiet", | ||
] | ||
default: | ||
# Running `zepter` with no subcommand will check & fix. | ||
- [$check.0, "--fix"] | ||
|
||
# Will be displayed when any workflow fails: | ||
help: | ||
text: | | ||
Alloy uses the Zepter CLI to detect abnormalities in Cargo features, e.g. missing propagation. | ||
It looks like one more checks failed; please check the console output. | ||
You can try to automatically address them by installing zepter (`cargo install zepter --locked`) and simply running `zepter` in the workspace root. | ||
links: | ||
- "https://github.com/ggwpez/zepter" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters