Skip to content

Commit

Permalink
(Hopefully) fixed DOI badge
Browse files Browse the repository at this point in the history 
DOI badge acted very strangely. The markdown seemed fine, but the generated badge linked to the LexiconSE Zenodo archive. Maybe moving it around (to force a new commit) will do the trick?
  • Loading branch information
@WoutDLN
WoutDLN authored Feb 17, 2023
1 parent 5b257a4 commit 90a6acf
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion README.md
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
# DIY frankensTEIn
[![DOI](https://zenodo.org/badge/471181054.svg)](https://zenodo.org/badge/latestdoi/471181054)

# DIY frankensTEIn

🚀 [Visit the Website](https://sslis.github.io/DIY-frankensTEIn/) 🚀

This is a work in progress adaptable template repository designed to help students in the University of Borås' Digitizing Cultural Herirate Materials course to develop their own website for presenting their digitisation projects, hosted on GitHub.

2 comments on commit 90a6acf

@WoutDLN
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For some reason, the GitHub repo is still generating the wrong badge -- even though the link is correct.

It may not help that git interprets the change that line 1 (header 1 title) was moved to line 3, even though what I really did was move line 2 (DOI badge) over line 1. But technically, it's the same thing of course.

@WoutDLN
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scratch that, problem solved... It wasn't the link that was wrong, it was the title of the archive in Zenodo. Fixed that issue over there now.

Please sign in to comment.