Skip to content

Updated README: added Quick Tips section after Game Launcher#1587

Closed
rabia-sarfaraz wants to merge 15 commits intoHyDE-Project:masterfrom
rabia-sarfaraz:myfreshbranch
Closed

Updated README: added Quick Tips section after Game Launcher#1587
rabia-sarfaraz wants to merge 15 commits intoHyDE-Project:masterfrom
rabia-sarfaraz:myfreshbranch

Conversation

@rabia-sarfaraz
Copy link

@rabia-sarfaraz rabia-sarfaraz commented Feb 9, 2026

Pull Request

Description

This PR updates the README.md by adding a Quick Tips section after the Game Launcher images.
The new section provides guidance for enabling the app bar at the bottom of the HyDE interface.

  • Updates README documentation.
  • Adds step-by-step instructions for a better user experience.
  • No code changes are included.

Type of change

  • Documentation update (non-breaking change; modified files are limited to the documentation)

Checklist

  • I have read the CONTRIBUTING document.
  • My change follows the code style of this project.
  • My commit message follows the commit guidelines.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Additional context

This is a straightforward README enhancement to guide users on app bar configuration.

Summary by CodeRabbit

  • Documentation

    • Added a "Quick Tips" section explaining how to switch themes quickly: press Mod + T, choose a theme, and apply instantly without restarting.
  • Style

    • Menu item border-radius now applies to all items (not just hovered) and a 0.25s transition was added for smoother menu interactions.
  • Chores

    • Updated several local config files: adjusted logo command, updated Nvidia cursor guidance, added float rules for Steam UI windows, and changed lockscreen variable fallback behavior.

florianvazelle and others added 13 commits January 16, 2026 12:12
# Pull Request

## Description

This change fixes how the lockscreen command is selected from
environment variables.

## Type of change

Please put an `x` in the boxes that apply:

- [x] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that would cause existing
functionality to not work as expected)
- [ ] **Documentation update** (non-breaking change; modified files are
limited to the documentations)
- [ ] **Technical debt** (a code change that does not fix a bug or add a
feature but makes something clearer for devs)
- [ ] **Other** (provide details below)

## Checklist

Please put an `x` in the boxes that apply:

