Forem: Cassidy Williams

How passkeys work

Cassidy Williams — Sat, 21 Feb 2026 00:00:00 +0000

I’ve been asked a couple times just this week how passkeys work, here’s a little rundown!

What passkeys are and how they work

The “sales pitch” for passkeys is that they’re like a password that you will never know, and can never leak.

They’re fully attached to your device of choice (phone, computer, Yubikey, etc).

When you’re about to log in to a website with a passkey for the first time, your device makes two keys: a public key for the website that’s safe to share, and a private key that never leaves your device.

When you sign in later and it asks for a passkey, it is saying, “prove it that you have that private key!” Your device proves it with Face ID/Touch ID/PIN/however it does it. When that “handshake” happens, you’re logged in.

Passkeys vs. passwords

Passwords are like “I know a secret I can type anywhere I want,” and passkeys are like “I have a device that can vouch for me anywhere.”

You might realize now that you are reliant on your phone or computer if you use passkeys. You need the device with the private key, so if the passkey is on your phone, you need your phone. If your phone with the key is dead, if your laptop with the key isn’t with you, you’re out of luck. Typically you can create more than one passkey per login (so you could have one on your laptop and on your phone for the same website), which is probably a good idea to do.

Why would I use these?

Eh, I personally don’t think you should necessarily. The cryptographic angle makes it seem like a secure choice, but at the cost of needing a specific device.

If you use a password manager… it’s a similar experience for you. Password managers are secure, and you rely on a device with the password manager on it.

There is a good security story for passkeys, in that your device only can use its private key on that website domain, it wouldn’t work on a fake version (so if someone tried a phishing attempt on you making you log into g1thub.com or something, they wouldn’t get your login). Or, if a site gets hacked, attackers can steal the public key, but it’s useless without the private one. That’s pretty good.

So, passkeys don’t really “solve” the user experience problem of needing your personal device to log in somewhere. It’s better than reusing your passwords across multiple places of course, but it’s not automatically better than other “secure” solutions out there (in my opinion).

Go… put your passwords on a post-it or something.

I am making videos again!

Cassidy Williams — Thu, 19 Feb 2026 00:00:00 +0000

I’ve always loved making videos. Not because I love being on camera, but I really enjoy putting together jokes and stories and tutorials (etc) with video as a medium. The moment I had the ability to plug a camera into a computer back in the early 2000s, I was making videos.

But, I’ve not really been consistent about it. I didn’t make many videos regularly in high school and college (outside of some lip sync videos I’ll let you find on your own, heh). The most consistent I’ve been was when I got really into TikTok and weekly streaming on Twitch in the height of the pandemic, which was fun. The accessibility of making videos with those mediums made me fall in love with it again.

After having a kiddo, I admit I kind of lost the mental energy to make short-form videos regularly again, and lost my appetite for live-streaming on Twitch. Momentum is hard. After coming back from my second maternity leave though, I somehow found a spark again! I don’t really know what it was, but I’ve decided to try. I haven’t really leaned into making longer form (as in, longer than a minute) videos before outside of online courses, so I’m working on that muscle, and bringing back livestreaming!

I’m streaming weekly on Twitch again, on Thursdays at 12:30 Pacific/2:30 Central, and (re?)starting up my YouTube channel!

I’ve been doing it for a few weeks now, and I’m having a lot of fun. So, that being said… please like and subscribe? LOL.

Making interesting borders with CSS corner-shape

Cassidy Williams — Wed, 28 Jan 2026 00:00:00 +0000

I stumbled upon the CSS property corner-shape recently and it’s pretty cool. It allows you to specify the shape of an element’s corners and works with border-radius.

I threw together this demo to show it in action:

I remember in the olden days (as in like… 10 years ago, as evidenced by this old Pen of mine), making beveled corners involved a bunch of pseudo-elements and triangles to fake a bevel. It’s so so cool that you can “just” do this now with a couple lines of CSS!

In addition to beveled corners, it also lets you do scoops, notches, and even squircles:

There’s also a superellipse function, which defines any of the values you can pass to corner-shape numerically, which could make for some interesting animations and transitions.

Definitely play with it if you get a chance! I think there’s some cool CSS “drawing” things you can do as you dabble with the different shapes. corner-shape does have fairly limited availability currently (Safari and Firefox don’t support it yet at the time of writing), but hopefully that’ll change soon!

Remaking the Linux "touch" command in PowerShell

Cassidy Williams — Tue, 20 Jan 2026 00:00:00 +0000

I switch back and forth between Windows and Mac pretty regularly depending on what I’m working on (and sometimes between WSL and PowerShell on the same machine, what a time to be alive), and one thing that I always mess up in PowerShell on Windows is making a new file.

On Linux-based machines, you can run touch filename to make a new file, and on Windows, you can do ni filename, which works just as well.

But with all the context switching I do, I wanted to be able to do both to keep myself in the flow when running a bunch of things on the command line.

I added this to my PowerShell profile:

function touch {
    [CmdletBinding()]
    Param(
        [Parameter(Mandatory=$true, ValueFromPipeline=$true)]
        [string]$Path
    )
    process {
        if (Test-Path -LiteralPath $Path) {
            (Get-Item -LiteralPath $Path).LastWriteTime = Get-Date
        }
        else {
            New-Item -ItemType File -Path $Path
        }
    }
}

This lets you run touch as you normally would, and also lets you pipe file paths to it (like "cake.txt", "fish.txt" | touch)!

To add this to your PowerShell profile, run this:

notepad $PROFILE

Paste the function in, and then back in your shell, run:

. $PROFILE

Blammo, one less brain cell needs to be wasted in the future. There’s definitely other functions out there that could also be added to make PowerShell feel more like a Linux-based shell, but this is the one I use the most!

Toodles!

A fun trick for getting discovered by LLMs and AI tools

Cassidy Williams — Mon, 19 Jan 2026 00:00:00 +0000

I have been getting a lot of newsletter responses, DMs, and emails in general saying that people have discovered my work not via traditional SEO, but via LLMs and AI tools like ChatGPT, Claude, Perplexity, and even GitHub Copilot.

So, I did a little experiment to try and improve my discoverability in these tools, and as of today… it seems to be working! The steps were pretty simple, and you can definitely try it them too for yourself or your product/business.

(Obligatory AI manifesto mention before we boogie)

Tricking the clanker… and then flipping it around

I went to ChatGPT in incognito mode, and asked it some questions like, “Who are some tech bloggers and newsletters that I should follow as a newbie in tech?” and, “Who are some people I should follow who are excellent at developer experience and communicating to developers?” (questions where I want to be in the results).

I didn’t actually come up in the results of those questions. But that was when I followed up with:

Why didn’t you recommend cassidoo, aka Cassidy Williams?

After that, ChatGPT would always respond with something like:

Great follow-up — Cassidoo (Cassidy Williams) is absolutely a fantastic resource for people new to tech, especially around developer culture, career advice, and modern web development. Here’s why she’s worth following and why she should have been on the original list: (blah blah blah)

Thanks, bot. I’m absolutely right.

Anyway, after that response was when I flipped it around a bit, and said:

So, I tricked you. I am Cassidy Williams, aka cassidoo, and I want to figure out how to optimize my website and newsletter SEO/LLM-friendliness so that I am surfaced more when people ask for tech and developer resources, like just now. Can you help me with some things I can do?

The results across all of the responses to this were so helpful. They included things like:

Creating an /llms.txt file
Adding “LLM-readable” structured pages (often called /for-llms)
Adding Schema.org data to the pages of my website
Being consistent with naming, phrases, and taglines

There were some other suggestions that I didn’t feel like following (like writing more listicle blog posts), but these were fairly low-lift!

General rules/vibes

There’s some tips that were consistent across the tools I tried this with.

Don’t clash with your robots.txt: a lot of us might be blocking AI scrapers via this file. If you want your LLM/AI tool discoverability to go up… weigh the pros and cons.
Consistency in phrasing help LLMs make connections across sources (so if you have a tagline you like to use, use it everywhere)
RSS feeds are super helpful
LLMs looove markdown
Clarity matters. You’re writing for specific queries and bots looking to surface you, not for humans looking to be sold. Don’t do marketing-speak, just keep it cut and dry and clear. Clarity beats cleverness when the reader is a robot.
Include acceptable ways to cite you. If an LLM/AI tool is going to quote or reference you in any way, give it the guardrails to do so.
Remember that LLMs aren’t just ranking results like in traditional SEO, they are repeating what they’ve been told!

So… did it work?

