Skip to content

Conversation

@Kuzuri247
Copy link
Contributor

What kind of change does this PR introduce?

This PR fixes the position of the Github logo

Issue Number:

Closes #2073

Screenshots/videos:

Before:

Screenshot 2026-01-08 141945

After:

image

If relevant, did you update the documentation?

No.

Summary

The Github logo is perfectly positioned after implementing the change.

Does this PR introduce a breaking change?

No.

@Kuzuri247 Kuzuri247 requested a review from a team as a code owner January 8, 2026 08:58
@github-project-automation github-project-automation bot moved this to Ready to review in PR - Triage Group Jan 8, 2026
@github-actions
Copy link

github-actions bot commented Jan 8, 2026

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
website ✅ Ready (View Log) Visit Preview d422986

@codecov
Copy link

codecov bot commented Jan 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (2c94143) to head (d422986).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #2074   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           30        30           
  Lines          633       633           
  Branches       196       196           
=========================================
  Hits           633       633           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vtushar06
Copy link
Collaborator

Hi @Kuzuri247, thanks for looking into this.
For future reference, please wait for the maintainers to review or confirm an issue before opening a PR. Opening PRs without confirmation can sometimes create unnecessary noise. Hope you’ll keep this in mind next time.

and you definitely have an eagle eye for catching small UI alignment issues.
@Utkarsh-123github what do you think about this? Are we okay accepting small alignment changes like this right now?

@Utkarsh-123github
Copy link
Member

Hi @Kuzuri247,
As Tushar mentioned earlier, and as I’ve also noted in previous PR comments, please make sure to wait for an issue to be triaged and assigned before opening a PR.

For this particular change, since it’s quite small, it would be best to include it as part of one of the PRs you’re already assigned to, rather than creating a separate PR just for this. That will help keep things more streamlined.

Thanks for your understanding, and appreciate your contributions!

@github-project-automation github-project-automation bot moved this from Ready to review to Done in PR - Triage Group Jan 11, 2026
@Kuzuri247 Kuzuri247 deleted the layout branch January 11, 2026 07:59
@Kuzuri247 Kuzuri247 restored the layout branch January 12, 2026 07:17
@Kuzuri247 Kuzuri247 deleted the layout branch January 12, 2026 07:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

🐛 Bug: Position of the Github logo is a little off

3 participants