-
Notifications
You must be signed in to change notification settings - Fork 153
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
Report-config.json: Support more fields #1360
Comments
We can also extend it to configure the introductory text as outlined in #467. |
I think we have to decide to what extent should we allow the customization of the introductory text. If its just basic text replacement, then it can be done, but if the users are allowed to modify the html themselves, then it might not be suitable |
@damithc Hi, Prof. Do you think a simple text will do what you need? |
I think it would be support basic HTML but if that's too hard, even just text is good enough. We also need to figure out where we are going to display that text, in what format. |
Related task for setting |
Hi, may I check if this issue is resolved? If not, may I try this issue? |
Hi @logical-1985516, I think this issue is not so relevant anymore as one of our ongoing PRs #2192 might make it irrelevant when merged, depending on the implementation. I'd recommend working on other issues for now, thanks! |
We have added a report-config.json file that can be used for the configuration of report generation.
Right now, it only allows users to specify a report title.
We can support more fields with this config file, especially if they can be applied to all repositories during report generation.
The following are some of the fields I think we can include:
The text was updated successfully, but these errors were encountered: