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

wechaty-with-aws2024 #184

Merged
merged 6 commits into from
Apr 25, 2024
Merged

wechaty-with-aws2024 #184

merged 6 commits into from
Apr 25, 2024

Conversation

AIAmber
Copy link
Member

@AIAmber AIAmber commented Apr 24, 2024

Please make sure to check the following boxes creating your pull request, thank you very much!

  • Add Blog Header, including title, author, image, categories, tags, etc.

    For example:

    ---
    title: Your Great Blog Title
    author: your_github_id
    categories: project
    tags:
      - python
      - padlocal
    image: /assets/2021/02-your-blog-slug/teaser.jpg
    ---
    
    One line bio
    
    Your blog post content Your blog post content
    Your blog post content Your blog post content
    Your blog post content Your blog post content

    It will be easier to start drafting your post by using a existing post file as your template, for example, this one

  • Keep all filenames lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor.md instead of 2017-10-06-WeChat PC Impactor.md

  • Embed video/pdf from YouTube/Bilibili/local (if there's any) by using {% include iframe.html src="URL_or_PATH" %}. (Learn more about how to embed file/url in the post by reading this blog post

  • Save photo to local before publishing, to a folder named by ${MONTH}-${YOUR_BLOG_SLUG}/ under /assets/2021/ directory.

  • Select a beautiful and meaningful teaser image for your blog

  • Create your contributor profile (if you are a first time contributor)

    For excample:

    jekyll/_contributors/lijiarui.md

    ---
    name: Jiarui LI (李佳芮)
    site: https://lijiarui.github.io
    bio: 句子互动创始人 & CEO,微软人工智能最具价值专家 (AI MVP)
    avatar: /jekyll/assets/contributors/lijiarui/avatar.png
    email: [email protected]
    twitter: https://weibo.com/u/2175505900
    ---

    Here is the example file:

To learn more about the contribute guideline, visit: https://wechaty.js.org/docs/contributor-program/

Summary by CodeRabbit

  • Documentation
    • Updated blog post on the "China Generative AI Innovation Application Challenge," to highlight the second edition of the competition, collaboration details, participation guidelines, objectives, structure, and rewards. Includes registration links for developers and entrepreneurs.

Copy link

coderabbitai bot commented Apr 24, 2024

Walkthrough

The new post introduces the "China Generative AI Innovation Application Challenge," emphasizing the second edition of the competition in collaboration with various entities. It invites developers and entrepreneurs to participate in creating innovative generative AI applications, providing details on competition themes, stages, and registration information.

Changes

File Path Change Summary
jekyll/_posts/2024-04-25-wechaty-with-aws2024.md New post on the China Generative AI Innovation Application Challenge

🐇✨
In the realm of AI, a challenge awaits,
Where minds converge and innovate,
Generative dreams take flight,
In the glow of digital light.
Join the quest, let creativity soar,
To build a future like never before.
🌟🚀


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 77b975c and d9596e8.
Files selected for processing (1)
  • jekyll/_posts/2024-04-25-wechaty-with-aws2024.md (1 hunks)
Additional Context Used
LanguageTool (1)
jekyll/_posts/2024-04-25-wechaty-with-aws2024.md (1)

Near line 60: 数量词修饰并列短语,可能产生歧义
Context: ...rs,并被万名Github开发者Star。目前,Wechaty的开发者已遍布全球多个国家和地区,覆盖数万人,是国内最活跃的Conversational AI Chatbot ...

Additional comments not posted (4)
jekyll/_posts/2024-04-25-wechaty-with-aws2024.md (4)

31-31: Ensure there are no trailing spaces at the end of line 31 to maintain clean Markdown syntax.


40-40: Add a blank line above the heading on line 38 to improve readability and adhere to Markdown best practices.


44-44: Add a blank line above the heading on line 41 to improve readability and adhere to Markdown best practices.


48-48: Add a blank line above the heading on line 44 to improve readability and adhere to Markdown best practices.


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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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

@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: 4

@AIAmber
Copy link
Member Author

AIAmber commented Apr 24, 2024

hey @huan, please review this PR, thank you!

@AIAmber
Copy link
Member Author

AIAmber commented Apr 25, 2024

hey @huan, please review it again!

Copy link
Member

@huan huan left a comment

Choose a reason for hiding this comment

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

LGTM

Thank you very much for sharing this great event with the community!

@huan huan merged commit 587c4eb into wechaty:main Apr 25, 2024
3 checks passed
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