Thanks a lot @vadorequest
for the input! Really appreciate it 🙌🏻
An option to decide whether do the sentiment analysis per file or per "block" could be handful.
That is a great idea, I actually thought about that myself. From my experience, when we usually run sentiment analysis on actual documents, we do it for the whole document. But I see how there is a content issue there. While papers are meant to be written about the same topic, on a website you have different sections that might be totally unrelated and have a different tone, vibe, or language. So I think an option to switch between those would be really helpful.
It would definitely be great to have it both as Action comment (as shown above) and as PR comment (for history and easier/faster visualization).
Thank you for that, I totally agree. I am currently trying to sort out @actions/github and then I will jump on the PR comment.
Having such artifact would allow the owner to actually use those results programmatically quite easily. (table is great for visualization)
This is such a great idea, never thought about how should I take this programmatically to the next steps.
Thanks a lot @vadorequest for the input! Really appreciate it 🙌🏻
That is a great idea, I actually thought about that myself. From my experience, when we usually run sentiment analysis on actual documents, we do it for the whole document. But I see how there is a content issue there. While papers are meant to be written about the same topic, on a website you have different sections that might be totally unrelated and have a different tone, vibe, or language. So I think an option to switch between those would be really helpful.
Thank you for that, I totally agree. I am currently trying to sort out @actions/github and then I will jump on the PR comment.
This is such a great idea, never thought about how should I take this programmatically to the next steps.
Thanks for sharing UnlyEd/next-right-now, you have really nice pipelines in there.
Thanks! Glad it helped :)