fix: update contributors image max count to 300#8000
Merged
Conversation
dosubot
Bot
added
the
size:S
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the contributor image URLs across multiple README files to increase the maximum number of displayed contributors from 200 to 210. Feedback was provided regarding the accidental introduction of UTF-8 Byte Order Marks (BOM) at the beginning of several files, which should be removed to ensure compatibility with various tools and parsers.
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Hey - I've found 4 issues, and left some high level feedback:
- In all updated README files, the first line now includes a leading invisible character (likely a BOM or zero-width space) before the image markdown; please remove that character to avoid potential rendering or diff noise issues and adjust your editor settings to prevent reintroducing it.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In all updated README files, the first line now includes a leading invisible character (likely a BOM or zero-width space) before the image markdown; please remove that character to avoid potential rendering or diff noise issues and adjust your editor settings to prevent reintroducing it.
## Individual Comments
### Comment 1
<location path="README.md" line_range="1" />
<code_context>
-
+
</code_context>
<issue_to_address>
**suggestion (bug_risk):** There appears to be an invisible character (likely a BOM) before the `!` at the start of this line.
The new line begins with an unseen zero‑width character before `
```
Ensure the README.md file is saved as UTF-8 **without BOM** in your editor/IDE settings so that this invisible character is not reintroduced on future saves.
</issue_to_address>
### Comment 2
<location path="README_ja.md" line_range="1" />
<code_context>
-
+
<div align="center">
</code_context>
<issue_to_address>
**suggestion (bug_risk):** There looks to be an extra invisible character before the `!` at the beginning of this line.
The `+
```
To fully implement the suggestion:
1. Ensure the file is saved without a UTF-8 BOM (use plain UTF-8) in your editor settings.
2. Verify there are no other invisible characters at the start of the file by reopening and diffing after save.
</issue_to_address>
### Comment 3
<location path="README_ru.md" line_range="1" />
<code_context>
-
+
<div align="center">
</code_context>
<issue_to_address>
**suggestion (bug_risk):** An unexpected invisible character appears before the `!` at the start of this line.
That leading invisible character (likely a BOM/zero-width char) should be removed and the file encoding checked to prevent potential Markdown parsing issues.
```suggestion
```
</issue_to_address>
### Comment 4
<location path="README_zh.md" line_range="1" />
<code_context>
-
+
<div align="center">
</code_context>
<issue_to_address>
**suggestion (bug_risk):** A likely BOM or zero-width character appears before the `!` at the start of this line.
This line starts with `+
```
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
PR AstrBotDevs#8000 follow-up: Sourcery and codereview agent flagged UTF-8 BOM in 6 README files. BOM is unnecessary in UTF-8 and may cause compatibility issues with Markdown parsers.
Contributor
Author
|
@sourcery-ai review |
Soulter
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
修复贡献者图片显示不完整的问题。
问题
当前 max=200&columns=14，200 无法被 14 整除（200 ÷ 14 = 14.28），导致最后一行有一块空白区域未填满。
修复
调整为 max=300&columns=15（300 ÷ 15 = 20），6 个语言版本的 README 均已同步更新。
修改内容
共修改 6 个文件，将所有 max=200&columns=14 替换为 max=300&columns=15。
Summary by Sourcery
Enhancements: