-
Notifications
You must be signed in to change notification settings - Fork 17
Add full release docs #42
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
opusforlife2
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Start all new sentences with capital letters.
Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com>
|
@opusforlife2 all done, and added a few commits blending the new documentation into the old one and making this PR ready. Thank you for the suggestions ;-) |
Co-authored-by: opusforlife2 <53176348+opusforlife2@users.noreply.github.com>
|
@opusforlife2 all done, except #42 (comment) ;-) |
|
@TobiGr can you deploy? Or explain me how it can be done |
|
Isn't this page just hosted on GitHub pages? The files should be in some |
|
Uhm, ok, I tried to serve it on my pc but the formatting is all broken... It wasn't the case in the vscode Markdown editor... |
While releasing 0.23.1 I wrote down all of the steps I took, both as an effort to not forgetting things all the time, and so as to better understand what needs to be done to achieve automation.
The name of the file is obviously not the correct one, but I still don't know where to put this file, and what to do of the current file that explains how to do releases.
The section about the blog post is still almost empty, please join in @opusforlife2 @Poolitzer.
Since you are not watching, here is a ping for you: @litetex @AudricV @mhmdanas @Redirion