Here's the Weekly Digest for gitgitgadget/gitgitgadget:

ISSUES

Last week 7 issues were created.
Of these, 6 issues have been closed and 1 issues are still open.

OPEN ISSUES

💚 #58 Improve Cc:ing, by dscho

CLOSED ISSUES

❤️ #64 ci: upgrade to node.js v10.x, by dscho
❤️ #63 Upgrade the Function and Pipelines to use node.js v10.x, by dscho
❤️ #62 Improve GitGitGadget's own CI by publishing the test results, by dscho
❤️ #61 CONTRIBUTING: we do not actually use Standard JS style, by dscho
❤️ #60 Bu-bye Probot, by dscho
❤️ #59 Remove reminders of the Probot approach, by dscho

NOISY ISSUE

🔈 #62 Improve GitGitGadget's own CI by publishing the test results, by dscho
It received 3 comments.

PULL REQUESTS

Last week, 8 pull requests were created, updated or merged.

MERGED PULL REQUEST

Last week, 8 pull requests were merged.
💜 #64 ci: upgrade to node.js v10.x, by dscho
💜 #62 Improve GitGitGadget's own CI by publishing the test results, by dscho
💜 #61 CONTRIBUTING: we do not actually use Standard JS style, by dscho
💜 #60 Bu-bye Probot, by dscho
💜 #56 Fix the "Published-As:" footer, by dscho
💜 #55 Drop extra MIME-Version headers, by dscho
💜 #54 Use correctly-encoded email headers for names with non-ASCII characters, by dscho
💜 #53 Fix formatting, by dscho

COMMITS

Last week there were 18 commits.
🛠️ [Merge pull request #64 ci: upgrade to node.js v10.x In theory, the (very simple) GitGitGadget code should compile easily
with any node.js version that supports ES6. In practice, only a proper
test suite can give us enough confidence that that is the case.

Luckily, even GitGitGadget's rather sparse test suite covers enough to
give us that confidence, and we should be able to upgrade to node.js
v10.x without issues (because v8.x is expected to not receive any
regular updates anymore come April '19, and not even security updates
come December '19).

This addresses part of https://github.com/gitgitgadget/gitgitgadget/issues/63.](https://github.com/gitgitgadget/gitgitgadget/commit/7b152960d5972228d8464ef75e27b1f67b726926) by derrickstolee
🛠️ Merge pull request #62 Improve GitGitGadget's own CI by publishing the test results Might just as well use Azure Pipelines' most convenient features... This will populate the "Tests" tab of the Azure Pipeline runs. by derrickstolee
🛠️ ci: upgrade to node.js v10.x In theory, the (very simple) GitGitGadget code should compile easily with any node.js version that supports ES6. In practice, only a proper test suite can give us enough confidence that that is the case. Luckily, even GitGitGadget's rather sparse test suite covers enough to give us that confidence, and we should be able to upgrade to node.js v10.x without issues (because v8.x is expected to not receive any regular updates anymore come April '19, and not even security updates come December '19). Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Publish the test results in GitGitGadget's own CI Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Support 'npm run ci' for Continuous Integration This will be run in the Azure Pipeline that tests GitGitGadget itself. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Install jest-unit as dev dependency We will use this to report the test results on the Azure Pipeline that tests GitGitGadget PRs. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Merge pull request #61 CONTRIBUTING: we do not actually use Standard JS style Standard JS does not really make sense for Typescript projects. by derrickstolee
🛠️ Merge pull request #60 Bu-bye Probot Since GitGitGadget is no longer a web app, but rather a serverless Azure Function that triggers a dedicated Azure Pipeline (making it much faster in the process, not to mention the nice PR Check that lets users even see the logs), we no longer need Probot. by derrickstolee
🛠️ [Merge pull request #56 Fix the "Published-As:" footer It was incorrect all the time (and nobody noticed except for me).](d211d2a) by derrickstolee
🛠️ [Merge pull request #55 Drop extra MIME-Version headers As explained in https://github.com//issues/38, sometimes we end up with mails that have multiple MIME-Version headers.

In order to avoid being filed away in the spam folder, let's just post-process the generated mails to remove duplicate MIME-Version headers.](a2d32d1) by derrickstolee
🛠️ Merge pull request #53 Fix formatting Just one of those huge changes due to late discovery of auto-formatting rules... by derrickstolee
🛠️ CONTRIBUTING: we do not actually use Standard JS style Standard JS does not really make sense for Typescript projects. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ CONTRIBUTING: remove comment about Probot It no longer applies. While at it, mention scripts/. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Clarify that the GitGitGadget class is no longer backing a Probot-based app Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Uninstall probot/smee related packages We are no longer using Probot... Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Make @octokit/rest an explicit dependency, upgrading to latest version Currently, we use @octokit/rest's classes, but we only have it as an indirect dependency via probot. This is not only fragile, it also needs to be fixed because we are about to remove the latter dependency (GitGitGadget is no longer based on Probot). Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Update TODOs A lot of them have been addressed already, or became obsolete. We should probably move those TODOs into GitHub issues... Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho
🛠️ Remove Probot-related source code We no longer use a Probot-based setup, but instead an Azure Function that in turn triggers an Azure Pipeline. Signed-off-by: Johannes Schindelin johannes.schindelin@gmx.de by dscho

CONTRIBUTORS

Last week there were 2 contributors.
👤 derrickstolee
👤 dscho

STARGAZERS

Last week there were no stargazers.

RELEASES

Last week there were no releases.

That's all for last week, please 👀 Watch and ⭐ Star the repository gitgitgadget/gitgitgadget to receive next weekly updates. 😃

You can also view all Weekly Digests by clicking here.

Your Weekly Digest bot. 📆