Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sort by play count #1080

Closed
wants to merge 42 commits into from
Closed

Conversation

Decimate1405
Copy link

@Decimate1405 Decimate1405 commented Mar 4, 2025

  • Feature request

marquee effect on song title
Merge pull request #1 from Decimate1405/marquee
fixed non marquee text alignment issue
…that's a temp fix for marquee after flutter 3.2.2
…or on the now playing bar adapts to the theme. Fixed bug where with the one line marquee enabled, even non-overflowing text uses a marquee on the player screen.
…ttings and renamed it "Allow one line break before using scrolling text"
@Chaphasilor
Copy link
Collaborator

@Decimate1405 thanks for the PR!

But something got messed up, the diff is massive, with tons of JSON files, and there are commits from your last PR in there.
Can you try to rebase onto the current redesign branch please?

@Decimate1405 Decimate1405 deleted the sort_by_play_count branch March 4, 2025 13:12
@Decimate1405 Decimate1405 restored the sort_by_play_count branch March 4, 2025 13:14
@Decimate1405
Copy link
Author

i apologize all this mess, git is sometimes confusing for me. I added the changes to the redesign branch but when I try to create a new PR with that branch I still see these old changes instead of just the new one. Trying to figure this out now

@Decimate1405
Copy link
Author

This is what I see on my current redesign branch

image

image

@Chaphasilor
Copy link
Collaborator

This is most likely because I squashed all the commits from your last PR into a new commit that contained everything. That helps to keep the commit history clean and uncluttered. But now Git still doesn't see your original commits in the upstream branch, so it tries to merge them in once again, which causes the conflict.

To fix this, you should reset the branch on your fork to the base branch, by checking it out (git checkout redesign) and then resetting it to upstream (git reset --hard upstream/redesign).
To avoid such issues in the future, always create a new branch for any changes your make and any PRs you open, and delete the branches after the PR gets merged. Then you can simply pull any new changes from the upstream redesign branch, and use that to create new branches :)

@Decimate1405
Copy link
Author

Thank you very much for explaining! Will work on this

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.

2 participants