You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/09/28 18:15:11 UTC

[GitHub] [airflow] dstandish commented on a diff in pull request #26759: Add docs re how to patch from main

dstandish commented on code in PR #26759:
URL: https://github.com/apache/airflow/pull/26759#discussion_r982724420


##########
docs/apache-airflow/production-deployment.rst:
##########
@@ -222,6 +222,29 @@ you can exchange the Google Cloud Platform identity to the Amazon Web Service id
 which effectively means access to Amazon Web Service platform.
 For more information, see: :ref:`howto/connection:aws:gcp-federation`
 
+
+Applying patches from ``main``
+==============================
+
+On occasion, a user may want to apply a patch from ``main`` which has not yet made it into a release.  Assuming you want to apply a specific PR to one of the official airflow images, you can apply roughly as follows.  It's also possible to apply a specific commit.
+
+.. code-block:: docker

Review Comment:
   right yeah it's a hard one... i thought about that ... i was trying to just be like... here's an example... there are other things you can do too so go google :)  
   
   because.... we already have a _lot_ of docs... and not trying to be an exhaustive 
   
   could patch single commit, could patch diff between two commits... or two tags... or what have you 
   
   e.g. here's the patch between 2.4 and some commit https://github.com/apache/airflow/compare/2.4.0..21c40cd4cc7830bc17a4180d8dd0fa2cc4ed9cea.patch
   
   what do you think's the best balance to strike?



-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org