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

Add python script to update static tech docs #3933

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

Universal-Omega
Copy link
Member

@Universal-Omega Universal-Omega commented Sep 17, 2024

Summary by CodeRabbit

  • New Features

    • Introduced a new script to automate the fetching and updating of technical documentation from MediaWiki to Markdown files in a GitHub repository.
    • Supports conversion of wikitext to Markdown, maintaining original content structure and formatting.
    • Automatically manages file synchronization, including deletion of outdated files and committing changes to GitHub.
  • Enhancements

    • Improved documentation workflow by ensuring the latest content is readily available in a user-friendly format.

Copy link
Contributor

coderabbitai bot commented Sep 17, 2024

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

The pull request introduces a new script, techdocs.py, which automates the process of fetching, converting, and updating technical documentation from a MediaWiki instance into Markdown files for a GitHub repository. It includes functions to retrieve pages, convert wikitext to Markdown, manage file existence, and handle Git operations, ensuring synchronization between MediaWiki and GitHub.

Changes

File Path Change Summary
modules/mediawiki/files/bin/techdocs.py Added multiple functions: fetch_tech_pages, fetch_page_content, convert_wikitext_to_markdown, clean_markdown, file_exists_case_insensitive, update_local_repo, ensure_sub_directory, write_content_to_file, delete_files_not_in_pages, commit_and_push_changes, and mirror_tech_pages_to_github.

Poem

In the garden of code, a new script does bloom,
Fetching pages with ease, dispelling the gloom.
Markdown files dance, in a GitHub embrace,
Syncing knowledge with grace, at a rapid pace.
Hoppy changes abound, let the documentation flow,
A rabbit's delight in the techdocs' glow! 🐰✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    -- I pushed a fix in commit <commit_id>, please review it.
    -- Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    -- @coderabbitai generate unit testing code for this file.
    -- @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    -- @coderabbitai read src/utils.ts and generate unit testing code.
    -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@Universal-Omega
Copy link
Member Author

@coderabbitai review

Copy link
Contributor

coderabbitai bot commented Sep 17, 2024

Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 5

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4bae14d and a1b4f23.

Files selected for processing (1)
  • modules/mediawiki/files/bin/techdocs.py (1 hunks)
Additional context used
Ruff
modules/mediawiki/files/bin/techdocs.py

44-44: Loop control variable page_id not used within loop body

Rename unused page_id to _page_id

(B007)

Additional comments not posted (1)
modules/mediawiki/files/bin/techdocs.py (1)

52-66: Function fetch_page_content implemented correctly

The function properly retrieves wikitext content for a given page title using the MediaWiki API, handling HTTP errors appropriately.

Comment on lines 68 to 359
no_space_after = (',', ';', ':', '(', '[', '{', '-', '_')

if not current_line.endswith(no_space_after) and not current_line.endswith(' '):
current_line += ' '

anchor_replacements = {
'.28': '',
'.29': '',

'(': '',
')': '',
'?': '',
'!': '',
':': '',
'/': '',
'.': '',
',': '',
'"': '',
"'": '',
'_': '-',
' ': '-',
}

if target.startswith('#'):
# Anchor link
anchor = target
for old, new in anchor_replacements.items():
anchor = anchor.replace(old, new)
anchor = anchor.lower()
current_line += f'[{label}]({anchor})'
else:
if '#' in target:
# Anchor link
base_title, anchor = target.split('#', 1)
else:
base_title, anchor = target, None

formatted_title = base_title.replace(' ', '_').replace('/', '-')
local_file_path = os.path.join(ensure_sub_directory(), f'{formatted_title}.md')

# Case-insensitive file existence check
if file_exists_case_insensitive(local_file_path):
# If the local file exists, use the local markdown link
formatted_url = f"/tech-docs/{formatted_title.replace(':', '').lower()}"

# Append anchor if it exists
if anchor:
for old, new in anchor_replacements.items():
anchor = anchor.replace(old, new)
anchor = anchor.lower()
formatted_url += f'#{anchor}'

