Message 400038 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	rmast
Recipients	pablogsal, rmast, vstinner, zach.ware
Date	2021-08-21.17:27:15
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1629566835.69.0.665049200132.issue44972@roundup.psfhosted.org>
In-reply-to

Content
* The main constraint is that the the `workflow_dispatch` trigger must be in the GHA workflow yaml files for the branch to be selectable as a target on the Actions tab when manually triggering a workflow. Having the change made to the main branch and backported would mean that new or rebased branches would have the trigger needed for manually running the CI job in forks.

* The main constraint is that the the `workflow_dispatch` trigger must be in the GHA workflow yaml files for the branch to be selectable as a target on the Actions tab when manually triggering a workflow. Having the change made to the main branch and backported would mean that new or rebased branches would have the trigger needed for manually running the CI job in forks.

History
Date	User	Action	Args
2021-08-21 17:27:15	rmast	set	recipients: + rmast, vstinner, zach.ware, pablogsal
2021-08-21 17:27:15	rmast	set	messageid: <1629566835.69.0.665049200132.issue44972@roundup.psfhosted.org>
2021-08-21 17:27:15	rmast	link	issue44972 messages
2021-08-21 17:27:15	rmast	create