You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2021. It is now read-only.
I'd like to use some different text for the explanatory comment that is posted when an issue is closed. However, currently the only way to do that is to fork the repository and build from source. It would be much more convenient to allow exporting an optional environment variable to override the explanatory comment.
The text was updated successfully, but these errors were encountered:
raxod502
added a commit
to raxod502/no-carrier
that referenced
this issue
Aug 13, 2017
Yeah, I'm in favor of it being customizable. Problem is, that implies picking a templating system, and I've no idea which to choose. Recommendations welcomed.
For something as simple as this, I don't think it would be remiss to just use $DAYS_ELAPSED, $LABEL_NAME, etc. and then allow \$LABEL_NAME for quoting. I don't do Scala but it looks like you can do regex replacement using a function of the match, so this would be pretty trivial implementation-wise.
I'd like to use some different text for the explanatory comment that is posted when an issue is closed. However, currently the only way to do that is to fork the repository and build from source. It would be much more convenient to allow exporting an optional environment variable to override the explanatory comment.
The text was updated successfully, but these errors were encountered: