Open markhalliwell opened 10 years ago
Wondering whether the github/release/build code is actually that specific to dreditor.org to require a dreditor_
prefix…?
Yes... and no. Some of it is very Dreditor specific. I don't think we'll really know until some of this stuff is flushed out more. I think using the dreditor_
prefix is fine until we're ready to abstract what we can and either 1) move upstream to existing contrib or 2) create a new contrib module(s)
Currently the
dreditor_org
module houses too much functionality and it's easy to get lost and understand what does what.Recommending that we rename from
dreditor_org
todreditor
and have the following sub-modules:dreditor_build
- automated buildsdreditor_gh
ordreditor_github
? - GitHub API / webhook eventsdreditor_release
- release management (need to create)More to come?