I have implemented code with testing. All checks are ok but Doc Build and Upload workflow results error. In log there is nothing to find the root of error. Despite running workflow again with debug enabled, I didn't find any solution after googling a lot. https://github.com/hamedgibago/pandas/actions/runs/4459701029/jobs/7837174530
waiting for workers...
In file included from /home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1948,
from /home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:5,
from /home/runner/.cache/ipython/cython/_cython_magic_da5cd844e719547b088d83e81faa82ac.c:769:
/home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with " \
| ^~~~~~~
In file included from /home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/ndarraytypes.h:1948,
from /home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/ndarrayobject.h:12,
from /home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/arrayobject.h:5,
from /home/runner/.cache/ipython/cython/_cython_magic_14ff65f3705192578d563d86399e4562.c:770:
/home/runner/micromamba/envs/test/lib/python3.8/site-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:17:2: warning: #warning "Using deprecated NumPy API, disable it with " "#define NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
17 | #warning "Using deprecated NumPy API, disable it with " \
| ^~~~~~~
/home/runner/micromamba/envs/test/lib/python3.8/site-packages/nbsphinx/__init__.py:1043: RuntimeWarning: You are using an unsupported version of pandoc (3.1.1).
Your version must be at least (1.12.1) but less than (3.0.0).
Refer to https://pandoc.org/installing.html.
Continuing with doubts...
nbconvert.utils.pandoc.check_pandoc_version()
/home/runner/work/pandas/pandas/doc/source/whatsnew/v1.4.3.rst:86: WARNING: Cannot find contributors for range 'v1.4.2..v1.4.3': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.4.2..v1.4.3
stderr: 'fatal: ambiguous argument 'v1.4.2..v1.4.3': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
/home/runner/work/pandas/pandas/doc/source/whatsnew/v1.4.4.rst:79: WARNING: Cannot find contributors for range 'v1.4.3..v1.4.4|HEAD': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.4.3..HEAD
stderr: 'fatal: ambiguous argument 'v1.4.3..HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
/home/runner/work/pandas/pandas/doc/source/whatsnew/v1.5.0.rst:1299: WARNING: Cannot find contributors for range 'v1.4.4..v1.5.0': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.4.4..v1.5.0
stderr: 'fatal: ambiguous argument 'v1.4.4..v1.5.0': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
/home/runner/work/pandas/pandas/doc/source/whatsnew/v1.5.1.rst:136: WARNING: Cannot find contributors for range 'v1.5.0..v1.5.1': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.5.0..v1.5.1
stderr: 'fatal: ambiguous argument 'v1.5.0..v1.5.1': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
/home/runner/work/pandas/pandas/doc/source/whatsnew/v1.5.2.rst:60: WARNING: Cannot find contributors for range 'v1.5.1..v1.5.2': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.5.1..v1.5.2
stderr: 'fatal: ambiguous argument 'v1.5.1..v1.5.2': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
/home/runner/work/pandas/pandas/doc/source/whatsnew/v1.5.3.rst:72: WARNING: Cannot find contributors for range 'v1.5.2..v1.5.3': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.5.2..v1.5.3
stderr: 'fatal: ambiguous argument 'v1.5.2..v1.5.3': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
/home/runner/work/pandas/pandas/doc/source/whatsnew/v2.0.0.rst:1422: WARNING: Cannot find contributors for range 'v1.5.0rc0..v2.0.0|HEAD': Cmd('git') failed due to: exit code(128)
cmdline: git log --grep=Co-authored --pretty=%b v1.5.0rc0..HEAD
stderr: 'fatal: ambiguous argument 'v1.5.0rc0..HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]''
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
Originally posted by @hamedgibago in https://github.com/pandas-dev/pandas/issues/51503#issuecomment-1476578671
Comment From: MarcoGorelli
I think this is just if you open a PR to your own fork
I'd suggest just opening a PR to pandas-dev/pandas,
closing then, let's take the discussion to your PR
Comment From: hamedgibago
Sorry, you mean I open a pull request from my fork to main pandas? What about the error? Workflow will be green?
Comment From: MarcoGorelli
yup
we'll see, but this check looks like one that would only work if you're opening a PR to pandas
Comment From: hamedgibago
PR created, all checked are ok and resulted in green tick. Should I add Added [type annotations] and
Added an entry in the latest doc/source/whatsnew/vX.X.X.rst file if fixing a bug or adding a new feature. ? Are they necessary to the PR to be accepted?