Repository navigation
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Github PR support #1555
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
base: trunk
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Github PR support #1555
Changes from 1 commit
80867f615b063ec4ac2a6ef00943849c1506c16f8805b9a9085365518a6129f973d7c0692b720a3f2aaddfb8f1aecfe5a8f79aa89b44eaf18641b300126ede5bdbdfa3b574e761beed3b13549806d216bc929552File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
v1 PR export is update-only: creating a pull-request from git-bug is skipped with a NewExportNothing because it requires pushing the head branch to GitHub first (out of scope for the bridge). An attempt to export-create a PR surfaces a clear message pointing the user to open it on GitHub and re-import. For PRs that are already imported (metadata[github-id] present), existing update paths now route to PR-specific GraphQL mutations: * EditCreateComment (body edit) -> updatePullRequest.body * SetTitle -> updatePullRequest.title * SetStatus OPEN/CLOSED -> updatePullRequest.state * SetStatus MERGED -> skipped (merging must happen on GitHub; status then re-imports) * SetStatus DRAFT -> skipped in v1 * UpdateHead / AddReview / AddReviewComment -> skipped in v1 (no direct mapping for the head-commit tracking op, and write paths for review threads are a later commit) * LabelChange / AddComment -> unchanged; GitHub's labelable and addComment mutations accept PR node ids, so the existing issue path covers them. Adds updatePullRequestMutation + updateGithubPullRequestStatus / Body / Title helpers using githubv4.UpdatePullRequestInput. Signed-off-by: Giles Cope <gilescope@gmail.com>Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing