Damith C. Rajapakse
Damith C. Rajapakse
> I found the github API that will return the commit diff, sth like the image below, and there are open source diff parser but havnt tested. If we only...
> In the case where the existing gh-pages site is deployed based on auto-deploy scripts, the situation is a bit complicated since most likely the maintainer of the repo has...
> I mean before adding RepoSense's deployment script, the existing gh-pages site may have its own script to publish its content (for example, using asciidoctor to convert `adoc` files to...
Good progress @niqiukun Is it possible to generalize your approach independent of RepoSense. The general problem: * Use GitHub pages as the deployment target and travis as the CI to...
> I see. I will look into this. But just to check, there are still multiple repos but the GitHub page is only deployed to the main repo right? Yes....
Thanks for looking into this @tlylt I'm not sure if it will work for the use case of deploying code dashboards as part of CS2103 website. This is because CS2103...
We don't use this technique in our other projects. Which means we can survive without it. But I don't mind giving it a try just to see how it goes....
@gerhean @dcshzj @HCY123902 need help with this
Thanks for the investigation @HCY123902 How come .fxml files still appear in the code view? Perhaps 'ignore glob' is not working fully?
> I think using `src/main/resources/**` instead of `src/main/resources` will remove the Fxml file changes and commits that only involves Fxml and CSS files from the report, which should give the...