Matrix documentation #66
No reviewers
Labels
No labels
blocked
bug
component: fediversity panel
component: nixops4
contributor experience
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
goal: devops
project-management
question
role: sysadmin
security
technical debt
testing
user experience
user story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Fediversity/Fediversity#66
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "hans/Fediversity:main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Matrix documentation is pretty much finished, at least all aspects have been covered.
@Niols of @fricklerhandwerk, can one of you merge this bit please?
@hans> Is your request for a merge still up to date?
@Niols Yes, it's up to date. In fact, I just corrected a few things that Kevin pointed me at.
Nice, thanks @Niols.
Not really sure how to continue from here, so I'll just ask :)
No doubt there are going to change things in this documentation, and I can already see several things to be added. I assume what I should do is rebase my fork to absorbe the merge, continue to add/change stuff in my own fork, and when I think the new stuff should be merged, I create another PR from this same fork, right?
Sounds perfect!