JabRef
v6
v6
  • JabRef Bibliography Management
  • Installation
  • Getting started
  • Collect
    • Add entry manually
    • Add entry using an ID
    • Add entry using reference text
    • Searching externally using Online Services
    • Add entry using PDFs
    • Add PDFs to an entry
    • Browser Extension
    • Import
      • Custom import filters
      • Import inspection window
  • Organize
    • Edit an entry
    • Groups
    • Keywords
    • Mark and grade
    • Comment on an entry
    • Searching within the library
    • Complete information using online databases
    • Manage associated files
    • Manage field names and their content
    • Best practices
    • Check consistency
    • Cleanup entries
    • Check integrity
    • Find duplicates
    • Merge entries
    • Save actions
  • Cite
    • BibTeX and biblatex
    • Pushing to external editor application
    • Export to Microsoft Word
    • OpenOffice/LibreOffice integration
  • Share
    • Sharing a Bib(la)TeX Library
    • Shared SQL Database
      • Migration of pre-3.6 SQL databases into a shared SQL database
    • Export
      • Custom export filters
    • Send as email
  • AI functionality
    • AI providers and API keys
    • AI preferences
    • AI troubleshooting
    • Running a local LLM model
  • Configuration
    • Customize the citation key generator
    • Customize entry types
    • Customize general fields
    • Customize key bindings
    • Library properties
    • Entry preview setup
    • Manage external file types
    • Manage protected terms
    • The string editor
  • Advanced information
    • Main Window
    • Entry Editor
      • Links to other entries
      • The Bibtex / Biblatex source tab
      • The 'owner' field
      • Time stamp field
      • LaTeX Citations Tab
    • About BibTeX and its fields
    • Strings
    • Field content selector
    • URL and DOI links in JabRef
    • Command line use and options
    • Automatic Backup (.sav and .bak) and Autosave
    • XMP metadata support in JabRef
    • Remote operation
    • Custom themes
    • Journal abbreviations
    • New subdatabase based on AUX file
    • How to expand first names of an entry
    • Debugging your library file
    • Resources
    • License
    • Knowledge
      • MS Office Bibliography XML format
      • Comparison of the Medline (txt), Medline (xml), and RIS format
      • EndNote Export Filter
  • Frequently Asked Questions
    • Linux
    • Mac OS X
    • Windows
  • JabKit
  • Discussion Forum
  • Contribute to JabRef
    • How to Improve the Help Page
    • How to translate the JabRef User Interface
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF

Contribute to JabRef

PreviousJabKitNextHow to Improve the Help Page

Last updated 1 day ago

Was this helpful?

We are really happy that you are interested in contributing to JabRef. Please take your time to look around here. We especially invite you to look into our where members introduce themselves.

I would like to try out a feature introduced at pull request.

In JabRef, there are dozens of bug fixes and new features introduced using GitHub's pull request mechansim. You can browse all at . The JabRef team really welcomes users to try out these changes and to comment on them. Improving on changes in active pull requests is much easier than fixing them later on after their acceptance.

If you are familiar with the command line on your OS, then it is very easy to try out pull requests and give feedback. In the following, we try to give a minimal set of installation instructions to be able to run a contribution from a fork.

Required tooling:

  • - A command-line client for GitHub. You can install it using the installer linked on their or the commands given at the .

  • - A cross-platform and cross-architecture version manager. Download and store it in your home (or Downloads) directory.

Initial setup:

  • Windows:

    • Open PowerShell

    • Switch to a directory containing git repositories. We recommend c:\git-repositories

      • mkdir c:\git-repositories

      • cd c:\git-repositories

    • Get gg.cmd

      • wget ggcmd.io -OutFile gg.cmd

    • Clone JabRef

      • ./gg.cmd jbang https://github.com/JabRef/jabref/blob/main/.jbang/CloneJabRef.java JabRef

    • Make gg.cmd available in JabRef directory

      • cd JabRef

      • move ..\gg.cmd .

  • Linux:

    • Open a shell

    • Switch to a directory containing git repositories. We recommend ~/git-repositories

      • mkdir ~/git-repositories

      • cd ~/git-repositories

    • Get gg.cmd (using either wget or curl)

      • wget ggcmd.io/gg.cmd

      • Alternative: curl -L ggcmd.io > gg.cmd

    • Clone JabRef

      • sh ./gg.cmd jbang https://github.com/JabRef/jabref/blob/main/.jbang/CloneJabRef.java JabRef

      • NOTE: You can also use the native git client: git clone --recurse-submodules https://github.com/JabRef/jabref.git JabRef for achieving the same result.

    • Make gg.cmd available in JabRef directory

      • cd JabRef

      • mv ../gg.cmd .

Now you are all set: You have a directory JabRef containing the recent updates and also gg.cmd which you will need later for executing a JabRef build.

Try a branch:

  1. cd into the JabRef directory: cd c:\git-repositories\JabRef

  2. Compile and run JabRef: gg.cmd gradle run :jabgui:run (on Linux and macOS, you need to prefix it with sh: gg.cmd gradle run :jabgui:run). This will also download the necessary JDK and gradle distribution. On the first run, please give the system enough time to accommodate and wait until the JabRef window launches. Depending on your hardware, this may take minutes.

Alternatives:

  1. You don't want to use gg.cmd: You have the project clone ready and have some Java JDK available: In the JabRef directory, execute ./gradlew run.

  2. You don't want to use GitHub's gh tool: You can use the "usual" git clone ..., git remote add ..., git fetch ..., and git checkout ... commands to checkout a pull request from a fork.

I would like to improve the help page.

I would like to help translating JabRef to another language.

I would like to keep Wikipedia pages up-to-date.

JabRef improves -- and Wikipedia pages should keep up!

For changes in a specific language, go to the related page, and simply click on "Edit" (top right-hand tab). Currently, existing pages are:

If there is no page for your own language, you can easily create one.

I have some cool feature requests.

Can I make a donation? How?

Our team consists of volunteers. To provide better support, we are currently trying to get a funded developer on board. Please consider donating money!

I would like to contribute code. How to?

Checkout out the pull request: gh pr checkout 13111 - where 13111 is the PR number, in this case .

Please see

We encourage you to read about .

For changes affecting all languages, update the .

Deutsch:

English:

Español:

Français:

Italiano:

Русский:

Portuguese:

Svenska:

Українська:

中文:

Donations keep us going! You can use PayPal or bank transfers. Your institution/company can contribute too, through bank transfer for example. All details are provided at .

Please head to our .

community members page
https://github.com/JabRef/jabref/pulls
GitHubCLI
homepage
installation hints
gg.cmd
gg.cmd
pr#13111
How to Improve the Help Page
translating the JabRef user interface
wikidata entry of JabRef
https://de.wikipedia.org/wiki/JabRef
https://en.wikipedia.org/wiki/JabRef
https://es.wikipedia.org/wiki/JabRef
https://fr.wikipedia.org/wiki/JabRef
https://it.wikipedia.org/wiki/JabRef
https://ru.wikipedia.org/wiki/JabRef
https://pt.wikipedia.org/wiki/JabRef
https://sv.wikipedia.org/wiki/JabRef
https://uk.wikipedia.org/wiki/JabRef
https://zh.wikipedia.org/wiki/JabRef
Come discuss it!
https://donations.jabref.org
Contributing Guide