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

wiki/projects: add envdoc documentation tool #8

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

g4s8
Copy link
Contributor

@g4s8 g4s8 commented Feb 8, 2024

Add envdoc go generator tool which can extract documentation for environment variables from go source files and build Markdown, HTML and plaintext documents. Already added to awesome-go repo: avelino/awesome-go@768d097

Add `envdoc` go generator tool which can extract documentation for environment variables from go source files and build Markdown, HTML and plaintext documents. Already added to awesome-go repo: avelino/awesome-go@768d097
@gopherbot
Copy link

This PR (HEAD: 98ce757) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/wiki/+/562218.

Important tips:

  • Don't comment on this PR. All discussion takes place in Gerrit.
  • You need a Gmail or other Google account to log in to Gerrit.
  • To change your code in response to feedback:
    • Push a new commit to the branch used by your GitHub PR.
    • A new "patch set" will then appear in Gerrit.
    • Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
    • Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
    • Multiple commits in the PR will be squashed by GerritBot.
  • The title and description of the GitHub PR are used to construct the final commit message.
    • Edit these as needed via the GitHub web interface (not via Gerrit or git).
    • You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
  • See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants