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
{{ message }}
This repository has been archived by the owner on Jan 29, 2019. It is now read-only.
These are not really equivalents: a svn export is a distribution of the source code, without the version control history etc. While the git clone command actually creates a local repository.
The git equivalent seems to be archive. The reason I'm asking is because I wanted to use .gitattributes to exclude certain paths from exporting (to save time), but that does not work with clone.
Not sure if the default action should be changed (seems like a BC break), or if it should be configurable. But it would be nice if this was fixed to be similar across VCS systems.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As is stands now, the
export
task actually does the following:For git:
git clone
For svn:
svn export
These are not really equivalents: a svn export is a distribution of the source code, without the version control history etc. While the git clone command actually creates a local repository.
The git equivalent seems to be archive. The reason I'm asking is because I wanted to use
.gitattributes
to exclude certain paths from exporting (to save time), but that does not work with clone.Not sure if the default action should be changed (seems like a BC break), or if it should be configurable. But it would be nice if this was fixed to be similar across VCS systems.
The text was updated successfully, but these errors were encountered: