toan added a comment.
To some extent this could probably be circumvented by using a dedicated branch with commits that contain this info and could be passed as the "ref". Example: 1. Our CI pushes a commit to some branch on wikibase-release-pipeline which contains the information on what is supposed to run. 2. Our CI triggers a workflow and setting the ref <https://github.com/wmde/wikibase-release-pipeline/pull/184/files#diff-7841fe6616480dd42c35946f63a9fb082a33072222313e32026f66888f40a460R15> to this commit hash TASK DETAIL https://phabricator.wikimedia.org/T282479 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: toan Cc: Jakob_WMDE, hoo, Tarrow, toan, WMDE-leszek, Aklapper, Invadibot, maantietaja, Akuckartz, Nandana, Lahi, Gq86, GoranSMilovanovic, QZanden, LawExplorer, _jensen, rosalieper, Scott_WUaS, Jonas, Wikidata-bugs, aude, Lydia_Pintscher, Addshore, Mbch331
_______________________________________________ Wikidata-bugs mailing list -- wikidata-bugs@lists.wikimedia.org To unsubscribe send an email to wikidata-bugs-le...@lists.wikimedia.org
