Rename webhook_server_container->webhook_server

[myakove]

Summary by CodeRabbit

• Refactor

  • Updated all references from the old package and directory name to the new, consistent naming throughout the application, configuration, and test files.
  • Adjusted import paths and environment variables to match the new structure.
  • Improved style and formatting in configuration files for consistency.

• Chores

  • Updated configuration and test settings to align with the new package structure.

[myakove-bot]

Report bugs in Issues

The following are automatically added:

• Add reviewers from OWNER file (in the root of the repository) under reviewers section.
• Set PR size label.
• New issue is created for the PR. (Closed when PR is merged/closed)
• Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

• To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
• To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
• To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
  verified label removed on each new commit push.
• To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.
  • Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
  • Cherry-pick will be started when PR is merged
• To build and push container image command /build-and-push-container in the PR (tag will be the PR number).
  • You can add extra args to the Podman build command
    • Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>
• To add a label by comment use /<label name>, to remove, use /<label name> cancel
• To assign reviewers based on OWNERS file use /assign-reviewers
• To check if PR can be merged use /check-can-merge
• to assign reviewer to PR use /assign-reviewer @<reviewer>

PR will be approved when the following conditions are met:

• /approve from one of the approvers.
• Minimum number of required /lgtm (2) is met.

Approvers and Reviewers

• Approvers:

  • myakove
  • rnetser

• Reviewers:

  • myakove
  • rnetser

Supported /retest check runs

• /retest tox: Retest tox
• /retest build-container: Retest build-container
• /retest python-module-install: Retest python-module-install
• /retest pre-commit: Retest pre-commit
• /retest all: Retest all

Supported labels

• hold
• verified
• wip
• lgtm
• approve

[coderabbitai]

Caution

Review failed

The pull request is closed.

"""

Walkthrough

This change updates the project structure and module references by renaming all instances of the webhook_server_container directory and module path to webhook_server. All import statements, environment variables, configuration files, and test references have been modified to align with this new naming convention. No functional or logic changes are introduced; the updates are limited to paths, import statements, and related configuration adjustments to reflect the new module name.

Changes

Files/Paths	Change Summary
Dockerfile, entrypoint.sh, example.config.yaml, pyproject.toml, pytest.ini, tox.toml	All references to webhook_server_container changed to webhook_server in paths, configs, and env.
webhook_server/app.py, webhook_server/libs/config.py, webhook_server/libs/github_api.py	Import paths updated from webhook_server_container to webhook_server.
webhook_server/utils/github_repository_and_webhook_settings.py, webhook_server/utils/github_repository_settings.py, webhook_server/utils/helpers.py, webhook_server/utils/webhook.py	Import paths updated from webhook_server_container to webhook_server.
webhook_server/tests/conftest.py, webhook_server/tests/test_branch_protection.py, webhook_server/tests/test_pull_request_owners.py, webhook_server/tests/test_pull_request_size.py	Test imports and environment variables updated to use webhook_server paths.

Possibly related PRs

• Fix no owners for subfolders #639: Updates internal logic and type annotations in ProcessGithubWehook within github_api.py; related at module level but does not overlap in import path changes.
• Rename webhook_server_container->webhook_server - 733 #734: This PR directly addresses the objective of renaming webhook_server_container to webhook_server across the codebase.

Suggested labels

size/XS, verified, can-be-merged, commented-coderabbitai[bot]

Suggested reviewers

• rnetser
  """

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 65d8065 and 12f414e.

📒 Files selected for processing (17)

• Dockerfile (1 hunks)
• entrypoint.sh (1 hunks)
• example.config.yaml (1 hunks)
• pyproject.toml (5 hunks)
• pytest.ini (1 hunks)
• tox.toml (1 hunks)
• webhook_server/app.py (1 hunks)
• webhook_server/libs/config.py (1 hunks)
• webhook_server/libs/github_api.py (2 hunks)
• webhook_server/tests/conftest.py (2 hunks)
• webhook_server/tests/test_branch_protection.py (1 hunks)
• webhook_server/tests/test_pull_request_owners.py (1 hunks)
• webhook_server/tests/test_pull_request_size.py (1 hunks)
• webhook_server/utils/github_repository_and_webhook_settings.py (1 hunks)
• webhook_server/utils/github_repository_settings.py (2 hunks)
• webhook_server/utils/helpers.py (1 hunks)
• webhook_server/utils/webhook.py (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

[myakove-bot]

New container for ghcr.io/myk-org/github-webhook-server:latest published