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

Bulldozer doesn't trigger when use the shared configuration from .github repository #314

Open
ajayshrestha005 opened this issue May 26, 2022 · 1 comment

Comments

@ajayshrestha005
Copy link

ajayshrestha005 commented May 26, 2022

We want to set the default bulldozer config for all the repos.
We followed the wiki here. If the file does not exist in the repository, bulldozer tries to load a shared bulldozer.yml file at the root of the .github repository in the same organization
But bulldozer doesn't trigger when moving the config to the .github repo. Does it require any extra permissions or settings to use the shared config?

@ajayshrestha005 ajayshrestha005 changed the title Doesm Bulldozer doesn't trigger when use the shared configuration from .github repository May 26, 2022
@bluekeyes
Copy link
Member

The .github repository must be public, but otherwise, I don't believe there are any extra settings or permissions required.

If you have access to the server configuration and logs, try to temporarily enable debug logging. Bulldozer logs messages about the files it tries when loading configuration that may help explain what is happening.

For this particular problem, look for messages that start with Trying default configuration or Found default configuration. This might show that Bulldozer is looking for a different file than the one you added to your .github repository or you might see an error after the "Trying..." message.

If you're unsure how to interpret the logs and are able to share some in a redacted form, feel free to attach a sample here and I can take a look.

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

No branches or pull requests

2 participants