Skip to content

Documentation updates and reformatting - #106

Merged
Gogotchuri merged 2 commits into
mainfrom
doc_rewrite
Aug 5, 2025
Merged

Documentation updates and reformatting#106
Gogotchuri merged 2 commits into
mainfrom
doc_rewrite

Conversation

@Gogotchuri

Copy link
Copy Markdown
Contributor

This PR updates documentation to match the current version of the repository.
And reformats all of the documents to a newer markdown standard.

Resolves #51
Resolves #99

Checklist

  • I have read the contribution guide.
  • I have not used an AI coding assistant to create this PR.
  • I have written all code in this PR myself OR I have marked all code I have not written myself (including modified code, e.g. copied from other places and then modified) with a comment indicating where it came from.
  • I (and other contributors to this PR) have not looked at the Terraform source code while implementing this PR.
  • If I'm releasing, I have read the releasing guide.

Go checklist

  • I have run golangci-lint on my change and receive no errors relevant to my code.
  • I have run existing tests to ensure my code doesn't break anything.
  • I have added tests for all relevant use cases of my code, and those tests are passing.
  • I have only exported functions, variables and structs that should be used from other packages.
  • I have added meaningful comments to all exported functions, variables, and structs.

Signed-off-by: Ilia Gogotchuri <ilia.gogotchuri0@gmail.com>
Signed-off-by: Ilia Gogotchuri <ilia.gogotchuri0@gmail.com>
@Gogotchuri
Gogotchuri marked this pull request as ready for review August 2, 2025 16:38
@Gogotchuri
Gogotchuri requested a review from a team as a code owner August 2, 2025 16:38
@tzabbi

tzabbi commented Aug 4, 2025

Copy link
Copy Markdown
Contributor

Do you want to add a github job to lint over the markdown files?

@Gogotchuri

Copy link
Copy Markdown
Contributor Author

@tzabbi Good idea.
I would prefer it to be less invasive. We can create a workflow to check if markdown files are linted correctly and return an error otherwise. Let's leave it to the contributor to sort the linting part themselves. I would also prefer the check to be non-mandatory.

@diofeher

diofeher commented Aug 5, 2025

Copy link
Copy Markdown
Member

@Gogotchuri Agreed. Just checking would be enough.

@diofeher diofeher left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for doing this work, Ilia! Good call on removing the Sublime Text stuff.

@Gogotchuri
Gogotchuri merged commit f9e700f into main Aug 5, 2025
23 of 24 checks passed
@Gogotchuri
Gogotchuri deleted the doc_rewrite branch August 5, 2025 13:48
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.

Markdown Linter Documentation needs to be rewritten

4 participants