facade

关于接下来要写什么：

你们在这个时间点看到的文章已经把Laravel的Database部分都讲完了，接下来的计划是：

事件系统、用户认证系统、异常处理、Session以及Laravel应用请求整个生命周期的总结，当然我也想把
Composer原理和Laravel中用到的设计模式说一下以便更好的理解。时间来到了6月，希望能在18年把Laravel这些核心相关的东西大体梳理完，把年初挖的这个坑填上。

关于问题反馈和交流：
我在写这些文章时都会尽量严谨防止由于自己的失误误导大家，有的部分源码过多也就难免会有贴上了大块源码的地方，如果有看不懂的也欢迎针对话题新开issue来讨论。

The way it is now:

If collecting commit data fails due to a git checkout error (e.g. permissions error on the repo directory, missing git executable, etc.), the Repo nevertheless gets marked as "Update" and no attempt is made to ever check out the repo again.

The way it should be:

If a worker can't check out a git repo, or can't extract data from it, it should keep retrying until the situ

Currently docs only get published on release.

It would be great if we could publish the docs for main on each push/merge.

Questions

• Which version would these docs have?

I think a great feature of this package would be to allow the underlying mailable to return the message_id

I recall you can do something like this

 $this->withSwiftMessage(function ($message) {
    /// $message->getId() available here.
  });

I think it would be great if you're tracking opens/clicks from these services and their web hooks.

I personally do this with mai