-
Notifications
You must be signed in to change notification settings - Fork 21
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
Generate html diff output (for GitLab) #91
Comments
Hi @sergeyshevch |
Maybe something like: https://diff2html.xyz. I guess rust also has some solution for it For not it's slightly hard to send output to comment in gitlab but it already support exposing artifacts on gitlab pages, but it doesn't support markdown for now Regarding current diff, maybe it's good idea to place each file in it's own spoiler. It will help reading of large diffs |
Maybe I can handle it on my side later then, with something like https://github.com/pycontribs/ansi2html or https://github.com/Wilfred/difftastic/?tab=readme-ov-file Then it can be good to have just plain git diff as an output and leave postprocessing to end user |
What did you end up doing? :) Would you be open to sharing the script you used to get it working with GitLab? 🚀
If you want to get the raw output of git diff you can just run after the tool finishes:
|
@dag-andersen I found correct way to post it to Gitlab
Also I guess this comemment can be really improved if we split diff spoiler per application Like app1
app2
app3
|
@sergeyshevch I haven't worked with GitLab in a long time. Would you mind sharing the full pipeline you're using? If so, I can add it to the docs so others can see how to use the tool with GitLab Alternatively, if you'd like to contribute, you can add a page similar to this one: GitHub Actions Workflow. |
Hello! I'm looking to expose diff output into gitlab, and for now it's not support .md files to expose on pages.
Maybe it's possible to add .html output with generated styles. Later we can also improve diff readability as well
The text was updated successfully, but these errors were encountered: