Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support central location for labels #9

Open
ssbarnea opened this issue Oct 25, 2019 · 4 comments · May be fixed by #125
Open

Support central location for labels #9

ssbarnea opened this issue Oct 25, 2019 · 4 comments · May be fixed by #125
Assignees

Comments

@ssbarnea
Copy link

Instead of having to store labels inside each repository, it would be great if we can use a URL to point it to a centralized location where these could be loaded from.

@crazy-max
Copy link
Owner

@ssbarnea Nice idea, could be done with #3

@crazy-max
Copy link
Owner

@ssbarnea But since the file would no longer be in the repository, there would be no way to trigger the build. This is therefore not feasible until GitHub has introduced the addition of custom triggers or manual build triggering.

@jetersen
Copy link

jetersen commented Jan 4, 2021

Wouldn't a github action with cron expression / manual dispatch suffice?

inside the org's .github repo one could create a repository dispatch job for all the repos using the central labels with the help of this action https://github.com/marketplace/actions/repository-dispatch

@jetersen jetersen linked a pull request Jan 8, 2021 that will close this issue
@kdeldycke
Copy link

FYI, remote label definitions are supported by julb/action-manage-label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants