![]() ![]() My biggest question is whether these are always consistent across these scenarios. These are the ones we've discussed, but there may be other things that likely depend on this preference about whether you're on a fork with the intention of contributing back to upstream, or on a fork because that's where you're contributing to. ![]() Using fork to contribute to fork: Ability to easily stay up to date with latest from fork Any others? Using fork to contribute to upstream: Ability to easily stay up to date with latest from upstream repo's default branch Using fork to contribute to fork: View pull requests for the fork repo Staying up to date Using fork to contribute to upstream: View pull requests for the upstream repo Using fork to contribute to fork: Create PR from fork targeting fork (this represents a divergence from the default behavior of, which by default targets new PRs toward upstream) Viewing list of pull requests in the PR tab of the branch list Using fork to contribute to upstream: Create PR from fork targeting upstream Using fork to contribute to fork: Create issue in fork repo Creating a pull request Using fork to contribute to upstream: Create new issue in upstream repo (documented in #9232) In other words, are they on the fork because they're just trying to contribute to the upstream repo? Is this a "long-running" fork that's intended to diverge entirely from upstream? Something else? In talking through this, we think there may be several connected elements that may operate similarly depending on the preference. Describe the feature or problem you’d like to solveĬurrently, there are several places in GitHub Desktop where how the interaction should work in the app when someone is on a fork is highly dependent on someone's relationship to the project. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |