billing VS checkout

Yes. Go to Settings | Billing. Scroll down to Add-ons, and you can change from yearly to monthly or the reverse there.

If you're not going to pay for it and you're on the preview, the first wave of charges are about to go out. So make sure you do want to pay or cancel: https://github.com/settings/billing

Link to plan comparison: https://github.com/settings/billing/plans

I've been testing in the last hour or so, and so far I don't see the Github LFS bandwidth limit moving under https://github.com/settings/billing. I just want to make sure I don't run into bad surprises. So I'd have three questions :

GitHub is free for anything you'd need to do for CS50

An easier example would be the Github Billing's Usage Reports. All of the metrics they have there report the usage, and if you were to write some kind of feature in your billing app that works like this, using Cashier Register, you'd increment the amount of usage for any of your features, and later on you can retrieve them or check when the limit was reached to ping your users, per se.

Chris, that looks to do the job. You're triggering the workflow run when there is a change in the podcast_audio folder pushed to the master branch. You've also enabled the lfs flag, so that the runner will go ahead and pull down the binary files as needed. Why is that a naïve implementation? I'm glad you asked! As a GitHub user you have a storage and bandwidth quota for Git LFS data. You can find this in the billing section of your GitHub account.

checkout

To checkout the merged commit with actions/checkout on pull_request_target event, you need to get the pull request by GitHub API and set the merge commit hash to actions/checkout input ref.

If you re-run GHA after master changes, CI is testing over different code.

You can [disable](https://github.com/actions/checkout#checkout-pull-request-head-commit-instead-of-merge-commit) on the checkout action:

```

There was an outage yesterday too when the GitHub action “checkout@v3” broke when they released “checkout@v4”

Yes, they broke the ability for GitHub CI to checkout repos…

https://github.com/actions/checkout/issues/1448

The first two steps are setting up the job's environment. The checkout action will checkout out the repository at the triggering ref. The setup-python action will setup the desired Python runtime. My package supports Python 3.9+ so I'm targeting the minimum version for my build environments.

These first few steps demonstrate how you can run commands like npm install or import other workflows such as how it uses the actions/checkout to copy the contents of the repository into a working directory on the runner host. Read Reusable workflows for more about the syntax for referencing them.

Check out the repo: We will use the actions/checkout action to checkout the repository.

Take a look at the checkout action usage here https://github.com/actions/checkout

Then, we have two important initial steps to define. The first one is an official GitHub Action used to check-out a repository so a workflow can access it. The second one it's pretty more complex but, briefly, downloads and set up a requested version of Java.