Git PR Automator FAQs

Question 1

How does the skill handle duplicate pull requests?

Accepted Answer

The skill is idempotent; it checks for existing PRs via the GitHub API before attempting to create a new one, providing the existing URL instead of creating a duplicate.

Question 2

What happens if my fork has a different name than the upstream repository?

Accepted Answer

The skill uses smart detection via the GitHub API to identify your fork regardless of its name and correctly configures the origin and upstream remotes.

Question 3

Is DCO sign-off supported for commits?

Accepted Answer

Yes, all commits generated by the skill automatically include the -s flag to ensure Developer Certificate of Origin (DCO) compliance for open-source contributions.

Question 4

Does this skill require the GitHub CLI?

Accepted Answer

Yes, you must have the GitHub CLI (gh) installed and authenticated on your machine for the skill to perform forks and create pull requests.

Question 5

Can I use this with an existing local repository?

Accepted Answer

Absolutely. You can specify the current directory as the workspace to automate the PR process for a repository you already have cloned locally.

Git PR Automator

关于

主要功能

使用场景

Git PR Automator

关于

主要功能

使用场景