makerspace / makeradmin

Stockholm Makerspace member administration and store.
https://docs.makeradmin.se/
21 stars 16 forks source link

moved mkdocs.yml to the docs directory #557

Closed Lescurel closed 1 month ago

Lescurel commented 1 month ago

Summary by CodeRabbit

coderabbitai[bot] commented 1 month ago

Walkthrough

The pull request introduces several changes aimed at enhancing the documentation workflow using MkDocs. Key modifications include updates to the GitHub Actions workflow for publishing documentation, the addition of a Dockerfile for a Python environment, and changes to the .gitignore and Makefile to accommodate new documentation build processes. Additionally, configuration files have been updated to define output and source directories, and a new domain entry has been added for the documentation site.

Changes

File Change Summary
.github/workflows/documentation.yml Updated workflow triggers, build command, and job dependencies for documentation publishing.
.gitignore Added site/ directory to be ignored.
Makefile Added dev-docs target for building and serving documentation; corrected indentation for dev-test.
docs/CNAME Deleted file specifying the custom domain.
docs/Dockerfile Introduced a Dockerfile for setting up a Python environment for MkDocs.
docs/mkdocs.yml Modified to include site_dir and docs_dir, and corrected indentation in the navigation structure.
docs/requirements.txt Added dependency for mkdocs==1.6.1.
docs/src/CNAME Added custom domain docs.makeradmin.se for the documentation site.

Possibly related PRs

Suggested reviewers

Poem

πŸ‡ In the garden where the docs do grow,
A new path for publishing, now we know.
With Docker and MkDocs, our work's a delight,
A hop and a skip, our docs shine bright!
So let’s raise a cheer, for the changes today,
For a clearer, smoother, documentation way! 🌼


πŸ“œ Recent review details **Configuration used: CodeRabbit UI** **Review profile: CHILL**
πŸ“₯ Commits Files that changed from the base of the PR and between 92615cd036b5f3eac85576b1d035dce2c4d0125c and 07f605f6c3c39232e5c16876e684419580b689c3.
πŸ“’ Files selected for processing (1) * update-docker-images.sh (1 hunks)
🧰 Additional context used
πŸ““ Learnings (1)
update-docker-images.sh (1)
``` Learnt from: emanuelen5 PR: makerspace/makeradmin#552 File: update-docker-images.sh:38-43 Timestamp: 2024-10-05T17:06:02.618Z Learning: Within the `update_all_refs_to_latest_digest` function in `update-docker-images.sh`, the list of files to update should remain hard-coded because the images and tags are strictly correlated to the source code and update files in the source tree. ```
πŸ”‡ Additional comments (1)
update-docker-images.sh (1)
`42-42`: **LGTM! Addition of docs/Dockerfile is appropriate.** The inclusion of `docs/Dockerfile` in the list of files to update is consistent with the PR objective of moving the documentation setup to the `docs` directory. This change ensures that the Docker image digest in the new `docs/Dockerfile` will be updated along with other Dockerfiles and the docker-compose.yml file. This modification maintains the practice of hard-coding the list of files to update, which is appropriate as these files are directly correlated with the source code and update processes.
--- 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 - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
πŸͺ§ Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.