Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add documentation for forkToken #9701

Merged
merged 9 commits into from Apr 24, 2021
7 changes: 7 additions & 0 deletions docs/usage/self-hosted-configuration.md
Expand Up @@ -200,6 +200,13 @@ It will also override any settings in `packageRules`.
## forkMode

You probably have no need for this option - it is an experimental setting for the Renovate hosted GitHub App.
However, if this is set to true then Renovate will clone the repository before working on the clone and creating Pull Requests on the parent (GitHub only).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
However, if this is set to true then Renovate will clone the repository before working on the clone and creating Pull Requests on the parent (GitHub only).
However, if this is set to `true` then Renovate will clone the repository before working on the clone and creating Pull Requests on the parent (GitHub only).

Let's put true in monospaced font.

Also it's really confusing to read: "Renovate will clone the repository before working on the clone"...
I don't know what the behavior is, but the way its worded now is not helping me understand what's happening.

The way I understand Renovate is that it always clones the repo before doing stuff???

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, wording is misleading, I meant fork instead of clone. Let me rephrase.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct, wording is misleading, I meant fork instead of clone. Let me rephrase.

I thought some wires got crossed somewhere. 😄
I'll let you rephrase this. 😉

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have updated the wording, does it make more sense now?


## forkToken
Chumper marked this conversation as resolved.
Show resolved Hide resolved

You probably have no need for this option - it is an experimental setting for the Renovate hosted GitHub App.
This should be set to a personal access token (GitHub only) when `forkMode` is set to `true`.
Chumper marked this conversation as resolved.
Show resolved Hide resolved
Renovate will use this token to clone the repository and to create Pull Requests on the parent.

## gitAuthor

Expand Down
9 changes: 9 additions & 0 deletions lib/config/definitions.ts
Expand Up @@ -340,6 +340,15 @@ const options: RenovateOptions[] = [
default: false,
admin: true,
},
{
name: 'forkToken',
description:
'Will be used on GitHub when `forkMode` is set to `true` to clone the repositories.',
stage: 'repository',
type: 'string',
default: '',
admin: true,
},
{
name: 'requireConfig',
description: 'Set to true if repositories must have a config to activate.',
Expand Down