obsidian-plugin/al0cam_AutoMover
1
0
Fork 0
mirror of https://github.com/al0cam/AutoMover.git synced 2026-07-22 12:10:26 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
No description
15 commits 2 branches 10 tags 234 KiB
TypeScript 93.6%
CSS 3.9%
JavaScript 2.5%
Find a file
Al0cam 657841cb3f updating readme
2025-02-12 10:44:04 +01:00
Models simplified MovingRule to only have public attributes 2024-11-14 17:19:05 +01:00
Settings added duplicate button and removed unused properties 2025-02-12 10:43:46 +01:00
Utils finished plugin core functions 2025-02-10 12:01:16 +01:00
.editorconfig Initial commit 2024-09-17 10:23:12 +02:00
.eslintignore Initial commit 2024-09-17 10:23:12 +02:00
.eslintrc Initial commit 2024-09-17 10:23:12 +02:00
.gitignore Initial commit 2024-09-17 10:23:12 +02:00
.npmrc Initial commit 2024-09-17 10:23:12 +02:00
biome.json updated biome config 2025-02-06 21:20:27 +01:00
bun.lockb added settings tab 2024-10-01 10:31:49 +02:00
esbuild.config.mjs Initial commit 2024-09-17 10:23:12 +02:00
ItemToMove.md added settings tab 2024-10-01 10:31:49 +02:00
main.ts finished plugin core functions 2025-02-10 12:01:16 +01:00
manifest.json init 2024-09-17 16:53:18 +02:00
package-lock.json added settings tab 2024-10-01 10:31:49 +02:00
package.json updated UI and started work on regexRules that will move items around 2024-10-09 11:10:43 +02:00
README.md updating readme 2025-02-12 10:44:04 +01:00
styles.css added duplicate button and removed unused properties 2025-02-12 10:43:46 +01:00
tsconfig.json Initial commit 2024-09-17 10:23:12 +02:00
version-bump.mjs Initial commit 2024-09-17 10:23:12 +02:00
versions.json Initial commit 2024-09-17 10:23:12 +02:00

README.md

AutoMover plugin

This plugin is used for designating folders in which your files will be moved automatically. It seeks to be an alternative to the "https://github.com/farux/obsidian-auto-note-mover" plugin from farux. The problem I had with that plugin was the lack of support for regex and regex groups in the destination paths.

Therefore, this plugin supports regex and regex groups to create the destination paths unless they already exist.

Releasing new releases

  • Update your manifest.json with your new version number, such as 1.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 or npm version major after updating minAppVersion manually in manifest.json. The command will bump version in manifest.json and package.json, and add the entry for the new version to versions.json

TODO: Adding your plugin to the community plugin list