gdgbaroda / gdgbaroda.github.io

GDG Baroda Website
Apache License 2.0
10 stars 17 forks source link

Add upstream as remote #79

Closed HackyRoot closed 5 years ago

HackyRoot commented 5 years ago

Prerequisites

Description

Can't add upstream master as a remote.

Steps to Reproduce

1.cd gdgbaroda.github.io

  1. git remote add upstream https://github.com/gdgbaroda.github.io
  2. git pull upstream master

Expected behavior: [What you expect to happen] Fetch lastest changes from the upstram.

Actual behavior: [What actually happens] remote: Not Found fatal: repository 'https://github.com/gdgbaroda.github.io/' not found

Reproduces how often: [What percentage of the time does it reproduce?] 100

manan-jadhav commented 5 years ago

This is the URL you should be using, please follow githubs guide before reporting. Thank you.

https://github.com/gdgbaroda/gdgbaroda.github.io.git

On Wed, Jan 30, 2019, 12:25 PM Pratik Parmar <notifications@github.com wrote:

Prerequisites

Description

Can't add upstream master as a remote. Steps to Reproduce

1.cd gdgbaroda.github.io

  1. git remote add upstream https://github.com/gdgbaroda.github.io
  2. git pull upstream master

Expected behavior: [What you expect to happen] Fetch lastest changes from the upstram.

Actual behavior: [What actually happens] remote: Not Found fatal: repository 'https://github.com/gdgbaroda.github.io/' not found

Reproduces how often: [What percentage of the time does it reproduce?] 100

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gdgbaroda/gdgbaroda.github.io/issues/79, or mute the thread https://github.com/notifications/unsubscribe-auth/AChAPAR2rKzGquC-eUqoxqAzD_hqSS9uks5vIdWbgaJpZM4aasAL .

SnehPandya18 commented 5 years ago

The issue is produced due to malformed URL and thus closing the reported issue.

HackyRoot commented 5 years ago

@CurosMJ I read that guide thus I created this issue to make a change in our contribution guide. Should I submit a PR?

SnehPandya18 commented 5 years ago

Sure, go ahead. This issue stays closed, we're expecting a separate PR with required fix.