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.

Sign up for GitHub

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

Jump to bottom

Investigate PR edge cases #63

Open

ermshiperete opened this issue May 6, 2020 · 0 comments

Milestone

Collaborator

ermshiperete commented May 6, 2020

Check how we deal with the following scenarios:

PR gets merged; user makes additional changes to single-keyboard repo (skr), creates a new PR
user creates a PR; abandons PR, makes additional changes in skr, and creates a new PR
user creates a PR; abandons PR, resets skr, does force-push on skr, and creates a new PR
PR gets merged; some changes get made directly in keyboards repo; user makes changes in skr, creates a new PR

(a PR here means getting the changes from the single-keyboard repo into keyboards repo)

ermshiperete mentioned this issue

feat(backend): e2e tests for creating a pull request (#61) #62

Merged

ermshiperete added this to the Future milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment