Michael Heap

Trello CLI has hit version 1.0 after _11_ years! Initially built as part of a hackday, Trello CLI showcases tools such as pnpm, changesets and oclif to build a CLI interface to Trello.

How to have GitHub send you notifications on Slack in real-time when events that you’re interested in occur. In my case, that’s when a GitHub Actions build fails.

Working in an open-core company, I regularly need to test open source contributions against enterprise builds of software (which need a license key, stored in a secret). Being able to provide secrets on-demand with GitHub Actions provides a great developer experience, whilst still maintaining security.

How I use `actions/github-script` and GitHub Actions to stage new blog posts for a static site, but still update the `created_at` date when merging a pull request

I’ve always struggled to manage my GitHub notifications. Having them pushed to me in real-time is overwhelming, but having a separate inbox to check means that I never remember to look at them. GitHub notifications can be separated in to two categories for me, periodic and real-time. Periodic are things that need doing, but not right now (a PR is ready to review, for example). Real-time are items where there is a real human interacting with you (someone’s commented or requested changes on your PR). It turns out that GitHub launched scheduled reminders back in 2020 which is a great fit for this use case. Scheduled reminders allow you to receive reminders at specific times throughout the day in addition to real-time alerts for specific events. You can configure them for yourself, or for a specific GitHub team.

Jon and Michael discuss how your own failure can actually benefit you in the long run, how to align your work to the needs and wants of others, the misconceptions of DevRel Strategies, and how personability for a manager is absolutely key. They also delve into why a manager should always be introspective and the difference it can make for the team.

A detailed walkthrough of the difference between `author_association` and permissions, and how to use each in a GitHub Actions workflow

Automatically raise a PR to a downstream repo whenever a file changes. The repos to submit PRs to are controller using a configuration file that looks like the following: ```json { "mheap/downstream": [ { "src": "my-file.yaml", "dest": "a-folder/mf.yaml" } ], "mheap/other-repo": [ { "src": "multiple.yaml", "dest": "multiple.yaml" }, { "src": "files-work.yaml", "dest": "too.yaml" } ] } ```