- [x] I have read the
[CONTRIBUTING](https://github.com/HyDE-Project/HyDE/blob/master/CONTRIBUTING.md)
document.
- [x] My code follows the code style of this project.
- [x] My commit message follows the [commit
guidelines](https://github.com/HyDE-Project/HyDE/blob/master/COMMIT_MESSAGE_GUIDELINES.md).
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added a changelog entry.
- [ ] I have added necessary comments/documentation to my code.
- [ ] I have added tests to cover my changes.
- [ ] I have tested my code locally and it works as expected.
- [ ] All new and existing tests passed.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Refactor**
* Adjusted the configuration precedence order for lockscreen selection,
improving how default values are resolved when multiple configuration
options are available.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
# Pull Request

## Description

Another day, another waybar menu fixes.

I have noticed some selection glitch and added fix for it.

Also, added some quick `transition` animation effect.

|Before|After|
|-|-|
|![Video_2026-01-17_23-12-18 (online-video-cutter
com)](https://github.com/user-attachments/assets/ecd96d4c-150e-4a82-88a4-3aa9a46932c7)|![Video_2026-01-17_23-12-40
(online-video-cutter
com)](https://github.com/user-attachments/assets/4d956f5b-4b4e-4959-a36e-025b33c80e59)|

## Type of change

- [x] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that would cause existing
functionality to not work as expected)
- [ ] **Documentation update** (non-breaking change; modified files are
limited to the documentations)
- [ ] **Technical debt** (a code change that does not fix a bug or add a
feature but makes something clearer for devs)
- [ ] **Other** (provide details below)

## Checklist

- [x] I have read the
[CONTRIBUTING](https://github.com/HyDE-Project/HyDE/blob/master/CONTRIBUTING.md)
document.
- [x] My code follows the code style of this project.
- [x] My commit message follows the [commit
guidelines](https://github.com/HyDE-Project/HyDE/blob/master/COMMIT_MESSAGE_GUIDELINES.md).
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added a changelog entry.
- [ ] I have added necessary comments/documentation to my code.
- [ ] I have added tests to cover my changes.
- [x] I have tested my code locally and it works as expected.
- [ ] All new and existing tests passed.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Style**
* Menu items now display rounded corners at all times for consistent
visual appearance
* Added smooth transitions and refined hover effects for submenu items
with updated color styling

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
…ct#1565)

# Pull Request

## Description

Added floating for Steam settings and Steam Friends List , isn't that
how it should be especially for Friends List

## Type of change

- [ x ] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that would cause existing
functionality to not work as expected)
- [ ] **Documentation update** (non-breaking change; modified files are
limited to the documentations)
- [ ] **Technical debt** (a code change that does not fix a bug or add a
feature but makes something clearer for devs)
- [ ] **Other** (provide details below)

## Checklist

- [ x ] I have read the
[CONTRIBUTING](https://github.com/HyDE-Project/HyDE/blob/master/CONTRIBUTING.md)
document.
- [ x ] My code follows the code style of this project.
- [ ] My commit message follows the [commit
guidelines](https://github.com/HyDE-Project/HyDE/blob/master/COMMIT_MESSAGE_GUIDELINES.md).
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added a changelog entry.
- [ x ] I have added necessary comments/documentation to my code.
- [ x ] I have added tests to cover my changes.
- [ x ] I have tested my code locally and it works as expected.
- [ x ] All new and existing tests passed.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Chores**
* Updated window configuration to float Friends List and Steam Settings
windows by default, improving their behavior in the window manager.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
…t#1579)

# Pull Request

## Description

The config.jsonc file for fastfetch used `$(fastfetch.sh logo)` as the
source for the logo fastfetch displays. This meant that even when the
user copies the script and edits it, following the instructions in the
documentation, when starting the terminal, the displayed logo will be a
randomly chosen one, instead of using the user's custom script.

To fix this, I simply replaced the source with `$(hyde-shell fastfetch
logo)`, which loads the user-defined script first.

## Type of change

Please put an `x` in the boxes that apply:

- [x] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that would cause existing
functionality to not work as expected)
- [ ] **Documentation update** (non-breaking change; modified files are
limited to the documentations)
- [ ] **Technical debt** (a code change that does not fix a bug or add a
feature but makes something clearer for devs)
- [ ] **Other** (provide details below)

## Checklist

Please put an `x` in the boxes that apply:

- [x] I have read the
[CONTRIBUTING](https://github.com/HyDE-Project/HyDE/blob/master/CONTRIBUTING.md)
document.
- [x] My code follows the code style of this project.
- [x] My commit message follows the [commit
guidelines](https://github.com/HyDE-Project/HyDE/blob/master/COMMIT_MESSAGE_GUIDELINES.md).
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added a changelog entry.
- [ ] I have added necessary comments/documentation to my code.
- [ ] I have added tests to cover my changes.
- [x] I have tested my code locally and it works as expected.
- [ ] All new and existing tests passed.

## Screenshots

(if appropriate)

## Additional context

This seems like a really small change, so I didn't do all the rigorous
testing, I hope that's okay and I apologize in advance if not.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Enhanced migration guide with improved clarity and grammatical
corrections for better user comprehension

* **Chores**
* Updated system display configuration to use an improved logo
generation mechanism

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
# Pull Request

## Description

`cursor:allow_dumb_copy` has been phased out for 2 years in favor of
`cursor:use_cpu_buffer`, which doesn't have the same drawbacks and is
necessary for hardware cursor on NVIDIA
hyprwm/Hyprland#8424 (comment)
https://wiki.hypr.land/Configuring/Variables/#:~:text=use%5Fcpu%5Fbuffer

## Type of change

Please put an `x` in the boxes that apply:

- [x] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that would cause existing
functionality to not work as expected)
- [ ] **Documentation update** (non-breaking change; modified files are
limited to the documentations)
- [ ] **Technical debt** (a code change that does not fix a bug or add a
feature but makes something clearer for devs)
- [ ] **Other** (provide details below)

## Checklist

Please put an `x` in the boxes that apply:

- [x] I have read the
[CONTRIBUTING](https://github.com/HyDE-Project/HyDE/blob/master/CONTRIBUTING.md)
document.
- [x] My code follows the code style of this project.
- [x] My commit message follows the [commit
guidelines](https://github.com/HyDE-Project/HyDE/blob/master/COMMIT_MESSAGE_GUIDELINES.md).
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [ ] I have added a changelog entry.
- [ ] I have added necessary comments/documentation to my code.
- [ ] I have added tests to cover my changes.
- [x] I have tested my code locally and it works as expected.
- [x] All new and existing tests passed.

## Screenshots

(if appropriate)

## Additional context

Add any other context about the problem here.


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Updated Nvidia hardware cursor configuration guidance with clarified
requirements for CPU buffer settings to ensure optimal hardware cursor
compatibility.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

⚠️ Warning: PR targeting master branch detected!

This PR is targeting master but should target dev instead.

According to our Quarterly Release Policy:

  • All pull requests must be submitted to the dev branch
  • Changes go through dev first for testing before being merged to master during quarterly release windows (1st & 3rd Fridays)
  • PRs to master are only allowed for emergencies

Required Action:

  1. Change the base branch from master to dev
  2. Follow the pull request template

If this is an emergency fix, please add a comment explaining why it needs to target master directly.


This is an automated message enforcing our quarterly release workflow.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 9, 2026

📝 Walkthrough

Walkthrough

Multiple configuration and documentation updates: README adds a "Quick Tips" entry; Hypr, Waybar, fastfetch, and lockscreen configs are modified (comments, command paths, window rules, variable assignment order); Waybar CSS selectors and transitions adjusted.

Changes

Cohort / File(s) Summary
Documentation
README.md
Added "Quick Tips" section describing theme switching via Mod + T.
Hyprland configs
Configs/.config/hypr/nvidia.conf, Configs/.config/hypr/windowrules.conf, Configs/.local/lib/hyde/lockscreen.sh
Updated Nvidia cursor guidance (use_cpu_buffer vs allow_dumb_copy), added two Steam-related title-based float rules, and swapped default assignment order for LOCKSCREEN/HYPRLAND_LOCKSCREEN (changes fallback/precedence). Review variable precedence and windowrule patterns.
Fastfetch config
Configs/.config/fastfetch/config.jsonc
Replaced logo command from "$(fastfetch.sh logo)" to "$(hyde-shell fastfetch logo)" — check external command availability.
Waybar styles/includes
Configs/.config/waybar/includes/border-radius.css, Configs/.local/share/waybar/includes/border-radius.css, Configs/.local/share/waybar/styles/defaults.css
Changed selector from menu menuitem:hover to menu menuitem (applies border-radius unconditionally) and added transition: 0.25s for menu menuitem. Review visual impact and selector specificity.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

Suggested reviewers

  • kRHYME7

Poem

🐰 I hopped through configs, crisp and light,
Swapped a logo and tuned the sight,
Borders round and themes that gleam,
Locks that fall in kinder scheme,
I nibble tweaks — a small delight!

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title check ⚠️ Warning The title claims the PR adds a Quick Tips section after Game Launcher, but the actual changes span multiple configuration files (Hyprland, Waybar CSS, fastfetch, lockscreen) unrelated to README documentation. Update the title to accurately reflect the comprehensive nature of changes, such as 'Configuration updates: Nvidia cursor handling, Waybar styling, and Steam window rules' or provide context on all modified files.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

No actionable comments were generated in the recent review. 🎉


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@README.md`:
- Around line 290-299: The "Enabling App Bar at the Bottom" section is using
generic UI terms that don't apply to HyDE's file-based configuration; either
remove this placeholder or replace it with a HyDE-specific procedure: mention
the exact feature name (e.g., "bottom panel / waybar slot"), point to the
configuration file or script to edit (e.g., the HyDE panel/waybar config
referenced elsewhere in the README), show the exact setting/option name to
change (the "Enable Bottom App Bar" toggle should be replaced with the actual
config key used by HyDE), and replace "Restart the app" with the correct action
(e.g., reload the HyDE/waybar configuration or restart the desktop session) so
the instructions match HyDE's configuration approach and terminology.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

⚠️ Warning: PR targeting master branch detected!

This PR is targeting master but should target dev instead.

According to our Quarterly Release Policy:

  • All pull requests must be submitted to the dev branch
  • Changes go through dev first for testing before being merged to master during quarterly release windows (1st & 3rd Fridays)
  • PRs to master are only allowed for emergencies

Required Action:

  1. Change the base branch from master to dev
  2. Follow the pull request template

If this is an emergency fix, please add a comment explaining why it needs to target master directly.


This is an automated message enforcing our quarterly release workflow.

@github-actions
Copy link
Contributor

github-actions bot commented Feb 9, 2026

⚠️ Warning: PR targeting master branch detected!

This PR is targeting master but should target dev instead.

According to our Quarterly Release Policy:

  • All pull requests must be submitted to the dev branch
  • Changes go through dev first for testing before being merged to master during quarterly release windows (1st & 3rd Fridays)
  • PRs to master are only allowed for emergencies

Required Action:

  1. Change the base branch from master to dev
  2. Follow the pull request template

If this is an emergency fix, please add a comment explaining why it needs to target master directly.


This is an automated message enforcing our quarterly release workflow.

@rubiin
Copy link
Collaborator

rubiin commented Mar 24, 2026

the history for the PR seems to be messed up. Please open a new one

@rubiin rubiin closed this Mar 24, 2026
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.

8 participants