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

Schema4.5 #57

Open
wants to merge 4 commits into
base: develop
Choose a base branch
from
Open

Schema4.5 #57

wants to merge 4 commits into from

Conversation

tedhabermann
Copy link

I checked the build from the last metadata.rst file and it looked fine. I thought one of the links might be bad, but I tested them all. I made a couple of other changes in this branch, adding to the originals.

Checking for a syntax problem - but could not find any. The build from the first file I sent looks good, i.e. no errors. This branch includes those changes.
Trying to fix rst errors. Many lines with blanks on the end, lines too long, bad targets. It seems there must be a space before the url in links.
Trying to fix too long lines and trailing blanks...
@tedhabermann tedhabermann reopened this Oct 3, 2024
@tedhabermann
Copy link
Author

Looks like all checks have passed!

@RKrahl RKrahl self-requested a review October 29, 2024 10:07
@RKrahl RKrahl added the add content Suggestion to add new content not yet covered label Oct 30, 2024
@RKrahl RKrahl added this to the 1.0 milestone Oct 30, 2024
@RKrahl RKrahl mentioned this pull request Oct 30, 2024
Copy link
Member

@RKrahl RKrahl left a comment

Choose a reason for hiding this comment

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

Normally, it is best practice to clearly separate the roles: one proposes changes, another one reviews the proposal. But here, my review need to go deep into technical and formal details, including reStructuredText syntax errors. In this case, it is much easier to do the changes myself right away, rather than to explain them verbally.

Therefore, I submitted another PR #59 to amend your proposal. See that PR for a detailed list of changes. You may review the change in the rendered results by comparing your version with the updated version. @tedhabermann, please let me know if you are happy with these changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
add content Suggestion to add new content not yet covered
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants