-
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too oft…
-
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too oft…
-
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too oft…
-
This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/main/packages/flakybot).
If I'm commenting on this issue too oft…
-
The code examples should be self explanatory. That is how we should write it.
To reduce comments:
- Use suitable variable naming
- Use constants
- Use functions to reduce comments.
-
# Handle
robee
# Vulnerability details
The following functions are missing commenting as describe below:
ConvexStakingWrapper.sol, user_checkpoint (external), @return is missing
-
Allow commenting for the dual purposes of:
- debugging; and
- notes to other template developers
## Use Case 1: Notes to other developers
Comments would be programmer-readable explanation or ann…
-
```
The codebase needs significant commenting... due to the rapid redevelopment,
many of the functions and classes are not well documented.
Should this be done via JavaDocs?
```
Original issue repo…
-
Add a commenting system.
So far I have looked into IntenseDebate and Disqus.
Both are ok, but they are terrible at customization. Maintaining syntax highlighting is the hard part. Still researching …
-
It would be useful to have a comments column(?) that is editable