Closed pjcozzi closed 7 years ago
It is, currently.
Were you thinking a variable in the code? Or an environment-specific config variable?
This has a config JSON where I set all my project-specific settings, right? I would expect this to be there so I can tweak everything in one place.
Gotcha
@omh1280 as previously discussed in the initial pull request, each repository should have a signature
option that can be modified for each repository, so not just a name, but the entire last line.
What about hard-coded links like to the pull request guidelines? Right now it's split into multiple messages.
Should each be configurable?
Or maybe one signature
if Third-party files change, and one if CHANGES.md
does
What about hard-coded links like to the pull request guidelines? Right now it's split into multiple messages.
Should each be configurable?
Ultimately, we are going to have to allow for as much configuration as needed to get the job done. This can be tricky with generated content because you essentially need some sort of templating system to do it right (which is why I haven't worried about it yet). Let's get the stale PR bumper and CLA stuff done first before we worry about this.
I was thinking the same.
If there is a good templating library you use, I'd be happy using it in a pinch. It would definitely make the code cleaner.
handlebars is what we have used in the past, and I see no reason why that wouldn't work here.
For example, in this repo:
https://github.com/AnalyticalGraphicsInc/cesium-concierge/pull/52#issuecomment-320766906
Can it be a variable?