-
Notifications
You must be signed in to change notification settings - Fork 252
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
docs: update code block in ADR-006 #874
Conversation
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.
Question for reviewers: do we treat ADRs as a snapshot in time or should we update them to reflect changes that take place after the ADR was reviewed?
we can do both, as that's what tendermint and cosmos do. Updating can be tedious, and we should only do it if it makes sense (or is requested) or leave them as good beginner issues imo
@@ -1,3 +1,5 @@ | |||
"default": true # Default state for all rules | |||
"MD010": | |||
"code_blocks": false # Disable rule for hard tabs in code blocks |
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.
🔥 🔥 👍
Addresses informalsystems/audit-celestia#20 (comment) Question for reviewers: do we treat ADRs as a snapshot in time or should we update them to reflect changes that take place after the ADR was reviewed?
Addresses informalsystems/audit-celestia#20 (comment)
Question for reviewers: do we treat ADRs as a snapshot in time or should we update them to reflect changes that take place after the ADR was reviewed?