This is an automated email from the ASF dual-hosted git repository.

gurwls223 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new 893feb9  [SPARK-37511][DOCS][FOLLOW-UP] Fix documentation build 
warning from TimedeltaIndex
893feb9 is described below

commit 893feb90a73c0c7827ebb6892980dc6227e64ae4
Author: Hyukjin Kwon <[email protected]>
AuthorDate: Thu Dec 2 17:47:44 2021 +0900

    [SPARK-37511][DOCS][FOLLOW-UP] Fix documentation build warning from 
TimedeltaIndex
    
    ### What changes were proposed in this pull request?
    
    This PR is a followup of https://github.com/apache/spark/pull/34657 that 
adds underline to match with the title.
    
    ### Why are the changes needed?
    
    To fix the PySpark documentation build warning:
    
    ```
    /.../spark/python/docs/source/reference/pyspark.pandas/indexing.rst:340: 
WARNING: Title underline too short.
    
    TimedeltaIndex
    -------------
    ```
    
    ### Does this PR introduce _any_ user-facing change?
    
    No, dev-only.
    
    ### How was this patch tested?
    
    Manual build of the PySpark documentation.
    
    Closes #34775 from HyukjinKwon/SPARK-37511.
    
    Authored-by: Hyukjin Kwon <[email protected]>
    Signed-off-by: Hyukjin Kwon <[email protected]>
---
 python/docs/source/reference/pyspark.pandas/indexing.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/python/docs/source/reference/pyspark.pandas/indexing.rst 
b/python/docs/source/reference/pyspark.pandas/indexing.rst
index 8747230..0c94012 100644
--- a/python/docs/source/reference/pyspark.pandas/indexing.rst
+++ b/python/docs/source/reference/pyspark.pandas/indexing.rst
@@ -337,7 +337,7 @@ DatatimeIndex
    DatetimeIndex
 
 TimedeltaIndex
--------------
+--------------
 .. autosummary::
    :toctree: api/
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to