gpt4 book ai didi

patternlab.io - Pattern Lab 中的哪些内容应该提交到 master 分支?

转载 作者:行者123 更新时间:2023-12-04 03:48:22 26 4
gpt4 key购买 nike

我正在使用 Pattern Lab 开始我们的第一个项目,但我不知道我应该为我的团队做些什么。 Twig 构建附带一个 .gitignore 文件,该文件具有以下内容:

.DS_Store
composer.lock
config/*
export/*
packages/*
public/*
source/*
vendor/*

如果要共享并且要让多个开发人员做出贡献,似乎至少应该提交 source/* 。似乎还需要配置、包和供应商才能正确构建。我不确定导出是什么。

在公共(public)场合,我很确定我可以忽略一切,因为它似乎从头开始构建得很好。我们可以在单个本地机器以及服务器上构建。

那么这更像是应该被忽略的吗?对于一个一起工作的团队?
.DS_Store
composer.lock
public/annotations/
public/css/
public/images/
public/js/
public/patternlab-components/
public/patterns/
public/
public/favicon.ico

我还缺少另一个工作流程吗?如果在某个地方有关于此的资源,我无法找到它,但我很乐意简单地指向那里。

Also posed in the repo ,但看不到最近的事件。如果有回复,会在这里更新。

最佳答案

GitHub 项目的维护者 dmolsen 在那里回复了我。 https://github.com/pattern-lab/patternengine-php-twig/issues/15#issuecomment-202633762

他的回应与该 repo 直接相关:

The .gitignore is primarily focused on folks who use Composer to build or update their projects. If you downloaded the zip and expect that to be your own true copy then you're correct, a fair bit of the .gitignore can be removed.

packages/ and vendor/ can definitely be removed in that scenario. They get created by the Composer build process. Just note that you'll only want one member of your team running Composer update and pushing changes to the repo. Anything else could get really messy.

Adding config/ and source/ was probably overkill on my part. It's more to make sure I don't accidentally commit something but that's not going to happen in my dev environment anymore. Feel free to take them out. I'll remove them in the future too.

I'd leave export/ in as it's similar to public/. It's just a place to export clean patterns to and wouldn't need to be tracked. That's a new and undocumented feature.



感谢 dmolsen 的回复!

关于patternlab.io - Pattern Lab 中的哪些内容应该提交到 master 分支?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/36269721/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com