CI/CD DiscussionsArchive: https://archive.sweetops.com/release-engineering/ 2021-10-06 Zach05:38:55 PMhttps://github.blog/changelog/2021-10-05-github-actions-dry-your-github-actions-configuration-by-reusing-workflows/GitHub Actions: DRY your GitHub Actions configuration by reusing workflows | GitHub ChangelogGitHub Actions: DRY your GitHub Actions configuration by reusing workflows1 Zach09:34:07 PMugh. testing this out and the ‘reusable workflow’ must be in a public repository Erik Osterman (Cloud Posse)09:34:36 PMsame with private actions Zach09:34:43 PMthats a real bummer Erik Osterman (Cloud Posse)09:34:48 PMbut with private actions, there’s a workaround - you can as a step clone the private repo Erik Osterman (Cloud Posse)09:34:54 PMthen call uses on the local checkout Erik Osterman (Cloud Posse)09:34:57 PMcan. you try that? Zach09:35:04 PMI don’t understand githubs ‘thing’ with public repos Erik Osterman (Cloud Posse)09:35:39 PMya, so the whole community that pays them is snubbed from using the best features Zach09:36:16 PMNot sure if that would work in this case since the call_workflow requires calling a repository with a branch version Erik Osterman (Cloud Posse)09:38:53 PM Zach09:41:45 PMhm ok I’ll try that later Zach09:42:02 PMfor now I will write them a sternly worded letter of complaint1 Scott Mathson10:52:02 PMHah! I had the same reaction to this feature. The kinds of things I’d want to DRY up have absolutely no utility to the the wider community. Seems like a silly limitation Zach12:27:37 PMGithub support got back to me and said that yes, the use of this feature for private repos is GitHub Enterprise only.2 2021-10-07