Skip to content

docs: use repo icon and Pipery org avatar in README#5

Merged
hbahadorzadeh merged 1 commit intomainfrom
docs/readme-icons
Apr 28, 2026
Merged

docs: use repo icon and Pipery org avatar in README#5
hbahadorzadeh merged 1 commit intomainfrom
docs/readme-icons

Conversation

@hbahadorzadeh
Copy link
Copy Markdown
Contributor

Replace generic Feather icon SVGs with repo-specific assets/icon.png and Pipery org avatar.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@hbahadorzadeh hbahadorzadeh merged commit fd357b5 into main Apr 28, 2026
@hbahadorzadeh hbahadorzadeh deleted the docs/readme-icons branch April 28, 2026 18:06
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the README.md to replace generic icons with Pipery-branded assets. The review feedback recommends using relative paths for local assets to ensure they render correctly across branches and suggests using a vanity URL for the GitHub avatar to improve code readability and maintainability.

Comment thread README.md
@@ -1,4 +1,4 @@
# <img src="https://raw.githubusercontent.com/feathericons/feather/master/icons/code.svg" width="28" align="center" /> Pipery Python CI
# <img src="https://raw.githubusercontent.com/pipery-dev/pipery-python-ci/main/assets/icon.png" width="28" align="center" /> Pipery Python CI
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

Using a relative path for the repository icon is preferred over a hardcoded absolute URL pointing to the main branch. This ensures the icon renders correctly across different branches and forks, and remains functional if the default branch name is changed.

Suggested change
# <img src="https://raw.githubusercontent.com/pipery-dev/pipery-python-ci/main/assets/icon.png" width="28" align="center" /> Pipery Python CI
# <img src="assets/icon.png" width="28" align="center" /> Pipery Python CI

Comment thread README.md
## About Pipery

<img src="https://raw.githubusercontent.com/feathericons/feather/master/icons/zap.svg" width="18" align="center" /> [**Pipery**](https://pipery.dev) is an open-source CI/CD observability platform. Every step script runs under **psh** (Pipery Shell), which intercepts all commands and emits structured JSONL events — giving you full visibility into your pipeline without any manual instrumentation.
<img src="https://avatars.githubusercontent.com/u/270923927?s=32" width="22" align="center" /> [**Pipery**](https://pipery.dev) is an open-source CI/CD observability platform. Every step script runs under **psh** (Pipery Shell), which intercepts all commands and emits structured JSONL events — giving you full visibility into your pipeline without any manual instrumentation.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

The avatar URL uses a hardcoded numeric user ID. Using the organization's vanity URL (e.g., https://github.com/pipery-dev.png) is more readable and maintainable, as it clearly identifies the organization in the source code.

Suggested change
<img src="https://avatars.githubusercontent.com/u/270923927?s=32" width="22" align="center" /> [**Pipery**](https://pipery.dev) is an open-source CI/CD observability platform. Every step script runs under **psh** (Pipery Shell), which intercepts all commands and emits structured JSONL events — giving you full visibility into your pipeline without any manual instrumentation.
<img src="https://github.com/pipery-dev.png?s=32" width="22" align="center" /> [**Pipery**](https://pipery.dev) is an open-source CI/CD observability platform. Every step script runs under **psh** (Pipery Shell), which intercepts all commands and emits structured JSONL events — giving you full visibility into your pipeline without any manual instrumentation.

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.

1 participant