Management Tasks - tiangolo's boring personal website

These are the tasks that can be performed to manage the repositories in the FastAPI organization in GitHub.
This section is useful only to a handful of people, team members with permissions to manage the repositories in the FastAPI organization. You can probably skip it. 😉
...so, you are a member of the FastAPI team? Wow, you are so cool! 😎
There are some tasks that only you (as part of the team) can perform. 🙌
First of all, be nice. 😊
You probably are super nice if you were added to the team, but it's worth mentioning it. 🤓
When things are difficult, here are some guidelines.
Try to find the good side. In general, if people are not being unfriendly, try to thank their effort and interest, even if you disagree with the main subject (discussion, PR), just thank them for being interested in the project, or for having dedicated some time to try to do something.
It's difficult to convey emotion in text, use emojis to help. 😅
In discussions and PRs, in many cases, people bring their frustration and show it without filter, in many cases exaggerating, complaining, being entitled, etc. That's really not nice, and when it happens, it lowers our priority to solve their problems. But still, try to breath, and be gentle with your answers.
Try to avoid using bitter sarcasm or potentially passive-aggressive comments. If something is wrong, it's better to be direct (try to be gentle) than sarcastic.
Try to be as specific and objective as possible, avoid generalizations.
For conversations that are more difficult, for example to reject a PR, you can ask me (@tiangolo) to handle it directly.
Once the PR is merged, a GitHub Action (latest-changes) will use the PR title to update the latest changes automatically.
So, having a nice PR title will not only look nice in GitHub, but also in the release notes. 📝
The same GitHub Action latest-changes uses one label in the PR to decide the section in the release notes to put this PR in.
Make sure you use a supported label from the latest-changes list of labels:
Some tools like Dependabot, will add some labels, like dependencies, but have in mind that this label is not used by the latest-changes GitHub Action, so it won't be used in the release notes. Please make sure one of the labels above is added.
If a PR doesn't explain what it does or why, if it seems like it could be useful, ask for more information. Otherwise, feel free to close it.
If a PR seems to be spam, meaningless, only to change statistics (to appear as "contributor") or similar, you can simply mark it as invalid, and it will be automatically closed.
If a PR seems to be AI generated, and seems like reviewing it would take more time from you than the time it took to write the prompt, mark it as maybe-ai, and it will be automatically closed.
A PR should have a specific use case that it is solving.
If the PR is for a feature, it should have docs.
Dependabot will create PRs to update dependencies for several things, and those PRs all look similar, but some are way more delicate than others.
When a question in GitHub Discussions has been answered, mark the answer by clicking "Mark as answer".
You can filter discussions by Questions that are Unanswered.
There are some additional tasks specific to the FastAPI repo.
Translations for the FastAPI docs are generated automatically with LLMs and scripts.
There's one GitHub Action that can be manually run to add or update translations for a language: translate.yml.
For these language translation PRs, confirm that:
For PRs that update language-specific LLM prompts, confirm that:
If the PR meets the above conditions, you can merge it. 😎
Every month, a GitHub Action updates the FastAPI People data. Those PRs look like this one: 👥 Update FastAPI People.
If the tests are passing, you can merge it right away.