Bug 507116 - Option to prevent push entirely to specific remote
Summary: Option to prevent push entirely to specific remote
Status: NEW
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: 4.5   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-06 09:42 EST by Ricky Veach CLA
Modified: 2016-11-06 09:42 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ricky Veach CLA 2016-11-06 09:42:17 EST
When you configure a fetch remote in egit, it automatically configures that remote for pushing. I have not found any option in egit to prevent pushing to a specific remote.

When you create a new remote, the dialog says 'for either fetch or push; you can add configuration for the other direction later' but this is misleading as a fetch remote automatically allows pushing.

I have write privileges to a repository, but I never want to push directly to it, to prevent accidentally changing something and breaking the branch. We use various CIs on PRs, so I just want to only be able to fetch new changes from that remote and push to a fork for the CIs to be checked first before merging.