After following the setup instructions, I created a new theme called [root]/src/themes/custom-theme-test. I noticed that the files within custom-theme-test were showing up in source control.
Is this the expected behaviour? (Perhaps only an issue if you git clone rather than export Lamb ...)
My thinking is, I'd probably be inclined to move my custom theme into it's own repository separate from Lamb itself. This way I can version control my customisations independently of Lamb updates.
If not, then I think a modification to the .gitignore file that could be appropriate would be something like the following.
# Ignore custom themes by default
/src/themes/
!/src/themes/2024
!/src/themes/default
Essentially version control any default/included themes, and ignore the rest.
After following the setup instructions, I created a new theme called
[root]/src/themes/custom-theme-test
. I noticed that the files withincustom-theme-test
were showing up in source control.Is this the expected behaviour? (Perhaps only an issue if you
git clone
rather than export Lamb ...)My thinking is, I'd probably be inclined to move my custom theme into it's own repository separate from Lamb itself. This way I can version control my customisations independently of Lamb updates.
If not, then I think a modification to the
.gitignore
file that could be appropriate would be something like the following.Essentially version control any default/included themes, and ignore the rest.