Improve Git deployment strategy with git archive #451
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
swalkinshaw
force-pushed
the
deploys-use-git-archive
branch
from
44c0ec8
to
75777d7
Compare
|
Docs: roots/docs#13 |
swalkinshaw
force-pushed
the
deploys-use-git-archive
branch
from
75777d7
to
36f6eba
Compare
Currently the deployment process looks like this: 1. Clone the repo into the `source` dir 2. Copy the `source` dir into a new release dir 3. Optionally move the `repo_subtree_path` directory to the release root 4. Optionally remove unwanted dirs in the new release This process leads to some complications and bugs. By copying the entire repo into the release dir and then moving the subtree, other directories are left behind that you manually need to clean up. There can also be conflicts if your subtree directory contains directories with the same name as directories in the repo's root. The new process looks like this: 1. Clone the repo into the `source` dir 2. Run `git archive` to populate the new release dir `git archive` already supports subtrees and through `.git_attributes`, other files/folders can be excluded.
swalkinshaw
force-pushed
the
deploys-use-git-archive
branch
from
36f6eba
to
fde4bea
Compare
swalkinshaw
added a commit
that referenced
this pull request
Dec 30, 2015
Improve Git deployment strategy with git archive
|
This doesn't copy git submodules in your repo. |
|
@jawngee well, you shouldn't be using git submodules. not sure why you're commenting on this considering you already opened a thread on discourse and haven't replied to my question on there. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently the deployment process looks like this:
sourcedirsourcedir into a new release dirrepo_subtree_pathdirectory to the release rootThis process leads to some complications and bugs. By copying the entire
repo into the release dir and then moving the subtree, other directories
are left behind that you manually need to clean up.
There can also be conflicts if your subtree directory contains
directories with the same name as directories in the repo's root.
The new process looks like this:
sourcedirgit archiveto populate the new release dirgit archivealready supports subtrees and through.gitattributes, other files/folders can be excluded.