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

PR2 Konkurs na luchshuyu statyu 2025 #112

Merged
merged 7 commits into from
Jan 16, 2025
Merged

Conversation

dnnik
Copy link
Contributor

@dnnik dnnik commented Jan 16, 2025

Описание изменения

Чеклист ревью

Перед мержем не забудь проверить:

  • правописание в тексте, опечатки

Опционально (но важно для изменений в инфраструктуру):

  • задеплоить на stage, чтобы проверить, что все работает

Summary by CodeRabbit

  • New Content
    • Added a new page for the 2025 Wiren Board Article Competition
    • Detailed competition rules and guidelines for participation
    • Specified voting process and prize categories
    • Provided submission instructions and publication platforms

@dnnik dnnik requested a review from a team as a code owner January 16, 2025 13:21
Copy link
Contributor

coderabbitai bot commented Jan 16, 2025

Walkthrough

A new Russian-language markdown file has been created to announce a competition for the best article about Wiren Board devices. The document outlines a competition running from January 17 to April 17, where participants are invited to write articles about Wiren Board equipment. The competition involves two voting stages, with Dmitry Ustalov selecting six winners across Pro and DIY categories. Winners will receive prizes including equipment certificates, controllers, and branded merchandise.

Changes

File Change Summary
content/ru/pages/konkurs_na_luchshuyu_statyu_2025.md New file created for Wiren Board article competition, detailing participation rules, voting process, and prizes

Possibly related PRs

Suggested reviewers

  • aadegtyarev

Poem

🐰 Hop into the Wiren Board quest,
Where tech tales put skills to the test!
Write your story, let creativity soar,
Prizes await behind innovation's door!
A rabbit's challenge, both Pro and DIY,
Let your article make the judges sigh! 🖥️


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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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.

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: 1

🧹 Nitpick comments (1)
content/ru/pages/konkurs_na_luchshuyu_statyu_2025.md (1)

21-25: Standardize unordered list style.

For consistency with markdown style guidelines, replace dashes with asterisks in the unordered list.

 Как сделать статью заметнее среди остальных: 
-- максимально использовать возможности оборудования Wiren Board;
-- предлагать хитроумные технические решения;
-- делиться фотографиями красивых щитов; 
-- не забывать про юмор.
+* максимально использовать возможности оборудования Wiren Board;
+* предлагать хитроумные технические решения;
+* делиться фотографиями красивых щитов; 
+* не забывать про юмор.
🧰 Tools
🪛 Markdownlint (0.37.0)

22-22: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


23-23: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


24-24: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


25-25: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 8c7a142 and ee23592.

⛔ Files ignored due to path filters (1)
  • public/img/pages/konkurs_na_luchshuyu_statyu_2025/1.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • content/ru/pages/konkurs_na_luchshuyu_statyu_2025.md (1 hunks)
🧰 Additional context used
🪛 Markdownlint (0.37.0)
content/ru/pages/konkurs_na_luchshuyu_statyu_2025.md

22-22: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


23-23: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


24-24: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)


25-25: Expected: asterisk; Actual: dash
Unordered list style

(MD004, ul-style)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Codacy Static Code Analysis
🔇 Additional comments (3)
content/ru/pages/konkurs_na_luchshuyu_statyu_2025.md (3)

1-3: LGTM! Frontmatter is properly formatted.


11-14: Verify external links accessibility.

Please ensure that both the Google Form and Telegram channel links are:

  1. Accessible from all regions
  2. Have appropriate permissions set
  3. Will remain valid throughout the competition period
✅ Verification successful

External links verified successfully

Both the Google Form and Telegram channel links are properly configured and publicly accessible.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the links are accessible
curl -I "https://docs.google.com/forms/d/e/1FAIpQLSc-5XPtP3lavkQ1X8ChxqGwfLg3IpJ1Hi2DUA49VmE2limMOw/viewform"
curl -I "https://t.me/wirenboard_official"

Length of output: 4845


6-6: Verify that the referenced image exists.

Ensure the competition banner image is present in the repository.

✅ Verification successful

Image path verification successful

The referenced image exists at the correct location in the repository.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check if the image file exists
fd "1.png" "img/pages/konkurs_na_luchshuyu_statyu_2025"

Length of output: 183


Script:

#!/bin/bash
# Search for any files/dirs containing the competition name
fd "konkurs_na_luchshuyu_statyu_2025"

# Search for any PNGs in the entire repo
fd -e png

Length of output: 4506

content/ru/pages/konkurs_na_luchshuyu_statyu_2025.md Outdated Show resolved Hide resolved
@dnnik dnnik merged commit 326a3b0 into main Jan 16, 2025
3 checks passed
@dnnik dnnik deleted the konkurs_na_luchshuyu_statyu_2025 branch January 16, 2025 14:13
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.

2 participants