blender/flamenco
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Website: correct the OpenAPI commit guidelines

Browse Source 
The OpenAPI-generated code no longer contains the git hash, so the docs
had to change for that.
This commit is contained in:
Sybren A. Stüvel 2022-08-01 16:36:10 +02:00
parent fef3de28e1
commit 1db1b06c9e
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
web/project-website/content/development/openapi-commit-guidelines/_index.md
View File

@ -19,7 +19,6 @@ steps:
The downside to this approach is that the second commit will likely break the The downside to this approach is that the second commit will likely break the
project, which is unfortunate. However, this approach does have some advantages: project, which is unfortunate. However, this approach does have some advantages:
- The regenerated code has the commit hash of the actual change to the OpenAPI - The regenerated code has the right Flamenco version number.
definition.
- Changes to manually-written and generated code are tracked in separate - Changes to manually-written and generated code are tracked in separate
commits. This makes them easier to comprehend by humans. commits. This makes them easier to comprehend by humans.