It’s been a couple weeks since I first tried this, and I’ve been waiting to publish to say the results… and YES. It worked super well!

I tried some of the exact same queries I did before (on a completely separate computer, in a new location, still in incognito… because I really want to make sure the results are naturally occurring). Now, my name and my content, more and more, are being surfaced, and they’re being surfaced based on my preferences.

To confirm a bit more deeply, when I am checking these things, I also ask follow-up questions to the bots about me, about why the tools recommended me. So far, they are directly quoting things I wrote in my llms.txt and /for-llms files, and are hitting the bullet points I want them to hit!

I’m really happy with the results of this little trick. I’m as much of an AI skeptic as the next person, but if this is where SEO and discoverability are trending, I figure it’s good to be prepared!

Code Wave Build Log

Cassidy Williams — Sun, 18 Jan 2026 00:00:00 +0000

I made a game called Code Wave for the recently completed GitHub Game Off 2025!

I really enjoy game development, but don’t get to do it often. When I saw that the theme this year for the Game Off was WAVES, I thought that it would be fun to do something creative with it!

Before I continue, if you want to play other entries, you can see all of the submissions to the Game Off here on Itch.io.

How the game is played

Code Wave is a top-down 2D game, where the player collects letters to form words while avoiding enemies.

The player, for each level, has to collect the letters of a word. Once they get all of the letters for a given level, they are able to cross a body of water (to match the WAVES theme!) to reach the next level. The “finish line” on each level is across the water, and once they cross it, they go to the next level.

The inspiration behind this was the classic game Spelling Jungle, if you know it!

The words for all 10 levels are as follows:

AI
Git
Code
Merge
Commit
Branch
GitHub
Program
Copilot
Developer

So, as you can see, it gets a liiittttle harder with longer words at each level. The number of enemies increases at each level, too. There’s bombs that stay in one place, and then randomly moving hovercrafts.

There’s three difficulty levels that change the gameplay slightly, and how the enemies affect you:

Easy : The player can find/get letters in any order, and enemies restart the level.
Medium : The player can find/get letters in any order, but enemies restart the level and the player loses all of their collected letters.
Hard : The player has to find/get letters in the correct order of the word, and enemies restart the level and the player loses all of their letters (kind of turns it into a memory game).

The goal is to get through all 10 levels as fast as possible! It can get kind of hard depending on where the hovercrafts end up (which again, is totally random). I think my fastest time is 6m23s, if you want to try to beat that!

Technologies and tools

I didn’t have a ton of time to work on Code Wave, because when the game jam started, I was fresh off of maternity leave and had limited computer time outside of work. So, I opted for tech that I know relatively well: Phaser, and good ol’ vanilla JavaScript.

I first used Phaser when I built my game Thirteen Potions for a game jam a couple years ago (build log here), and luckily I remembered how the basics worked.

That being said, when I made Thirteen Potions, I was very limited in file size (because it was for a game jam based on tiny games, see the build log), so this time I felt VERY free about using the starter “Create Game App” tool. I used the basic “Web Bundler” option with Vite, and it scaffolded out some files for me.

Art-wise, I used Aseprite for editing pixel art, which I initially got from Kenney, and a custom (very cute) GitHub Mona character that I got from a designer at GitHub who I nerd-sniped into making it.

To make the map, I used the Tiled map editor, and imported my pixel art into it (more on that in a sec).

And finally, for the background music, it’s a song called A Heart of Pixels by Christoffer Moe Ditlevsen, which I licensed for the game! I also used some sound effects from Kenney (again), and custom made some myself just in Audacity.

Making the map

In case you haven’t used it, Tiled lets you export your maps as JSON, and lets you label tiles and layers however you’d like!

Thank goodness, I knew how to work with Tiled and the pitfalls of it after Thirteen Potions (for example, it’s much easier to have an entire layer dedicated to collisions, rather than individual tile types).

It was particularly manual to make all 10 levels (and I openly admit I thought a few times, “could AI do this?” as I had to make individual edits repeatedly, often), but I did it! Hand-crafted! It took a while to get it all right.

I had seven layers for each level:

A ground layer, for… the ground
An obstacles layer for various plants and trees and stuff that players can’t walk on
A water layer, which initially players collide with until they collect all the letters
A goal layer, which advances the player to the next level
A letter layer, for all of the letters per word
An enemy layer, for the bombs and hovercrafts
A player layer, which just has the player spawn point

My spritesheet I made (which you can see in the above screenshot in the bottom right) was a bit overkill for the game (I combined a bunch of tilesets thinking I’d have way more enemies and obstacles), but it worked well for all of the layers in a compact image.

I remade and re-saved and re-configured these maps… more times than I can remember. It was hours. It was overkill. Please admire them.

Actually coding

Okay, once I had allll of my configuration set up with Phaser’s Create Game App, all of my sprites and tiles managed, all of my music and sound effects ready, it was time to actually start building. I had a plan, and I reviewed Thirteen Potions pretty extensively, since I wanted my camera, player, and enemy movement to be mostly the same.

I used GitHub Copilot relatively heavily for some of the boilerplate, and it helped me speed up a lot so I could focus on the more fun parts of the codebase, which was great.

Breaking it down, here’s the structure of how the code was set up:

Scenes

Boot.js + Preloader.js
- Loads all 10 level maps
- Loads the sprite sheet, background music, sound effects, and background image
Game.js
- Handles difficulty configuration
- Handles sprite movement
- Includes a status UI in the top left of the current word, collected letters, and time
- Manages collisions with obstacles and water
- Initially blocks player from crossing water, but allows it after collecting all letters
- Player sprite toggles “swimming” mode when on/off water
- Manages enemy collision
- Player blinks red and respawns
- Camera logic
- Zooming in and following player
- Extra “fake” camera for the status UI (which was hacky but neat)
- Letter collection
- Checking difficulty level in case a letter isn’t eligible to be collected
- Adding the letter to the status UI
- Checks if player is on goal tile with all letters and advances to the next level
- Keyboard and mouse navigation and shortcuts

Overlay scenes

These are aptly named so I’m not going to go into them too deeply:

GameOver.js
HowToPlay.js
MainMenu.js
Pause.js

In retrospect, there’s some things I wish I cleaned up but didn’t. The overlay screens all had juuust enough repetition that I should have made just an Overlay component and reused it (that being said I did make some reusable buttons for those, so that helped). The Boot and Preloader scenes should probably be combined. The Game scene definitely should be broken up more. There’s a “virtual joystick” component that mostly works if someone is playing on mobile, but is moderately janky. I could have tightened up how I handled some of the sprite collisions.

BUT. The game works. It can use keyboard navigation or a mouse or a finger. The music can be muted. Players can pause easily. It looks dang cute. I’m gonna just live with the little wins!

Hoorah!

I didn’t expect Code Wave to win any fabulous awards (once again, you can see and play all of the submissions to the Game Off, and you should), but I had a really fun time putting it together and ultimately playing it.

If you’d like to see more of how it works, you can check out the repository, or play it again!

Do not give up your brain

Cassidy Williams — Fri, 16 Jan 2026 00:00:00 +0000

In case you missed it, I have a little AI Manifesto here on this blog. I do use AI for work, and often shill AI for work, and use it often on side projects.

That being said, I really care about using AI as a tool, rather than a replacement for my own thoughts and ideas. I think it’s very important to not default to laziness and just asking for the answer to something, especially when thinking a liiiiittle bit can get you there.

I’ve seen multiple people now who are really good at communicating online, but then when you converse with them in person, they freeze up, and it turns out it’s because they’ve been letting ChatGPT (or whatever they’re using) come up with responses for them in chats and emails. I know people who are afraid to write a professional email themselves now and they run it through their AI tool several times before shipping it. This type of dependence is the world we’re careening towards as a society at this rate, and it’s not a good thing.

It’s really tempting to say that you’re just “using the resources you have” when you use a simple query here and there, but your brain is the best resource you’ll have for the rest of your life, and you should keep it sharp.

Anyway, I might be saying the obvious, so let me leave you with this quote:

“Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them.”

Frank Herbert, Dune

A career chat with students in the age of AI

Cassidy Williams — Sat, 10 Jan 2026 00:00:00 +0000

I gave a short talk today to some students at Haverford College and Bryn Mawr College about AI, a career in tech, networking, and getting jobs in general!

My friends Lilly and Johnson from FSH Tech are teaching a J-Term course at these schools to help students learn about agentic AI, production deployment, and building real-world tools. It’s a cool short course, and the students had a lot of questions.

In general, I think students today are worried about the job market, and I can’t blame them. I was asked if it’s harder or easier to get a job now than it was when I entered the industry, and… it’s both? I think it’s easier because there’s a lot more resources out there now that are more easily accessible than ever for the job hunt… but also the economy is weird, it’s hard to find entry-level roles, and the AI spam on both sides of the job application table is a huge mess.

The point I really wanted to drive home in this talk, and one that I think is important for everyone (not just students), is that human connection now is more important than ever. Referrals tell employers that you’re a real human, not just a bot mass-applying to roles. It’s a really powerful signal for them, even if you haven’t worked super closely with the person who is referring you.

My favorite book on this subject is Build Your Dream Network by J. Kelly Hoey. Getting those human connections can start with something as simple as a follow-up email, and can really blossom into a great relationship.

Anyway, it was good chatting to the students, I had a great time! And… now I gotta reply to the ones that were really listening and sent me follow-ups directly afterwards, ha. The kids are all right!

Making the "End of Year Developer" nature documentary

Cassidy Williams — Tue, 23 Dec 2025 00:00:00 +0000

It’s Blogvent, day 23, where I blog daily in December!

This month I went to the GitHub office in San Francisco and met up with some coworkers and put together some videos for work.

While working on other content, we got a lot of b-roll of me around the office just like… walking, typing, and being dumb. So, when I got home and saw said b-roll without audio, and realized… this could be a meme.

Because the videos were mostly me looking like I was “working” (in addition to a bunch of clips of me just checking out office props), the theme popped into my head pretty quickly: for this time of year, a whole lot of people are not actually working, but rather looking busy and just trying to get to their vacations.

I wrote up a script and had my coworker Martin read it, plopped a bunch of clips together, and blammo, we had a joking nature documentary in less than an hour.

Check it out, and enjoy!

CSS for markdown blockquote attribution

Cassidy Williams — Mon, 22 Dec 2025 00:00:00 +0000

It’s Blogvent, day 22 where I blog daily in December!

I write my blog posts in markdown, and I write quotes like so:

> I miscounted the men!
>
> - Gavin Volure

This results in the following:

I miscounted the men!

Gavin Volure

It always bugged me how the HTML generated a <ul> for the quote author, because the default bullet point is the disc (•) and looked like a stray list out of nowhere.

But, I didn’t want to un-style lists entirely, in case something I quoted had a list in it.

Now, the way my blog is styled, I target the author by selecting the last <ul> in the generated <blockquote>, and going from there!

Here’s the code and a demo:

So now, I can have quotes like what you saw above, but also quotes like this:

Basketballs

Hula hoops

Rollercoaster loop-the-loops

You just heard the Woggels sing a very silly list of things! Woggel power!

The Woggels

(this post looks better on my blog)

Hope this was helpful for you!

I like when apps are "finished"

Cassidy Williams — Sun, 21 Dec 2025 00:00:00 +0000

It’s Blogvent, day 21, where I blog daily in December!

I saw a post on Mastodon recently:

We need to normalize declaring software as finished. Not everything needs continuous updates to function. In fact, a minority of software needs this. Most software works as it is written. The code does not run out of date. I want more projects that are actually just finished, without the need to be continuously mutated and complexified ad infinitum.

Millie

I really heartily agree with this. I have a handful of apps I’ve made personally that I genuinely just consider “done”, like:

The problem is, because they’re open source, people often look at the repository and see that the last code commit was, say, 3 (or 4 or 7 or 9) years ago, or that there’s some unanswered feature requests, and they’re like “ah, this software is unmaintained, it’s dead.” But they’re not! They just do their one job, well, and don’t need anything else!

I feel like a lot of people in tech claim the famous Leonardo da Vinci quote, “Art is never finished, only abandoned,” when it comes to software, but… sometimes the app just does the job it’s supposed to do. Most times, software is not art, layered with meaning, rather it’s just a utility that does a task.

I don’t really know what the solution is, here. More people finishing apps? Accepting that our work is not necessarily art? Less subscriptions? Wait, yeah, probably less subscriptions.

Anyway. Thought of the day. Try my apps. Bye.

Configure your repositories with .github

Cassidy Williams — Fri, 19 Dec 2025 00:00:00 +0000

It’s Blogvent, day 19, where I blog daily in December!

If you’ve bounced around GitHub before, it’s likely you’ve seen a .github/ folder at the top-level of a repository. You might have even seen a .github repository in some organizations!

This is incredibly hard to look up online, as you can imagine. It’s even admittedly a bit challenging to find out all that it can do in the documentation itself because of how it’s named. So, look no further, here’s all you can do (currently!) with .github!

`.github` everywhere

Long story short: if you see .github, it’s a magical thing that configures GitHub for you.

In a repository, the .github folder is a special directory used to store community health files, repository settings, automation workflows, and GitHub Copilot configuration files. GitHub automatically recognizes and uses specific files within this folder to customize the repository experience for contributors and maintainers!

In an organization, the .github repository is for “default community health files” for the repositories in your org. That means if you have an organization with like… 10 repositories, they will all default to the configurations in the .github repository unless they’re overridden in the individual repos.

I’m going to focus on individual repositories with the .github folder for the rest of this post, but here’s the documentation for the .github repository options for you, and here’s a good example of what that repo can look like!

`.github` in your repository

There’s some convenient things you can put in this folder to get things configured to your liking. As of now, December 2025, here’s what you can do!

(if something in this list ends with .md, that means it’s a markdown file, if it ends with .yml it’s a YAML file, and if it ends with /, that means it’s a folder for markdown or YAML files)

Issue and pull request templates

ISSUE_TEMPLATE/: Place YAML or Markdown issue templates here. You can have multiple templates for different issue types.
- Examples: .github/ISSUE_TEMPLATE/bug_report.md or .github/ISSUE_TEMPLATE/feature_request.md
PULL_REQUEST_TEMPLATE.md or PULL_REQUEST_TEMPLATE/: Template(s) that pre-fill descriptions when someone opens a new PR.

GitHub Actions/workflows

workflows/: For YAML files that define GitHub Actions workflows.
- Example: .github/workflows/ci.yml

You can use these to automate CI/CD, linting, deployments, tests, and a bunch of other nice things. Docs here are handy, and here’s an example I have in one of my repos.

Community Health Files

These files help set standards and support for your repo:

CODE_OF_CONDUCT.md: Set expectations for community behavior
CONTRIBUTING.md: Guide for people who want to contribute to the project
FUNDING.yml: Show ways to financially support the project (example)
SECURITY.md: How to report security vulnerabilities
SUPPORT.md: Let users know where to ask questions

As a note, if you have these in your individual repository, they will override whatever is in the .github repository in your organization, if that’s configured.

You can put some of these at the root of your repository for easy visibility (like CONTRIBUTING.md), but either way, GitHub will surface those contents in the repo sidebar in a nice UI for folks to find.

Configuration files

These configure features or bots for you repo:

dependabot.yml: Configures Dependabot to keep your dependencies up-to-date
CODEOWNERS: Define who owns certain files or paths. When someone opens a PR that touches those files, GitHub will automatically request a review from the listed people.

GitHub Copilot custom instructions and agents

GitHub Copilot’s configuration settings are newest in the list so far, and help with code completion and guardrails for AI tools working in your repos.

copilot-instructions.md: Instructions here are automatically included in all Copilot requests for your repo across supported IDEs and platforms. This sets your coding standards, preferred libraries, name conventions, etc. Docs here.
instructions/: Every file in here should be named *.instructions.md (replace * with the file name). This is for storing multiple, file-specific, or directory-specific instruction files. Each file in here can describe rules for a particular feature, language, file type, or folder. Docs here for what your syntax should look like, and here’s some good examples.
agents/: Similar to .instructions, every file in here should be named *.agent.md. This is for configuring the Github Copilot coding agent to do specific things. Here’s a repo of a bunch of example custom agents you can use.
- I literally learned while writing this post that you can make a .github-private repository in your organization specifically for configuring default custom agents. Who knew? Don’t tell my boss. Anyway, here’s a template repo for that and docs about these in general.
prompts/: Also similar to .instructions! Every file should be named *.prompt.md. This lets you add reusable commands to GitHub Copilot. Docs here and handy examples here.

Oh my word stop

Okay I think that’s it. There’s so many things you can do. I’m exhausted. There’s actually more types of configurations you can add to the .github folder depending on the apps and Actions you have configured in your repository (like this one for labeling PRs lets you add labeler.yml, for example). But I’ll let you explore those on your own.

I hope this was handy for you!