-
Notifications
You must be signed in to change notification settings - Fork 35
Solve some markdownlint issues #964
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Awaiting approval from the team (do-not-merge label) |
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
Signed-off-by: Martijn Govers <Martijn.Govers@Alliander.com>
|
The base branch was changed.
I see that the PyPI job has not triggered yet on the current release |
Seems deeper and not something we can (re)solve automatically. I manually kicked off the publish pipeline to unblock this and other work. NOTE: we will need to do the same until a permanent solution is implemented |
markdownlint
to VSCode workspace recommendationsResolve the following markdownlint issues:
NOTE: the following ones are still remaining: