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
Right now, when we deal with a remote repository, we often mock the calls to that repository as we initially assume it to be hosted on Github.
However, with the refactoring work for repo-smith version v1.0.0, I realized that it is possible to have a clone of a "remote" repository where the remote repository is actually stored on the local machine as a bare repository (more here). So, we might be able to work with this without doing all of these mocked behavior.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Based on git-mastery/exercises#124
Right now, when we deal with a remote repository, we often mock the calls to that repository as we initially assume it to be hosted on Github.
However, with the refactoring work for
repo-smithversionv1.0.0, I realized that it is possible to have a clone of a "remote" repository where the remote repository is actually stored on the local machine as a bare repository (more here). So, we might be able to work with this without doing all of these mocked behavior.Beta Was this translation helpful? Give feedback.
All reactions