Here is an index of officially deprecated Bork assertion types and documentation on how to use them. These do not ship with Bork, and are only available from this repository.
Please note that legacy types are not routinely maintained by Bork's core maintainers. Pull requests are welcome on this repository, but there are no guarantees that the types included here will still work, or will not have bugs or security vulnerabilities. Generally speaking, a type makes it into the legacy repository if the upstream utility to which it corresponds is deprecated or otherwise no longer recommended for use.
This repository is structured identically to the main Bork repository, meaning you can 'drop in' the legacy types over the top of an existing Bork installation (which is roughly how the tests are done in CI). If you don't want to do this, you can simply download the type files you are interested in from the types/ directory, and register them with Bork as though they were custom types like so:
register pipsi.shYou can then use them in your scripts exactly like any other Bork assertion.
Please see the contributors' guide for further information about this repository, but in short, the usual rules of contributing to GitHub repositories apply:
- Fork it
- Create your feature branch:
git checkout -b feature/my-new-feature - Commit your changes:
git commit -am 'Add some feature' - Push to the branch:
git push origin feature/my-new-feature - Submit a pull request
Pull requests are subject to (generally automated) review. We will not accept pull requests whose tests fail or where Danger requests changes. This is a low-maintenance repository, and we trust our automated tools. There is more information about this approach in the contributors' guide.