[Django] #37046: PR Quality check may need to account for ready for check-in
3 views
Skip to first unread message
Django
unread,
7:18 AM (15 hours ago) 7:18 AM
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django-...@googlegroups.com
#37046: PR Quality check may need to account for ready for check-in
--------------------------------+-----------------------------------------
Reporter: Tim Schilling | Type: Bug
Status: new | Component: Uncategorized
Version: dev | Severity: Normal
Keywords: GitHub Actions | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+-----------------------------------------
This is in reference to
[https://github.com/django/django/pull/21041#issuecomment-4272913765 PR
21041]
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django-...@googlegroups.com
#37046: PR Quality check may need to account for ready for check-in
---------------------------------+------------------------------------
Reporter: Tim Schilling | Owner: (none)
Type: Bug | Status: new
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to django-...@googlegroups.com
#37046: PR Quality check may need to account for ready for check-in
-------------------------------------+-------------------------------------
Reporter: Tim Schilling | Owner: Varun
| Kasyap Pentamaraju
Type: Bug | Status: assigned
Component: Core (Other) | Version: dev
Severity: Release blocker | Resolution:
Keywords: GitHub Actions | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
If not self-evident, there are a couple places where more actions happen
after marking a ticket RFC that will re-trigger the action:
- merger wants to trigger more tests, so they apply the Selenium or
coverage labels
- author pushes again to add themselves to AUTHORS
- merger force-pushes to edit commit messages etc.
--
Ticket URL: <https://code.djangoproject.com/ticket/37046#comment:11>