-
Notifications
You must be signed in to change notification settings - Fork 66
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
Allow automatic start of builds after pull request has been opened #11
Comments
Hey Michael, thanks for filing the first Buildasaur issue! :) Yeah making the lttm barrier optional makes sense, I'll look into allowing for customization of the bot enabled state from the UI or from a config file. Let me know if you have any more issues/ideas! |
Not our use case but others may benifit from the possibility to set this individually per repository (see my other issue about multi repo support ;). |
Yeah it would definitely be configurable on a per-Syncer basis. |
Hey Michael, optional lttm is in, checkout the latest release: https://github.com/czechboy0/Buildasaur/releases/tag/v0.2.5 You should now be able to just download the .app from the release page and use that. In the UI is now a switch where you can disable the "lttm" barrier - thanks for that name, by the way :) Let me know if this works for your team and keep the ideas coming! |
The switch to disable the lttm barrier works very good. Regarding ideas... well besides the mutli repo support we have everything we need right now. |
Hi, Honza.
You probably already anticipated it, so here's the request for the possibility to remove the "lttm barrier". :)
We're using your awesome tool for our pull requests which go to private repositories with only trusted users to access them.
Forgetting to type lttm leads to no hints at all of any failed tests.
Right now we simply return isEnabled: true from isBotEnabled() in our own build of Buildasaur but it would be nice if you could incorporate that as an option so we won't have to modify your code after each update.
The text was updated successfully, but these errors were encountered: