Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

Fair enough, I'm just a sucker for generic solutions, but you're right, we probably wouldn't want states like those to be set manually.
I've been looking through the tests but can't seem to find the ones for that part of the api, I feel like they should be in here: https://github.com/apache/airflow/blob/main/airflow/api/common/mark_tasks.py but I think I'm missing something.

@potiuk, do you have any idea why some of the CI checks fail without being executed? Is it related to the changes made yesterday, or is it just a temporary problem?

Likely intermittent. Looks like temporary Github Issue. Easiest is to rebase it or close/reopen such PR.

It still has the same problem after rebasing and closing/reopening it.
I wonder if it's something related to a maintainer commit in no-maintainer PR 🤔

@potiuk I think it's indeed related, the job has self-hosted label, but it was blocked by the security policy. wdyt?
Here is the debugging log for one of the failed jobs:

Requested labels: self-hosted
Job defined at: apache/airflow/.github/workflows/ci.yml@refs/pull/31421/merge
Waiting for a runner to pick up this job...
Job is about to start running on the runner: Airflow Runner 62 (organization)
Error: Running job on worker Airflow Runner 62 disallowed by security policy
##[debug]Finishing: Push Early Image Cache (linux/amd64)

@JoranDox The PR is almost ready, can you fix the CI so we can merge it ?

@JoranDox The PR is almost ready, can you fix the CI so we can merge it ?

Apologies, I thought the CI had issues unrelated to my code and was kind of ignoring the mailthread, thanks for pinging me! I forgot to import TaskInstanceState, but that should be all I think.

Why does black complain about files I didn't even edit? I can't even find them...

No idea what those sql failing tests have to do with my PR..

e.g. the fact that these two strings are not the same doesn't seem quite relevant to allowing the "skipped" state?

E - http://localhost:8080/ javascript:alert(1)
E + /home

Make sure to rebase your branch, you are 25 commits behind, there's been work on those, and fix might already be in main.

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.