Hi it´s possible to know how enter in this options thanks

@cdiegobb If I understand your question right, you are asking how to start that functionality? It changed now and then in the past. Currently, it is reachable from "Lookup":

@koppor Yes thanks i will try to work on that

@cdiegobb Thank you! Please try to do test-driven development. I hope, you are knowledable with JUnit.

@cdiegobb, since there has not been any activity, I assume you have dropped the issue. Be aware you can unassign yourself from Github.

Hi, is this issue still available to take? I am looking for an issue as my first contribution. I'd like to work on this issue.

As a general advice for newcomers: check out https://github.com/JabRef/jabref/blob/main/CONTRIBUTING.md for a start. Also, https://devdocs.jabref.org/getting-into-the-code/guidelines-for-setting-up-a-local-workspace is worth having a look at. Feel free to ask if you have any questions here on GitHub or also at JabRef's Gitter chat.

Try to open a (draft) pull request early on, so that people can see you are working on the issue and so that they can see the direction the pull request is heading towards. This way, you will likely receive valuable feedback.

Hello, I would like to ask if I should create a branch to solve the issue or fork the main branch. According to the contribution documentation, it mentions creating a branch to work on the issue, but I don't have permission to create a new branch in the repository. Could you please clarify the correct approach? Thanks

@R-Zhou4 Thank you for the question. I refined our guide at JabRef#11978.

The hint is to follow the "Pre Condition 3: Code on the local machine". Maybe, we should be more clear in this step and change the heading? - Currently, I hope that the text "a) create a fork" should make clear that this is required to contribute.

I hope, the text provided at this page guides you well.