This is a simple Obsidian plugin for rendering plaintext GoLinks (like go/links) so that they're clickable.
This plugin renders plaintext go/links as clickable! It ignores links in `go/backticks` and links that have already been [go/linkified](https://go/linkified).
> It also works in go/blockquotes, and...
- it
- works
- in
- go/lists!
- neat, right?
This plugin can be installed from the Obsidian Plugins directory!
You can also click this link to open the page directly in Obsidian: https://obsidian.md/plugins?id=obsidian-golinks
- create the
path/to/your/vault/.obsidian/plugins/obsidian-golinks
folder - go to the latest GitHub release
- download the
main.js
andmanifest.json
- move both of those files to the folder created in step 1
- in Obsidian settings, enable the plugin like normal
- clone this repo into
path/to/your/vault/.obsidian/plugins/obsidian-golinks
- in that folder install dependencies by running
yarn
- build w/
yarn build
- in Obsidian settings, enable the plugin like normal
There is no risk of data loss when using this plugin. As it only acts on the markdown rendering process, the worst it can do is make your reading view not show some of your text (or show it incorrectly). If this happens, disable the extension and please file an issue.
No data is sent off your machine, so this plugin is perfectly safe to use in corporate contexts. It's basically just some regex.
- Update your
manifest.json
with your new version number, such as1.0.1
, and the minimum Obsidian version required for your latest release. - Update your
versions.json
file with"new-plugin-version": "minimum-obsidian-version"
so older versions of Obsidian can download an older version of your plugin that's compatible. - Create new GitHub release using your new version number as the "Tag version". Use the exact version number, don't include a prefix
v
. See here for an example: https://github.com/obsidianmd/obsidian-sample-plugin/releases - Upload the files
manifest.json
,main.js
,styles.css
as binary attachments. Note: The manifest.json file must be in two places, first the root path of your repository and also in the release. - Publish the release.
You can simplify the version bump process by running
npm version patch
,npm version minor
ornpm version major
after updatingminAppVersion
manually inmanifest.json
. The command will bump version inmanifest.json
andpackage.json
, and add the entry for the new version toversions.json