Markdown table should be the step summary of the action

[koppor]

The table at https://github.com/JabRef/jabref-action#output should be the GitHub actions step summary of the action.

See https://github.blog/news-insights/product-news/supercharging-github-actions-with-job-summaries/#create-summaries for details.

Task: Modify this action to fill $GITHUB_STEP_SUMMARY file.

[aravind4799]

Hello! This looks like a great first issue for me to start my open source contributions with. I'll get started on it now.

[evealitaylor]

/assign-me

[github-actions]

👋 Hey @evealitaylor, thank you for your interest in this issue! 🎉

We're excited to have you on board. Start by exploring our Contributing guidelines, and don't forget to check out our workspace setup guidelines to get started smoothly.

For questions on JabRef functionality and the code base, you can consult the JabRef Guru or ask on our Gitter chat.

In case you encounter failing tests during development, please check our developer FAQs!

Having any questions or issues? Feel free to ask here on GitHub. Need help setting up your local workspace? Join the conversation on JabRef's Gitter chat. And don't hesitate to open a (draft) pull request early on to show the direction it is heading towards. This way, you will receive valuable feedback.

Happy coding! 🚀

[evealitaylor]

@koppor I am thinking the best strategy for this is to configure a new entrypoint to a new bash script to make the changes. Would the creation of an entry point script seem appropriate for this repo, or should this just be completely contained within the Dockerfile and pipeline? ZachCraw is my co-dev for this ticket :)