Skip to content

docs: remove private files in doc build#829

Merged
sesmart merged 9 commits intoamazon-braket:mainfrom
sesmart:doc--adjust-private-public
Feb 13, 2026
Merged

docs: remove private files in doc build#829
sesmart merged 9 commits intoamazon-braket:mainfrom
sesmart:doc--adjust-private-public

Conversation

@sesmart
Copy link
Copy Markdown
Contributor

@sesmart sesmart commented Feb 4, 2026

Issue #, if available:

Close #828; also improves doc testing

Description of changes:

Removed non-user generated files from docs/; changed some private vs public naming to avoid confusion. All public .md files can be edited and will not be overwritten, except for README.md.

Furthermore, we now have a test that the current README generated file is the same as the previous one. This helps testing when it should have been run and it was not, or if users tried to build the README.


By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@sesmart sesmart requested a review from speller26 February 4, 2026 16:25
@sesmart sesmart requested a review from a team as a code owner February 4, 2026 16:25
@sesmart sesmart changed the title docs: remove created files in doc build; fixed private vs public docs: remove private files in doc build Feb 4, 2026
with open("docs/_NOTEBOOKS.md",'w') as fp:
fp.write(main_body)
print("docs/_NOTEBOOK.md updated!")
return main_body
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.

Why do this and the next file need this new return line?

Copy link
Copy Markdown
Contributor Author

@sesmart sesmart Feb 5, 2026

Choose a reason for hiding this comment

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

This is so you can test the output here (see test_matching_README) - the README is the one public file that should not be modified directly. Q generally is how to prevent that.

In this PR, this test tries to check that. You also could (1) move the build script to python and just have everything be in python, or (2) have a more complex build_readme.sh, that can write to other locations and do cleanup, but this seemed simple enough as we were already verifying that the index and notebook entries build okay.

@sesmart sesmart requested a review from speller26 February 5, 2026 18:05
@sesmart sesmart merged commit a4a16ac into amazon-braket:main Feb 13, 2026
9 checks passed
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.

docs: delete temp _entries.md + _index.md

2 participants