You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extracted from #8509 (Problem 1) for tracking work on this particular issue
Problem: Trying to push changes to a repo you don't have write access to
If you've cloned a repo and make some changes with the intent to contribute, you're basically stuck. You can't push those changes to the repo you've cloned because you don't have write access, and you can't bring them over to a fork that doesn't yet exist in a low-friction way.
Desktop could let you know you don't have write access and give you a nice pathway to fork and create a PR. This is conceptually similar to local commits to protected branches, where ideally we wouldn't allow you to do that (because you'd never be able to push those commits to that branch), and instead give you a nice path to somewhere where your work can eventually be pushed without issue.
A potential solution is outlined in #3918 by @say25.
The text was updated successfully, but these errors were encountered:
kuychaco
changed the title
After cloning without write access, fork and publish from Deskto
[Fork] After cloning without write access, fork and publish from Deskto
Oct 29, 2019
billygriffin
changed the title
[Fork] After cloning without write access, fork and publish from Deskto
[Fork] After cloning without write access, fork and publish from Desktop
Oct 29, 2019
Extracted from #8509 (Problem 1) for tracking work on this particular issue
Problem: Trying to push changes to a repo you don't have write access to
If you've cloned a repo and make some changes with the intent to contribute, you're basically stuck. You can't push those changes to the repo you've cloned because you don't have write access, and you can't bring them over to a fork that doesn't yet exist in a low-friction way.
Desktop could let you know you don't have write access and give you a nice pathway to fork and create a PR. This is conceptually similar to local commits to protected branches, where ideally we wouldn't allow you to do that (because you'd never be able to push those commits to that branch), and instead give you a nice path to somewhere where your work can eventually be pushed without issue.
A potential solution is outlined in #3918 by @say25.
The text was updated successfully, but these errors were encountered: