diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index d8d3096..134aeab 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -2,17 +2,15 @@ ## Our Pledge -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our project and -our community a harassment-free experience for everyone, regardless of age, -body size, disability, ethnicity, gender identity and expression, level of -experience, education, socio-economic status, nationality, personal -appearance, race, religion, or sexual identity and orientation. +In the interest of fostering an open and welcoming environment, we as contributors and maintainers +pledge to making participation in our project and our community a harassment-free experience for +everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level +of experience, education, socio-economic status, nationality, personal appearance, race, religion, +or sexual identity and orientation. ## Our Standards -Examples of behavior that contributes to creating a positive environment -include: +Examples of behavior that contributes to creating a positive environment include: - Using welcoming and inclusive language - Being respectful of differing viewpoints and experiences @@ -22,53 +20,46 @@ include: Examples of unacceptable behavior by participants include: -- The use of sexualized language or imagery and unwelcome sexual attention or - advances +- The use of sexualized language or imagery and unwelcome sexual attention or advances - Trolling, insulting/derogatory comments, and personal or political attacks - Public or private harassment -- Publishing others' private information, such as a physical or electronic - address, without explicit permission -- Other conduct which could reasonably be considered inappropriate in a - professional setting +- Publishing others' private information, such as a physical or electronic address, without explicit + permission +- Other conduct which could reasonably be considered inappropriate in a professional setting ## Our Responsibilities -Project maintainers are responsible for clarifying the standards of acceptable -behavior and are expected to take appropriate and fair corrective action in -response to any instances of unacceptable behavior. +Project maintainers are responsible for clarifying the standards of acceptable behavior and are +expected to take appropriate and fair corrective action in response to any instances of unacceptable +behavior. -Project maintainers have the right and responsibility to remove, edit, or -reject comments, commits, code, wiki edits, issues, and other contributions -that are not aligned to this Code of Conduct, or to ban temporarily or -permanently any contributor for other behaviors that they deem inappropriate, +Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, +code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or +to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful. ## Scope -This Code of Conduct applies both within project spaces and in public spaces -when an individual is representing the project or its community. Examples of -representing a project or community include using an official project e-mail -address, posting via an official social media account, or acting as an -appointed representative at an online or offline event. Representation of a -project may be further defined and clarified by project maintainers. +This Code of Conduct applies both within project spaces and in public spaces when an individual is +representing the project or its community. Examples of representing a project or community include +using an official project e-mail address, posting via an official social media account, or acting as +an appointed representative at an online or offline event. Representation of a project may be +further defined and clarified by project maintainers. ## Enforcement -Instances of abusive, harassing, or otherwise unacceptable behavior may be -reported by contacting the project team at autarch@urth.org. All complaints -will be reviewed and investigated and will result in a response that is deemed -necessary and appropriate to the circumstances. The project team is obligated -to maintain confidentiality with regard to the reporter of an incident. -Further details of specific enforcement policies may be posted separately. +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting +the project team at autarch@urth.org. All complaints will be reviewed and investigated and will +result in a response that is deemed necessary and appropriate to the circumstances. The project team +is obligated to maintain confidentiality with regard to the reporter of an incident. Further details +of specific enforcement policies may be posted separately. -Project maintainers who do not follow or enforce the Code of Conduct in good -faith may face temporary or permanent repercussions as determined by other -members of the project's leadership. +Project maintainers who do not follow or enforce the Code of Conduct in good faith may face +temporary or permanent repercussions as determined by other members of the project's leadership. ## Attribution -This Code of Conduct is adapted from the [Contributor Covenant][homepage], -version 1.4, available at +This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html [homepage]: https://www.contributor-covenant.org diff --git a/Changes.md b/Changes.md index 94587ae..b0c30f4 100644 --- a/Changes.md +++ b/Changes.md @@ -1,42 +1,37 @@ ## 0.0.8 -- For builds that need the `cross` binary, this binary is now cached. A cache - hit saves about 20 seconds in my tests. Suggested by @timon-schelling. GH - #4. +- For builds that need the `cross` binary, this binary is now cached. A cache hit saves about 20 + seconds in my tests. Suggested by @timon-schelling. GH #4. ## 0.0.7 - 2023-04-21 -- The toolchain argument was (probably) not being respected with cross builds, - though it's hard to be sure since none of the output from past CI runs I've - looked at it includes the toolchain version in the output. But now the - toolchain version is explicitly passed to all `cargo` and `cross` commands. +- The toolchain argument was (probably) not being respected with cross builds, though it's hard to + be sure since none of the output from past CI runs I've looked at it includes the toolchain + version in the output. But now the toolchain version is explicitly passed to all `cargo` and + `cross` commands. ## 0.0.6 - 2023-04-21 -- When the `strip` parameter was true, stripping binaries could fail if there - were both `target/*/debug` and `target/*/release` directories present and - the `debug` directory didn't have a binary. Now it will strip all binaries - it finds under `target`. +- When the `strip` parameter was true, stripping binaries could fail if there were both + `target/*/debug` and `target/*/release` directories present and the `debug` directory didn't have + a binary. Now it will strip all binaries it finds under `target`. ## 0.0.5 - 2023-03-19 -- Fix use of `dtolnay/rust-toolchain` action to allow passing a `toolchain` - input. +- Fix use of `dtolnay/rust-toolchain` action to allow passing a `toolchain` input. ## 0.0.4 - 2023-03-19 -- Added a new `toolchain` parameter to allow selecting a Rust toolchain other - than stable. This supports picking on of "stable", "beta", or "nightly". -- Fixed binary stripping to work in more situations. Previously it depended on - a very specific setup plus expected to be run in the context of the matrix I - use for my own projects. -- Fixed a reference to a matrix variable that should have referenced an input - variable. +- Added a new `toolchain` parameter to allow selecting a Rust toolchain other than stable. This + supports picking on of "stable", "beta", or "nightly". +- Fixed binary stripping to work in more situations. Previously it depended on a very specific setup + plus expected to be run in the context of the matrix I use for my own projects. +- Fixed a reference to a matrix variable that should have referenced an input variable. ## 0.0.3 - 2023-03-17 -- This action now supports running the `build` and `test` commands, or both, - with a new input parameter, `command`. The default is `build`. +- This action now supports running the `build` and `test` commands, or both, with a new input + parameter, `command`. The default is `build`. ## 0.0.2 - 2023-03-05 diff --git a/README.md b/README.md index c320489..c6f13de 100644 --- a/README.md +++ b/README.md @@ -86,7 +86,6 @@ be stripped either. ## Caching Rust Compilation Output -You can use the [Swatinem/rust-cache](https://github.com/Swatinem/rust-cache) -action with this one seemlessly, whether or not a specific build target needs -`cross. There is no special configuration that you need for this. It just -works. +You can use the [Swatinem/rust-cache](https://github.com/Swatinem/rust-cache) action with this one +seemlessly, whether or not a specific build target needs `cross. There is no special configuration +that you need for this. It just works. diff --git a/precious.toml b/precious.toml index 6da1d01..cbbfe0a 100644 --- a/precious.toml +++ b/precious.toml @@ -2,9 +2,19 @@ exclude = [ "target", ] -[commands.prettier] +[commands.prettier-md] type = "both" -include = [ "**/*.md", "**/*.yml" ] +include = [ "**/*.md" ] +cmd = [ "./node_modules/.bin/prettier", "--no-config", "--print-width", "100", "--prose-wrap", "always" ] +lint_flags = "--check" +tidy_flags = "--write" +ok_exit_codes = 0 +lint_failure_exit_codes = 1 +ignore_stderr = [ "Code style issues" ] + +[commands.prettier-yml] +type = "both" +include = [ "**/*.yml" ] cmd = [ "./node_modules/.bin/prettier", "--no-config" ] lint_flags = "--check" tidy_flags = "--write"