c937085 Fix badge placement instructions in PR template
📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝pull_request_template.md (+1 -1)
📄 Description
This PR fixes the contradiction between the pull request template and the awesome-lint tool regarding badge placement.
Problem:
The PR template instructed users to place the Awesome badge 'on the right side of the readme heading'
The awesome-lint tool expects the badge to be placed after the main heading, not inline with it
This was causing linting failures when users followed the PR template instructions
Solution:
Updated the instruction in the PR template to clarify that the badge should be placed after the main heading, which matches both the linter expectations and the guidance in awesome.md.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/sindresorhus/awesome/pull/3969
**Author:** [@tysoncung](https://github.com/tysoncung)
**Created:** 2/28/2026
**Status:** ❌ Closed
**Base:** `main` ← **Head:** `fix-badge-placement-instructions`
---
### 📝 Commits (1)
- [`c937085`](https://github.com/sindresorhus/awesome/commit/c937085ef6081389dc506bafd9bc1a87c38ae13f) Fix badge placement instructions in PR template
### 📊 Changes
**1 file changed** (+1 additions, -1 deletions)
<details>
<summary>View changed files</summary>
📝 `pull_request_template.md` (+1 -1)
</details>
### 📄 Description
This PR fixes the contradiction between the pull request template and the awesome-lint tool regarding badge placement.
**Problem:**
- The PR template instructed users to place the Awesome badge 'on the right side of the readme heading'
- The awesome-lint tool expects the badge to be placed after the main heading, not inline with it
- This was causing linting failures when users followed the PR template instructions
**Solution:**
Updated the instruction in the PR template to clarify that the badge should be placed after the main heading, which matches both the linter expectations and the guidance in awesome.md.
Fixes #2097
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/3969
Author: @tysoncung
Created: 2/28/2026
Status: ❌ Closed
Base:
main← Head:fix-badge-placement-instructions📝 Commits (1)
c937085Fix badge placement instructions in PR template📊 Changes
1 file changed (+1 additions, -1 deletions)
View changed files
📝
pull_request_template.md(+1 -1)📄 Description
This PR fixes the contradiction between the pull request template and the awesome-lint tool regarding badge placement.
Problem:
Solution:
Updated the instruction in the PR template to clarify that the badge should be placed after the main heading, which matches both the linter expectations and the guidance in awesome.md.
Fixes #2097
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.