Revision 6d2e9090247f86cc84dc7ca1087073710140fb67 authored by Roman Donchenko on 28 March 2024, 15:51:09 UTC, committed by GitHub on 28 March 2024, 15:51:09 UTC
It has occurred to me that the documentation build happens inside the main workflow, which is configured to ignore changes to the docs when determining whether to run. So if a PR only changes the docs... we don't build the docs. That makes no sense. Fix this by extracting the documentation job into its own workflow, that always runs. The downside of this is that we have to duplicate the work of generating the SDK, but IMO, it's an acceptable sacrifice. A side effect of this is that a failure to build the docs no longer prevents the publishing of Docker images, but I don't think that was needed in the first place.
1 parent 6eb7b7d
README.md
# cvat-data module
```bash
yarn run build # build with minification
yarn run build --mode=development # build without minification
yarn run server # run debug server
```
## Versioning
If you make changes in this package, please do following:
- After not important changes (typos, backward compatible bug fixes, refactoring) do: `yarn version --patch`
- After changing API (backward compatible new features) do: `yarn version --minor`
- After changing API (changes that break backward compatibility) do: `yarn version --major`
Computing file changes ...
