Scenario: I fork a project and submit a PR on Feature A, and then another on Feature B. I want to continue working with both features while I'm waiting for the PRs to be merged (theoretically they might never be if the upstream is abandoned).
Updated Requirement: I’ll have to push the changes to my fork remote so that the CI will pick them up.
I thought of two possibilities:
1. Create a branch in my fork which I treat like
upstream/master catches up and can be synced back to my fork, but is there a standard convention for naming such a branch?
2. Merging the feature branches into
master on my fork, which would simplify loading, but would require a forced push to merge
upstream/master later on, which I know is frowned upon.
What is the best way to handle this situation?