Replies: 1 comment
-
GitHub had a beta feature "required workflows", which allowed easily reusing workflows across repos. Sadly it only worked for pull requests and no other triggers from my recollection... and they also discontinued it. https://docs.github.com/en/enterprise-server@3.11/actions/sharing-automations/required-workflows With 300+ repos, it would probably be better to run It first collects the repos in the org, then runs a strategy matrix to check all the stale issues and PRs. To me this has a few advantages over copying the workflow to every repo.
If you don't want to use the fork/pr branch of actions/stale that allows passing in a different user and repo, then you could replicate your workflow(s) to your repos. I use this to replicate some common workflows, like linters and whatnot. https://github.com/derberg/manage-files-in-multiple-repositories I agree your feature request is a nice idea. I doubt GitHub will ever see this though, so the above are just workarounds for you to consider. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Hello
I am working for a company and we have around +300 repositories. Recently we wanted to introduce actions/stale but on all our repositories. Github does not provide an easy way to do it.
It was mentioned in Github Universe 2022 but it requires IaC and Pulumi.
Before actions/stale it was a probot. The "cleanest" way was to create a file in
https://github.com/my-org/.github/.github/reuse.yml
, then from other repositories, use the _extends attributes, to import the yml.Now with the new
actions/stale
you have a to do more work, and useuses:
[doc].Github should leverage
.github
root repo where you could define an action that will be run on each repositories.There is other proposal at the moment:
Beta Was this translation helpful? Give feedback.
All reactions