GitHub action to retrieve Zotero collection in BibLaTeX format and save it as GitHub repository
GitHub action to automatically retrieve your Zotero collection in BibLaTeX format at 8:00, 12:00 and 18:00 and save it as GitHub repository.
Make sure you have a Zotero.org account and sync your local installation with it.
Get userID
from Zotero https://www.zotero.org/settings/keys
userID
as value of ZOTERO_USER_ID
to GitHub secrets of your repoCreate a new API Key
for Zotero https://www.zotero.org/settings/keys/new. If you grant access to group libraries, they are also retrieved.
Copy the new API Key
API Key
as value of ZOTERO_BEARER_TOKEN
to the GitHub secrets of your repoTo manually run the workflow, ensure that your GitHub repository has the appropriate permissions set. You need to assign workflow permissions that allow the execution of workflows manually. This is crucial for triggering the workflow as per your requirements.
For detailed steps on setting these permissions, refer to the GitHub documentation on manually running a workflow. Make sure to review and adjust the permissions under your repository’s settings to align with your workflow needs.
Copy the link to https://raw.githubusercontent.com/maehr/zotero-bib-to-gh/master/bibliography/zotero.bib (i.e. https://raw.githubusercontent.com/YOURNAME/zotero-bib-to-gh/master/bibliography/zotero.bib).
Change .github/workflows/zotero-bib-to-git.yml
to adjust the cronjob to your needs or run it manually (check out crontab.guru if you are not familiar with cronjobs).
on:
schedule:
- cron: "0 8,12,18 * * *"
This project is maintained by @maehr. Please understand that we won’t be able to provide individual support via email. We also believe that help is much more valuable if it’s shared publicly, so that more people can benefit from it.
Type | Platforms |
---|---|
🚨 Bug Reports | GitHub Issue Tracker |
🎁 Feature Requests | GitHub Issue Tracker |
🛡 Report a security vulnerability | GitHub Issue Tracker |
No changes are currently planned.
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
We use SemVer for versioning. For the versions available, see the tags on this repository.
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE.md file for details