# Add the final link
current_line += f'[{label}]({formatted_url})'
else:
# Otherwise, link to Miraheze
if is_category:
# Use a new section with a list for categories
if is_first_category:
if current_line:
markdown_lines.append(current_line.strip())
current_line = ''
markdown_lines.append('## Categories\n')
is_first_category = False
current_line += '* '
current_line += f"[{label}](https://meta.miraheze.org/wiki/{target.replace(' ', '_')})"

elif isinstance(node, mwparserfromhell.nodes.Comment):
if current_line:
markdown_lines.append(current_line.strip())
current_line = ''

if '<!--T:' not in str(node):
markdown_lines.append(f'\n{str(node).strip()}\n')

elif isinstance(node, mwparserfromhell.nodes.Template):
if current_line:
markdown_lines.append(current_line.strip())
current_line = ''

# Keep templates intact in Markdown
if '\n' in str(node):
markdown_lines.append(f'```\n{{{{ {node} }}}}\n```')
elif 'tech navigation' in str(node).lower() or 'hatnote' in str(node).lower():
markdown_lines.append(f'\n`{{{{ {node} }}}}`')
else:
current_line += f'`{{{{ {node} }}}}`'

elif isinstance(node, mwparserfromhell.nodes.HTMLEntity):
current_line += str(node)

else:
current_line += str(node)

# Flush any remaining inline content to markdown_lines
if current_line:
markdown_lines.append(current_line.strip())

return clean_markdown(markdown_lines)

Copy link
Contributor

Choose a reason for hiding this comment

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

Consider refactoring convert_wikitext_to_markdown for improved maintainability

The convert_wikitext_to_markdown function is lengthy and complex, spanning nearly 300 lines. Refactoring it into smaller, modular functions can enhance readability, make it easier to test, and improve maintainability. Separating the handling of different node types or processing steps into individual functions would adhere to the Single Responsibility Principle.

Comment on lines +432 to +438
def update_local_repo():
if not os.path.exists(LOCAL_REPO_PATH):
Repo.clone_from(GITHUB_REPO_URL, LOCAL_REPO_PATH)
else:
repo = Repo(LOCAL_REPO_PATH)
repo.git.pull()

Copy link
Contributor

Choose a reason for hiding this comment

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

Enhance error handling for Git operations

The update_local_repo function performs Git operations without error handling. If repo.git.pull() encounters issues such as merge conflicts or network errors, the script may terminate unexpectedly. Adding try-except blocks around Git commands can help handle exceptions gracefully and improve the script's robustness.

Comment on lines +472 to +478
def commit_and_push_changes():
repo = Repo(LOCAL_REPO_PATH)
repo.git.add(A=True) # Add all changes
commit_message = f'Auto-update Tech namespace pages {datetime.now()}'
repo.index.commit(commit_message)
origin = repo.remote(name='origin')
origin.push()
Copy link
Contributor

Choose a reason for hiding this comment

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

Add error handling for Git operations

Currently, the Git operations in commit_and_push_changes lack error handling. If the push fails (e.g., due to non-fast-forward updates or network errors), the script may crash without a clear error message. Consider adding try-except blocks around Git commands to handle exceptions gracefully and provide informative feedback.

Comment on lines 481 to 494
def mirror_tech_pages_to_github():
print('Fetching Tech namespace pages...')
pages = fetch_tech_pages()
update_local_repo() # Clone or pull latest changes
delete_files_not_in_pages(pages) # Delete old files not present in API response
for page in pages:
title = page['title']
print(f'Processing page: {title}')
content = fetch_page_content(title)
markdown_content = convert_wikitext_to_markdown(content)
write_content_to_file(title, markdown_content)
commit_and_push_changes()
print('Successfully updated GitHub repository.')

Copy link
Contributor

Choose a reason for hiding this comment

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

Implement exception handling in the mirroring process

To enhance the robustness of the script, consider adding exception handling within the mirror_tech_pages_to_github function. If an error occurs while processing a page (e.g., network issue, parsing error), handling the exception can prevent the entire script from terminating prematurely and allow processing of the remaining pages.

modules/mediawiki/files/bin/techdocs.py Outdated Show resolved Hide resolved
Universal-Omega and others added 2 commits September 17, 2024 12:33
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant