Skip to content

Local repos should ignore ALL remote functionality #84

Description

@Smolations

If creating a local repo with no remote, there are two pieces of remote functionality which come into play that should not; both happen to occur after a commit:

  1. After committing, an "Aborting..." error message is shown. I think this has something to do with the fact that no remotes are found, so that function aborts. It should return an error code instead.
  2. If the branch you are committing to happens to be in the protected list, you still receive the message "WARNING: Pushing to master is not allowed. Aborting..." after the local commit occurs. This message is superfluous.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions