openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

[PR #80] [CLOSED] chore: add github repo banner #250

New Issue
Closed
opened 2026-02-15 17:16:30 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:16:30 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/openclaw/clawhub/pull/80
Author: @warengonzaga
Created: 1/31/2026
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (2)

  • 7b502d4 chore: add github repo banner
  • f877fc2 chore: move the credits to it's own line

📊 Changes

1 file changed (+3 additions, -0 deletions)

View changed files

📝 README.md (+3 -0)

📄 Description

This pull request adds a visual improvement to the project documentation by including a GitHub repository banner in the README.md file.

Documentation update:

  • Added a GitHub Repo Banner image at the top of README.md to enhance the project's visual presentation.

The banner is made using this tool: https://ghrb.waren.build/ (I made it)
Wondering if we can add this to this project to have some good visuals. (Just launched today, yey)

Greptile Overview

Greptile Summary

This PR updates project documentation by adding a GitHub README banner image near the top of README.md (under the existing badges) to improve visual presentation.

The change is isolated to documentation and does not affect runtime code paths or application behavior.

Confidence Score: 4/5

  • This PR is safe to merge; it’s a documentation-only change with low blast radius.
  • The only change is adding a README banner image. Main considerations are long-term reliability/maintainability of a remote, dynamically generated asset and minor markdown rendering portability.
  • README.md (banner hosting/format choice)

(2/5) Greptile learns from your feedback when you react with thumbs up/down!

Context used:

  • Context from dashboard - AGENTS.md (source)

🔄 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/openclaw/clawhub/pull/80 **Author:** [@warengonzaga](https://github.com/warengonzaga) **Created:** 1/31/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (2) - [`7b502d4`](https://github.com/openclaw/clawhub/commit/7b502d466205aa76d469b6ed0b9a6252b46193d3) chore: add github repo banner - [`f877fc2`](https://github.com/openclaw/clawhub/commit/f877fc28a8c723587eb4bb2fe96874aeec9f0c90) chore: move the credits to it's own line ### 📊 Changes **1 file changed** (+3 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+3 -0) </details> ### 📄 Description This pull request adds a visual improvement to the project documentation by including a GitHub repository banner in the `README.md` file. Documentation update: * Added a GitHub Repo Banner image at the top of `README.md` to enhance the project's visual presentation. --- The banner is made using this tool: https://ghrb.waren.build/ (I made it) Wondering if we can add this to this project to have some good visuals. (Just launched today, yey) <!-- greptile_comment --> <h2>Greptile Overview</h2> <h3>Greptile Summary</h3> This PR updates project documentation by adding a GitHub README banner image near the top of `README.md` (under the existing badges) to improve visual presentation. The change is isolated to documentation and does not affect runtime code paths or application behavior. <h3>Confidence Score: 4/5</h3> - This PR is safe to merge; it’s a documentation-only change with low blast radius. - The only change is adding a README banner image. Main considerations are long-term reliability/maintainability of a remote, dynamically generated asset and minor markdown rendering portability. - README.md (banner hosting/format choice) <!-- greptile_other_comments_section --> <sub>(2/5) Greptile learns from your feedback when you react with thumbs up/down!</sub> **Context used:** - Context from `dashboard` - AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=a1d58d20-b4dd-4cbb-973a-9fd7824e1921)) <!-- /greptile_comment --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-15 17:16:30 -05:00
yindo closed this issue 2026-02-15 17:16:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#250
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?