loadsys / loadsys/CakePHP-Shell-Scripts
Our Hoping to Accomplish List
还没有人认领这个 Issue。
- 主要语言
- Shell
- 星标
- 18
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
描述
Migrated from the new skeleton's README to here, since these are things I think we'd ideally like to be able to composer install into any of our 3.0 projects.
- auto test running
- auto code sniffing
- auto builds
- auto deploy to stage
- one-click code rollback
Some of this may necessitate the creation of a different repo from the CakePHP-Shell-Scripts project. Some of these things (if they mean what I think they mean) are stuff we used to accomplish with grunt. We either need to move the existing Gruntfile, package.json and associated node scripts into the new skeleton and tweak(/improve) as necessary to fulfill some of the goals, or develop an alternative approach.
Personally, I'd like to not necessarily need the node+npm+grunt stack. Instead I think we could use Cake Shells for some of this, and use a stand alone "watcher" program like kicker to execute them on file change. That may be more tooling that we want to rewrite at the moment though...
The last few are going to require coordination on the production hosting end of things too and may be more long term goals, but I'd love to pursue them.
To this list I would add:
- auto-publishing code coverage reports.
- auto-publishing generated documentation.
(I actually wrote a tool for this that remains completely untested currently: beporter/docs-manager.) See also: #56
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
这是一个广泛的路线图,而不是单一的实现任务。首先查看现有的 Gruntfile、package.json、相关的 node 脚本以及所引用的 #56 issue;列出的目标还需要与 production-hosting 进行协调。完成的要求是将愿望清单拆分为范围明确的任务,并就测试、构建、部署、回滚、覆盖率和文档发布制定一致认可的方法。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- node.js, php, shell
- 领域
- build-system, devops, release, tooling
- Issue 类型
- 功能
- 难度
- 5/5
- 预计耗时
- 一周以上
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 20/100