Skip to content

Update README.md - #747

Open
Sal-ami wants to merge 1 commit into
KrisTHL181:mainfrom
Sal-ami:main
Open

Sal-ami wants to merge 1 commit into
KrisTHL181:mainfrom
Sal-ami:main

Conversation

@Sal-ami

@Sal-ami Sal-ami commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

🔥🔞🔞🔞 你对 Break-This-Repo 干了吗 🔞🔞🔞🔥

🔞想打炮🔥,打飞机🔥,打手枪🔥

🔞血与肉的碰撞,声声入耳的叫声🔥

🔞这是灵魂的碰撞,更是对自己意志的磨炼🔥

🔞别害羞,深夜寂寞是时候来点热血的🔥

🔞体会真男人一样激烈的战斗🔥

🔞前往此网站🔥

🔞点我前往🔞🔞🔞🔥

🔞备用线路🔞🔞🔞🔥

🔞未成年无法参加🔞

img

@github-actions

Copy link
Copy Markdown
Contributor

🔀 This PR has merge conflicts with main, so auto-merge can't apply it yet.

No need to reopen or do anything drastic — just update the branch (merge or rebase main into it, resolving the conflict). Once it merges cleanly, it will be merged automatically.

@github-actions github-actions Bot added the conflict Merge conflict; resolves itself once fixed label Sep 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

🔒 Auto-merge can't apply this PR yet — and it's nothing you did.

The merge API refuses the automation's token: Resource not accessible by integration (HTTP 403). It is not a merge conflict, and there is nothing wrong with your diff — it would apply unchanged.

Workaround: update the branch so it contains main's latest commits — that has cleared this for at least one PR. If it doesn't help, this is an open issue on our side, not yours; sorry for the friction.

@github-actions github-actions Bot added the merge-blocked Merge rejected by the API; will not clear on its own label Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conflict Merge conflict; resolves itself once fixed merge-blocked Merge rejected by the API; will not clear on its own

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant