JabRef
Add right click option to delete custom bst style for entry preview
Is your suggestion for improvement related to a problem? Please describe. I can add a new custom BST style in JabRef for entry preview but I have no option to remove it.
Describe the solution you'd like Add a right click option to remove the style. This should only be possible for bst styles.
Additional context Example bst files can be found in jabref/jablib/src/test/resources/org/jabref/logic/bst/IEEEtran.bst
Hey @Siedlerchr I'm new comer here!! I would to Like to work on that issue Can u assign this issue to me ??
Welcome to the vibrant world of open-source development with JabRef!
Newcomers, 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.
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.
⚠ Note that this issue will become unassigned if it isn't closed within 30 days.
🔧 A maintainer can also add the Pinned label to prevent it from being unassigned automatically.
Happy coding! 🚀
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
⚠️ Issue Already Assigned
Hi @KevinITAn, this issue is currently assigned to @Raghavjha60570.
[!NOTE] If no progress is made within 21 days, the issue will be automatically unassigned.
Options for contributors
- Wait for availability: The issue may become available if auto-unassigned
- Collaborate: You can ask the assignee if they want help
- Maintainer assistance: A maintainer can add you as co-assignee if appropriate
⏰ Assignment Reminder
Hi @Raghavjha60570, this is a friendly reminder about your assignment to this issue.
[!WARNING] This issue will be automatically unassigned in 10 days if there's no activity.
Remember that you can ask the JabRef Guru or DeepWiki about anything regarding JabRef. Additionally, our contributing guide has hints on creating a pull request and a link to our Gitter chat.
How to keep your assignment
If you are working on it, you can prevent automatic unassignment by:
- Submitting a draft pull request with your progress within 10 days
- Asking for the 📌 Pinned label if you need more time
We appreciate your contribution and are here to help if needed!
📋 Assignment Update
Hi @Raghavjha60570, due to inactivity, you have been unassigned from this issue.
Next steps
If you still want to work on this:
- Submit a pull request showing your current state. You will be automatically assigned again.
- Ask a maintainer to assign you again.
👋 Hey @btomar00001, thank you for your interest in this issue! 🎉
We're excited to have you on board. Start by exploring our Contributing guidelines, and set up your local development workspace by following the steps in our workspace setup guidelines to get started smoothly.
For questions on JabRef functionality, you can consult the JabRef Guru. For questions related to the codebase, please start using DeepWiki.
In case you encounter failing tests during development, please check our developer FAQs!
Still facing issues or having more questions? Feel free to ask here on GitHub or on JabRef's Gitter chat. Please don't hesitate to open a (draft) pull request early on to show the direction you are heading towards if unsure.
Happy coding! 🚀
Thank you for your continued work in JabRef. At this point, you probably already know the basics and the important links. If not, our contributing guidelines is the place you should go to.
Happy coding! 🚀
Thank you for your continued work in JabRef. At this point, you probably already know the basics and the important links. If not, our contributing guidelines is the place you should go to.
Happy coding! 🚀
Re-assigning myself. Just to clarify: I closed the previous PR due to technical issues with the automated tools.
My new PR is #14628. It is clean, has passed all CI checks, and is ready for review. Thanks!
We think that this issue was fixed. Please head to https://builds.jabref.org/main to download a development build and try it out.
For any feedback, add a comment to the pull request at https://github.com/JabRef/jabref/pull/14628.