Mariatta
Mariatta
Not all bugs need to be backported all the way to the earliest maintained version. I know from recent examples where some docs/bug fixes appearing in 3.8 but not 3.7,...
This is great! Thanks @ncoghlan and @msapiro!
I noticed the footer of core-workflow mailinglist email is broken: ``` core-workflow mailing list -- [email protected] To unsubscribe send an email to [email protected] %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s ``` See https://mail.python.org/mm3/archives/list/[email protected]/message/J6B443H7KMTI2DSJTMHVG3IUYHN5IESD/ for example
Thanks for the quick fix! 😄
@ncoghlan where should the above checklist be documented? I want to request [docs mailing list](https://mail.python.org/mailman/listinfo/docs) be updated too :) > Send an email to the affected list first to say...
+1 for adding it as part of core-workflow, but I suggest something like "docs" instead of "misc" so the contents of that directory don't become too random.
> After your step 3 `git rebase upstream/master` I had some error during the `git push origin` I think you need to do `git push origin --force` here to avoid...
Ok I will need to adjust miss-islington to understand that some tests can be `skipped`. Currently it expects all `success` status.
Let's try doing this as a GH Action instead of in bedevere. I think this would require checking the PR's "mergeable" status on the "synchronized" or "push" event.
Before you enable this I may need to make changes to miss-islington. It has logic for deleting branch.