Note that Netlify has a low limit for free tier users (only 300 build minutes per month as at June 2020 -- a single report generation can take 2-3 build minutes, longer if your report includes many/big repositories).
Fork the publish-RepoSense repository using this link. Optionally, you can rename the fork to match your RepoSense report e.g.,
Set up Netlify for your fork as described in this guide.
You will need to use the following in step 5:
pip install requests && ./run.sh
After Netlify finishes building the site, you should be able to see a dummy report at the URL of your Netlify site.
Generate the report you want by updating the settings in your fork.
run.shfile of your fork (on GitHub).
java -jar RepoSense.jar --repos FULL_REPO_URL(assuming you want to generate a default report for just one repo)
java -jar RepoSense.jar --repos https://github.com/reposense/RepoSense.git(note the .git at the end of the repo URL)
After setting up Netlify for your repo containing RepoSense settings, when a PR comes in to that repo to update any setting, you can scroll down the PR page and in
All checks have passed, click on the
deploy/netlify — Deploy preview ready! to see a preview of the report as per the changes in the PR.
Manual: Netlify UI has a way for you to trigger a build, using which you can cause the report to be updated.
Automated: Netlify's can be set up to update the report whenever a target repo of your report is updated, provided you are able to update the target repos in a certain way.
Click Add build hook, give your webhook a name, and choose the
master branch to build. A Netlify URL will be generated.
Go to your target repository (the repository you want to analyze) and click on Settings.
Note: Although the build url is not that secretive, it should be kept safe to prevent any misuse.
Select application.json as content type.
Select Let me select individual events and based on your requirements check the checkboxes.
Leave the Active checkbox checked.
Click on Add webhook to save the webhook and add it.