Skip to content
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

chore: add godoc comment requirement #587

Merged
merged 1 commit into from
Mar 17, 2023
Merged

Conversation

bryanchriswhite
Copy link
Contributor

@bryanchriswhite bryanchriswhite commented Mar 15, 2023

Description

Help us bootstrap and subsequently maintain godoc comments in the codebase via our existing review process.

Issue

image

Type of change

Please mark the relevant option(s):

  • New feature, functionality or library
  • Bug fix
  • Code health or cleanup
  • Major breaking change
  • Documentation
  • Other: Tooling

List of changes

  • Adds an item to the "Required Checklist" in the PR template

Next Steps

I'm extremely confident that we could automate these checks with the correct linter / config. At that point, we could remove this checklist item.

Testing

  • make develop_test
  • LocalNet w/ all of the steps outlined in the README

Required Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added, or updated, godoc format comments on touched members (see: tip.golang.org/doc/comment)
  • I have tested my changes using the available tooling
  • I have updated the corresponding CHANGELOG

If Applicable Checklist

  • I have updated the corresponding README(s); local and/or global
  • I have added tests that prove my fix is effective or that my feature works
  • I have added, or updated, mermaid.js diagrams in the corresponding README(s)
  • I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

@bryanchriswhite bryanchriswhite added the tooling tooling to support development, testing et al label Mar 15, 2023
@bryanchriswhite bryanchriswhite self-assigned this Mar 15, 2023
@bryanchriswhite bryanchriswhite mentioned this pull request Mar 15, 2023
16 tasks
@bryanchriswhite bryanchriswhite merged commit 519b188 into main Mar 17, 2023
@bryanchriswhite bryanchriswhite deleted the chore/review-godoc branch March 17, 2023 08:01
bryanchriswhite added a commit that referenced this pull request Mar 20, 2023
* pokt/main:
  [Libp2p] post-merge review improvements (#590)
  Add call # to devlog4.md title
  chore: add `godoc` comment requirement (#587)
dylanlott pushed a commit that referenced this pull request Mar 24, 2023
## Description

Help us bootstrap and subsequently maintain `godoc` comments in the
codebase via our existing review process.

## Issue


![image](https://user-images.githubusercontent.com/600733/225296249-874df9df-45fc-4f08-9df2-9e90d8f4fcc6.png)

## Type of change

Please mark the relevant option(s):

- [ ] New feature, functionality or library
- [ ] Bug fix
- [ ] Code health or cleanup
- [ ] Major breaking change
- [ ] Documentation
- [x] Other: Tooling

## List of changes

- Adds an item to the "Required Checklist" in the PR template

## Next Steps

I'm extremely confident that we could automate these checks with the
correct linter / config. At that point, we could remove this checklist
item.

## Testing

- [ ] `make develop_test`
- [ ]
[LocalNet](https://github.com/pokt-network/pocket/blob/main/docs/development/README.md)
w/ all of the steps outlined in the `README`

## Required Checklist

- [x] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have added, or updated, [`godoc` format
comments](https://go.dev/blog/godoc) on touched members (see:
[tip.golang.org/doc/comment](https://tip.golang.org/doc/comment))
- [ ] I have tested my changes using the available tooling
- [ ] I have updated the corresponding CHANGELOG

### If Applicable Checklist

- [ ] I have updated the corresponding README(s); local and/or global
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I have added, or updated,
[mermaid.js](https://mermaid-js.github.io) diagrams in the corresponding
README(s)
- [ ] I have added, or updated, documentation and
[mermaid.js](https://mermaid-js.github.io) diagrams in `shared/docs/*`
if I updated `shared/*`README(s)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling tooling to support development, testing et al
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants