FilesExpand file tree

main

/

autoclose_comment.yml

Copy path

View runs

Blame

More file actions

Blame

More file actions

Latest commit

 

History

History

History

80 lines (62 loc) · 3.17 KB

main

/

autoclose_comment.yml

Copy path

Top

File metadata and controls

• Code
• Blame

80 lines (62 loc) · 3.17 KB

Raw

Copy raw file

Download raw file

Open symbols panel

Edit and raw actions

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

---

name: autoclose comment

# Post comment on PRs when labeled with "status: autoclose candidate".

# Based on scikit-learn's autoclose bot at

# https://github.com/scikit-learn/scikit-learn/blob/main/.github/workflows/autoclose-comment.yml

permissions:

contents: read

pull-requests: write

on:

pull_request_target:

types:

- labeled

env:

GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

GH_REPO: ${{ github.repository }}

PULL_REQUEST_NUMBER: ${{ github.event.pull_request.number }}

jobs:

post_comment:

name: post_comment

if: "${{ contains(github.event.label.name, 'status: autoclose candidate') }}"

runs-on: ubuntu-latest

steps:

- name: comment on potential autoclose

run: |

gh api \

--method POST \

-H "Accept: application/vnd.github+json" \

-H "X-GitHub-Api-Version: 2022-11-28" \

/repos/$GH_REPO/issues/$PULL_REQUEST_NUMBER/comments \

-f "body=$BODY"

env:

BODY: >

⏰ This pull request might be automatically closed in two weeks from now.

Thank you for your contribution to Matplotlib and for the effort you

have put into this PR. This pull request does not yet meet the

quality and clarity standards needed for an effective review.

Project maintainers have limited time for code reviews, and our goal

is to prioritize well-prepared contributions to keep Matplotlib

maintainable.

Matplotlib maintainers cannot provide one-to-one guidance on this PR.

However, if you ask focused, well-researched questions, a community

member may be willing to help. 💬

To increase the chance of a productive review:

- Use [the template provided in the PR

description](https://github.com/matplotlib/matplotlib/blob/main/.github/PULL_REQUEST_TEMPLATE.md)

and fill it out as completely as possible, especially the summary and AI Disclosure sections.

- Make sure your PR conforms to our [PR

checklist](https://matplotlib.org/devdocs/devel/pr_guide.html#summary-for-pull-request-authors).

As the author, you are responsible for driving this PR, which entails doing

necessary background research as well as presenting its context and your

thought process. If you are a new contributor, or do not know how to

fulfill these requirements, we recommend that you familiarize

yourself with Matplotlib's

[development conventions](https://matplotlib.org/devdocs/devel/index.html)

or engage with the community via our [Discourse](https://discourse.matplotlib.org/)

or one of our [meetings](https://scientific-python.org/calendars/)

before submitting code.

If you substantially improve this PR within two weeks, leave a comment

and a team member may remove the `status: autoclose candidate` label and the

PR stays open. Cosmetic changes or incomplete fixes will not be

sufficient. Maintainers will assess improvements on their own

schedule. Please do not ping (`@`) maintainers.