From d4b31d20ca34dbd2cdad9238b8d03372a1e489a2 Mon Sep 17 00:00:00 2001 From: Brian Rose Date: Thu, 19 Jun 2025 09:59:13 -0400 Subject: [PATCH 1/3] Include jupyterlab in env for metrics --- environment.yml | 1 + 1 file changed, 1 insertion(+) diff --git a/environment.yml b/environment.yml index ee9c7b128..eef6da741 100644 --- a/environment.yml +++ b/environment.yml @@ -8,3 +8,4 @@ dependencies: - pre-commit - pyyaml - mystmd +- jupyterlab From 0800abe5033465bd741ed0ed86a14e99b254148f Mon Sep 17 00:00:00 2001 From: Brian Rose Date: Fri, 22 May 2026 08:55:49 -0400 Subject: [PATCH 2/3] Add new Julia Kent blog post to TOC --- portal/myst.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/portal/myst.yml b/portal/myst.yml index d6d0f679d..bba1f09e7 100644 --- a/portal/myst.yml +++ b/portal/myst.yml @@ -30,6 +30,9 @@ project: - file: about.md - file: blog.md children: + - title: "2026" + children: + - file: posts/2026/gh-actions.md - title: "2025" children: - file: posts/2025/mystification.md From 7ef4d172678ea4ed2cfe65e8b0da63661ee53c3d Mon Sep 17 00:00:00 2001 From: Brian Rose Date: Fri, 22 May 2026 09:04:36 -0400 Subject: [PATCH 3/3] Add new lines so images do not appear inline --- portal/posts/2026/gh-actions.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/portal/posts/2026/gh-actions.md b/portal/posts/2026/gh-actions.md index 3d164ab27..1ff1f833e 100644 --- a/portal/posts/2026/gh-actions.md +++ b/portal/posts/2026/gh-actions.md @@ -60,6 +60,7 @@ From what I can gather there are three main theories why a GitHub account can be There seems to have been a mass shadowbanning of GitHub accounts due to copilot usage. My connection at GitHub suggested that this was the likely culprit. But that seems unlikely to me, with my literally minimal usage: + ![0 Copilot Minutes](../../_static/images/posts/gh-actions/copilot-minutes.png) ### 2. Actions minutes @@ -94,17 +95,22 @@ To fix this: One workflow pattern now seems especially concerning: nightly rebuilds that repeatedly commit updates to `gh-pages`, often attributed to an individual maintainer account (i.e. mine). I noticed since we changed our Actions in 2025 that I had commits on days I knew I did not work (weekends, holidays, etc). + ![Weekend Commits](../../_static/images/posts/gh-actions/weekend-commits.png) + ![Weekend Commits 2](../../_static/images/posts/gh-actions/weekend-commits2.png) I accepted this as a non-issue, in part because it went on for a whole year before the shadowban. And partially because, when I would go to investigate the commits there would be none. + ![No Commits](../../_static/images/posts/gh-actions/no-commits.png) I didn't realize that the previous view defaulted to `main` instead of the branch where the commits are on - `gh-pages`. When I adjust my view, the commits become visible again. + ![GH-pages Commits](../../_static/images/posts/gh-actions/gh-pages-commits.png) And they do look, admittedly, very spammy; pushing Jupyter notebook metadata that does not need to be published. + ![Noisy Commits](../../_static/images/posts/gh-actions/noisy-commits.png) [We exorcised these ghost commits by dropping `gh-pages`](https://github.com/ProjectPythia/cookbook-actions/pull/179) and using the native GitHub-actions bot (instead of a user's account).