bedevere - GitLite

KO | EN

gitlite — search

#nextjs #rust #redis #json #automation #github #developer-tools #linux #graphql #sql

bedevere

(★ 140)

A bot to help identify missing information for CPython pull requests

File Explorer

ZIP Download

- - ci.yml
  - lint.yml
- codecov.yml
- dependabot.yml
- zizmor.yml
- __init__.py
- __main__.py
- backport.py
- close_pr.py
- filepaths.py
- gh_issue.py
- news.py
- prtype.py
- stage.py
- util.py
- __init__.py
- test___main__.py
- test_backport.py
- test_close_pr.py
- test_filepaths.py
- test_gh_issue.py
- test_news.py
- test_prtype.py
- test_stage.py
- test_util.py
.coveragerc
.git-blame-ignore-revs
.gitignore
.pre-commit-config.yaml
CONTRIBUTING.rst
dev-requirements.txt
LICENSE
Procfile
pytest.ini
README.md
requirements.txt
runtime.txt
tox.ini

# Use via CDN

jsDelivr

jsDelivr serves any public GitHub repository as a CDN with zero setup. Pick a version and a file to get a ready-to-paste link and snippet.

Version

File

Link

Example

# Project Badges

Build Status Visit
codecov Visit

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

This bot is meant to help identify issues with a CPython pull request.

## What the bot does:
- ### Identifies missing GitHub issue numbers in the title
If no GitHub issue number is found the status fails and the
"Details" link points to the relevant
[section of the devguide](https://devguide.python.org/getting-started/pull-request-lifecycle.html#submitting).
- ### Links to GitHub issues
If an issue number is found then the "Details" link points to the relevant issue
itself, making it easier to navigate from PR to issue.
- ### Identifies missing news entry
If no `Misc/NEWS.d` entry is found or the news entry is formatted incorrectly
and the issue doesn't have the `skip-news` label, the status fails and a relevant
description label is added to it.
- ### Closes invalid PRs
Closes PRs that try to merge a maintenance branch into the main branch, adds
`invalid` label, and posts a relevant message.
- ### Labels PRs for docs
Labels PRs for documentation as `docs`
- ### Copies main labels to backport
Copies labels from main PRs to backport PRs

## PR State Machine

This diagram represents the state machine for pull requests, and the labels
applied by Bedevere.

The colors represent who can make a state change or who is currently
blocking the PR from moving forward:
* Yellow: the PR creator
* Green: core developers
* Blue: anyone

```mermaid
flowchart TD
    A([Published PR]):::creator
    A_draft([New Draft PR]):::creator
    A_draft -- publish draft by contributor --> A:::creator
    A -- by contributor --> B[Awaiting review]:::anyone
    A -- by core dev --> C[Awaiting core review]:::coredev
    B & C -- new review by<br>another contributor --> C
    C & B & E  -- new core review<br>requests changes --> D[Awaiting changes]:::creator
    D -- changes by contributor --> E[Awaiting change review]:::coredev
    C & E & B -- new core review<br>approves ---> F[Awaiting merge]:::coredev
    G[When a review is dismissed<br>the highest remaining state is restored<br>based on the remaining reviews]
classDef creator stroke:#CC0;
classDef anyone stroke:#00C;
classDef coredev stroke:#0C0;
classDef triager stroke:#C0C;
linkStyle 0,1,8 stroke:#CC0,color:auto;
linkStyle 3,4 stroke:#00C,color:auto;
linkStyle 2,5,6,7,9,10,11 stroke:#0C0,color:auto;
```

## *Aside*: where does the name come from?
Since this bot is about identifying pull requests that need changes,
it seemed fitting to name it after Sir Bedevere who knew
[how to identify a witch](https://youtu.be/yp_l5ntikaU).