Add plugin: Publish to Confluence

[UltraREX]

I am submitting a new Community Plugin

• [x ] I attest that I have done my best to deliver a high-quality plugin, am proud of the code I have written, and would recommend it to others. I commit to maintaining the plugin and being responsive to bug reports. If I am no longer able to maintain it, I will make reasonable efforts to find a successor maintainer or withdraw the plugin from the directory.

Repo URL

Link to my plugin:https://github.com/UltraREX/publish2confluence

Release Checklist

• [x ] I have tested the plugin on
  • [x ] Windows
  • [ x] macOS
  • [x ] Linux
  • Android (if applicable)
  • iOS (if applicable)
• [x ] My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz)
  • [x ] main.js
  • [ x] manifest.json
  • styles.css (optional)
• [ x] GitHub release name matches the exact version number specified in my manifest.json (Note: Use the exact version number, don't include a prefix v)
• [x ] The id in my manifest.json matches the id in the community-plugins.json file.
• [ x] My README.md describes the plugin's purpose and provides clear usage instructions.
• [x ] I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies.
• [x ] I have read the tips in https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines and have self-reviewed my plugin to avoid these common pitfalls.
• [ x] I have added a license in the LICENSE file.
• [ x] My project respects and is compatible with the original license of any code from other plugins that I'm using.
  I have given proper attribution to these other projects in my README.md.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here
❌ The authorUrl field in your manifest should not point to the GitHub repository of the plugin.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[UltraREX]

Reopen

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1]:The command name should not include the plugin name.

[1]:You should change all instances of var to either const or let. var has function-level scope, so it can easily lead to bugs if you're not careful. Here's a pretty good guide with examples of why not to use var: why var is obsolete

[1][2][3][4][5][6][7][8][9][10][11][12][13]:You should consider limiting the number of console.logs in your code, to not pollute the dev console.

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.
Once you have pushed all of the required changes to your repo, the bot will update the labels on this PR within 6 hours.
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.

[ObsidianReviewBot]

Changes requested by bot have been made, ready for additional review by human.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ The newly added entry is not at the end, or you are submitting on someone else's behalf. The last plugin in the list is: jack-chronicle/custom-comment. If you are submitting from a GitHub org, you need to be a public member of the org.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Description mismatch, the description in this PR (Publish markdown notes to Confluence with cookies.) is not the same as the one in your repo (Publish markdown notes to Confluence.). If you just changed it, remember to change it in the manifest.json in your repo and your latest GitHub release.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

---

Optional

[1][2][3]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.