Vibe Coding with GitHub Copilot (Getting Started with GitHub Copilot)

This is the last Gobbledygook post on PLOS Blogs, and at the same time the first post at the new Github blog location. I have been blogging at PLOS Blogs since the PLOS Blogs Network was launched in September 2010, so this step wasn't easy. But I have two good reasons. In May 2012 I started to work as technical lead for the PLOS Article-Level Metrics project.

Ein Fehler ist aufgetreten. Sieh dir dieses Video auf www.youtube.com an oder aktiviere JavaScript, falls es in deinem Browser deaktiviert sein sollte. A source code version control system is an essential ingredient of software development. But it's just low-level technology that doesn't change the way you think about creating software and so can safely be ignored.

The science blog archive Rogue Scholar depends heavily on GitHub Actions. They are used to trigger content and metadata extraction of new blog posts and to register DOIs for these posts with Crossref. More recently they have also been used to push this content and metadata to the new InvenioRDM-based Rogue Scholar platform. GitHub Actions are workflows that typically operate on the command line.

Some time ago, the brilliant GitHub people gave me the following tip. Rajarshi is lazy, and might find it interesting. By appending .patch to the commit URL, a commit can easily be downloaded as patch. That way, developers can easily download it with wget or curl and apply it locally with git am, without having the fetch the full repository.

Playing with my eLife Lens-inspired article viewer and some recent articles from ZooKeys I regularly come across articles that are incorrectly marked up. As a quick reminder, my viewer takes the DOI for a ZooKeys article (just append it to http://bionames.org/labs/zookeys-viewer/?doi=, e.g. http://bionames.org/labs/zookeys-viewer/?doi=10.3897/zookeys.316.5132), fetches the corresponding XML and displays the article.Taking the article