-
Notifications
You must be signed in to change notification settings - Fork 428
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
Issue when share workflow within organization #123
Comments
Hello @Jasstkn !
According to the documentation, your configuration file has to be in the same repository as caller workflow. Alternatively, you can clone the repository with the called workflow using the checkout action: - uses: actions/checkout@v3
with:
repository: 'Repository name with owner. For example, actions/checkout' Please see the GitHub documentation for more examples. |
I’m closing the issue. Please let us know if you have any questions. |
Hi @MaksimZhukov I have this same issue and I am confused by this solution you propose:
It appears this action it hard-coded to make a request to the caller repo to get the labeler configuration. How does checking out the called repo (where my shared configuration lives) solve this? |
@jtmullen just FYI, /~https://github.com/actions/labeler/releases/tag/v4.3.0 / #394 has added support for Can see an example of how I'm accomplishing the same here ( |
Hello
|
Configuration file for labeler can't be copied if you use shared workflow within the organization.
Is there any way to put configuration inside the workflow?
The text was updated successfully, but these errors were encountered: