https://github.com/opqdonut/stacked-pr-test-repo

Surprising Github behaviour with stacked PRs
https://github.com/opqdonut/stacked-pr-test-repo

Last synced: about 1 month ago
JSON representation

Surprising Github behaviour with stacked PRs

• Host: GitHub
• URL: https://github.com/opqdonut/stacked-pr-test-repo
• Owner: opqdonut
• Created: 2024-08-08T10:43:37.000Z (5 months ago)
• Default Branch: main
• Last Pushed: 2024-08-08T10:55:55.000Z (5 months ago)
• Last Synced: 2024-10-18T11:25:09.396Z (3 months ago)
• Homepage:
• Size: 1.95 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
Surprising behaviour with stacked PRs.

1. Create two commits in sequence on top of main: main--A--B

2. Create a PR for commit A: [#1](https://github.com/opqdonut/stacked-pr-test-repo/pull/1)

3. Create a PR for commit B: [#2](https://github.com/opqdonut/stacked-pr-test-repo/pull/2)

    – shows both commits A and B

    - this is correct, in my opinion: merging #2 would add both commits to main

4. Merge PR A

5. PR B still shows commits A and B

    - this is wrong, in my opinion: A has already been merged and merging this PR won't include it

6. Create a new PR for commit B: [#3](https://github.com/opqdonut/stacked-pr-test-repo/pull/3)

    – now shows only commit B!

    - this is correct but new behaviour AFAIK – I don't think the PR creation time affected the contents previously