eed2bfe06a
Extend the CI checkstyle workflow to perform the library ABI checks in the master branch. The intent is not to prevent any ABI changes but to detect them immediately so when they're made it's done intentionally. When the changing the ABI the `make storeabi` target can be used to generate a new .abi file which can be included with the commit. This depends on the libabigail utility which is available from the majority of distribution package managers. Reviewed-by: George Melikov <mail@gmelikov.ru> Signed-off-by: Brian Behlendorf <behlendorf1@llnl.gov> Closes #11287
2.4 KiB
2.4 KiB
Motivation and Context
Description
How Has This Been Tested?
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Performance enhancement (non-breaking change which improves efficiency)
- Code cleanup (non-breaking change which makes code smaller or more readable)
- Breaking change (fix or feature that would cause existing functionality to change)
- Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
- Documentation (a change to man pages or other documentation)
Checklist:
- My code follows the OpenZFS code style requirements.
- I have updated the documentation accordingly.
- I have read the contributing document.
- I have added tests to cover my changes.
- I have run the ZFS Test Suite with this change applied.
- All commit messages are properly formatted and contain
Signed-off-by.