jedcunningham opened a new pull request #18419:
URL: https://github.com/apache/airflow/pull/18419


   Missing newlines in the new pre-commit hook is causing the `docker-stack` 
docs build to fail:
   
   e.g: 
https://github.com/apache/airflow/pull/18417/checks?check_run_id=3669346986
   ```
   ############################## Start docs build errors summary 
##############################
   
   ============================== docker-stack ==============================
   ------------------------------ Error   1 --------------------
    WARNING: Explicit markup ends without a blank line; unexpected unindent.
   
   File path: docker-stack/build-arg-ref.rst (73)
   
     68 | 
+------------------------------------------+------------------------------------------+---------------------------------------------+
     69 | 
     70 | List of default extras in the production Dockerfile:
     71 | 
     72 | .. BEGINNING OF EXTRAS LIST UPDATED BY PRE COMMIT
   > 73 | * amazon
     74 | * async
     75 | * celery
     76 | * cncf.kubernetes
     77 | * dask
     78 | * docker
   ------------------------------ Error   2 --------------------
    WARNING: Bullet list ends without a blank line; unexpected unindent.
   
   File path: docker-stack/build-arg-ref.rst (99)
   
     94 | * sftp
     95 | * slack
     96 | * ssh
     97 | * statsd
     98 | * virtualenv
   > 99 | .. END OF EXTRAS LIST UPDATED BY PRE COMMIT
    100 | 
    101 | Image optimization options
    102 | ..........................
    103 | 
    104 | The main advantage of Customization method of building Airflow image, 
is that it allows to build highly optimized image because
   
   ############################## End docs build errors summary 
##############################
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to