-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
Consider supporting .github directory for DEREK.yaml #38
Comments
Turns out at least two other bots use |
I see the point about projects collecting files in their root such as .travis.yml, Dockerfile and the likes. At the moment convention over configuration means the project's code-base can remain simple. There are lots of different integrations which have a file in the root of a repo - this does also give better visibility to the project which is provided for free. Example of the Docker project and some of the bots they use - https://github.com/moby/moby While it is a valid point, I don't see a pressing need for this change. Thanks for logging the suggestion - I'll mark it for revisiting at a later date. |
GitHub supports a
.github
directory to reduce the amount of clutter in a projects root directory for issue and contribution docs. It would be nice if DEREK.yml could also be placed there.A potential downside is that GitHub owns the
.github
namespace. Alternately a directory named.automation
would be nice for this type of configuration data, but pointless if only Derek uses it.The text was updated successfully, but these errors were encountered: