exclude wwwroot\umbraco\lib folder. It gets regenerated on each run. #4
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
|
Great, thanks! |
|
Ok, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi Dennis,
I have exclude wwwroot\umbraco\lib folder, because it gets regenerated on each run.
Hopefully Umbraco or Community (maybe me) will document an updated .gitignore for V9馃檮
Btw. again I create this PR for the feature/integration-products branch, because it seems to be your current WIP branch.
In general I think it would be better to use the master branch. My experience with git is: short life times for feature branches are the best to avoid merging conflicts or limit the effort of solving these.
What do you think about branch targets and git collaboration?
Have a nice weekend!
/Dirk