Closed mathisgauthey closed 4 months ago
I need you settings.
I need you settings.
Oh, pretty sure I copied them inside the template :o I edited the post o/
Fixed in v7.0.6
Caused by the slugify encoding of the anchor, that removed the #
.
Fixed in
v7.0.6
Caused by the slugify encoding of the anchor, that removed the#
.
Thanks again for your reactivity ✌️ Still enjoying your plugin after more than a year 💪
Issue validation
Command used
Upload single current active note
Plugin version
7.0.5
Describe the bug
When using the option
[[Wikilinks]] to [MDlinks](links) Convert Wikilinks to MDlinks, without changing the contents.
, the links are not correctly translated if they link to a file header.How to reproduce ?
|
argument to define a custom text link. Example :[[How to Enforce Commit Conventions and Automate the Release and Changelog Process#Configuration|previous section]]
[previous section](How%20to%20Enforce%20Commit%20Conventions%20and%20Automate%20the%20Release%20and%20Changelog%20Process.mdconfiguration)
and it leads to a 404 error page not found.Minimal Reproducible Example
The link is present just before the
### Launch Locally to Test it Out
section, in the callout. It links to### Configuration
It should create a
package.json
andpackage.lock
file in your repository. Don't forget to addnode_modules/
to your.gitignore
file but keep the other two committed as they manage the packages and packages dependencies versions respectively.Configuration
Then, create a configuration file named
.releaserc
at the root of your repository. More on that here, but just copy and paste that for now :Note that there are two ways to modify the
release-notes-generator
to your liking, and they both involves adding another key belowpreset
in your config file.According to the plugin's README :
So you can modify the settings :
writerOpts
key and change the different templates parts likeheaderPartial
orcommitPartial
. Example can be found here.compareUrlFormat
for example, is to use thepresetConfig
option. Example can be found here.Auto-increment the Version
You might want to auto-increment your app version when you release it. It is possible to do it by using
semantic-release/exec
and execute a bash script like this one that replaces the version in the__manifest__.py
file of a Odoo module :Launch Locally to Test it Out
If you want to run the
semantic-release
locally, use./node_modules/.bin/semantic-release --no-ci --dry-run
. If you're satisfied with the results, just get rid of the--dry-run
, and it will create a release commit and tag locally that you can then push if you like.Add Semantic-release to Your Continuous Integration & Deployment Solution
If you want to automatically trigger a release when a new commit is detected on your main branch (that's only an example, you can fine tune it obviously), you can add it to your CI configurations. You can find examples on the semantic-release repository for Github, Gitlab, Jenkins or Travis.
If you happen to use AzureDevOps, first of all best of luck to you too, and feel free to use my simple template here :
You can use a different agent, try using a Ubuntu LTS if possible. Don't forget to use the
GIT_CREDENTIALS
as they are required for semantic-release to be able to commit and push the release commit.Enforce Commit Conventions in Your Team
Introduction
Creating new rules and standards can be pretty hard, especially in a team that has been working differently for a very long time.
But a developer should know how to write a good commit message, it is an essential part of his job as he won't always be the one to work on complex pieces of software, and needs to communicate for the present colleagues and the futures ones.
A good example that follows directly the flow from above might be :
Use an Editor Extension
There's probably an extension that might allow for a streamlined conventional commit process in your editor, for example :
Here's an extension that allows to use a commit modal when commiting changes on VS Code. Simply install and use it when committing changes.
Use a CLI Tool
Alternative to an editor extension, here on the CLI directly, you can install it globally using :
Simply use
git cz
or justcz
instead ofgit commit
when committing. You can also usegit-cz
, which is an alias forcz
. If you use npm 5.2+, you can also usenpx cz
.Force Conventional Commits Using Commitlint
If you want to enforce it and don't allow for random commit messages, you can enforce it with pre-commit hooks using commitlint :
At the root of your project, execute the following commands :
Configuration
Relevant log output
OS
Windows
Anything else?
No response
Plugin settings
As for my mkdocs settings, you can find them here.
Obsidian information