We're currently always skipping the detection of open bugs/features, so
even though [0] introduced authentication to GitHub, this didn't
actually lead to the lookup when running in CI.
If we're not running in Renovate's CI build (i.e. as part of the release
process) or the docs site's CI build (as part of post-release
operations) we should continue to skip the build, when running in CI.
This also makes it clearer with a WARN log line to explain why this is
being skipped.
This is a re-apply of ae46c57f56, as well
as making sure that the `GITHUB_TOKEN` is explicitly passed as
`extraEnv`, otherwise we see i.e.
```
ERROR: Error getting query results
"err": {
"cmd": "/bin/sh -c gh issue list --json \"title,number,url,labels\" --search \"type:Bug\" --limit 1000",
"stderr": "gh: To use GitHub CLI in automation, set the GH_TOKEN environment variable.\n",
"stdout": "",
"options": {
"encoding": "utf-8",
"env": ["CI", "HOME", "PATH", "LANG"],
"maxBuffer": 10485760,
"timeout": 900000
},
"exitCode": 4,
"name": "ExecError",
"message": "Command failed: gh issue list ...\ngh: To use GitHub CLI in automation, set the GH_TOKEN environment variable.\n",
"stack": "ExecError: Command failed: gh issue list ...\ngh: To use GitHub CLI in automation, set the GH_TOKEN environment variable.\n\n at ..."
}
```
As we can see, the `env` isn't automagically picking up the
`GITHUB_TOKEN`, so we should explicitly pass it.
[0]: https://github.com/renovatebot/renovatebot.github.io/pull/746
* Revert "fix(docs): wire in `GH_TOKEN` for `gh` CLI (#39812)"
This reverts commit 295eaac4d0.
* Revert "fix(docs): add required permissions for `build:docs` (#39809)"
This reverts commit bbd30ce930.
* Revert "fix(docs): look up open issues on `main` builds for Renovate docs (#39801)"
This reverts commit ae46c57f56.
We're currently always skipping the detection of open bugs/features, so
even though [0] introduced authentication to GitHub, this didn't
actually lead to the lookup when running in CI.
If we're not running in Renovate's CI build (i.e. as part of the release
process) or the docs site's CI build (as part of post-release
operations) we should continue to skip the build, when running in CI.
This also makes it clearer with a WARN log line to explain why this is
being skipped.
[0]: https://github.com/renovatebot/renovatebot.github.io/pull/746
Michael Kriese