You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@cketti I fixed this bug locally in a new branch, pushed it to my fork on GitHub, and went on to create a pull request.
Does not contain merge commits. Rebase instead.
This was mentioned on the pull request page. I looked up what rebase is in Git and learned that it is a mechanism to combine changes from one branch into another, a potentially better alternative to merging.
But I'm confused about what I should do on my side as merging/rebasing is concerned with maintainers and not contributors.
When your pull request branch lives for a while, chances are that our main branch will see some additional commits. If one of the commits introduces changes that conflict with the changes in your pull request, you need to update the pull request to resolve this conflict. What we're asking is that in such a case you should rebase on our updated version of main rather than merging our updated main branch into your pull request branch.
This is probably not relevant for your fix. Just go ahead and create the pull request.
Checklist
App version
6.602
Where did you get the app from?
Google Play
Android version
Android 11
Device model
Realme 3 Pro
Steps to reproduce
Expected behavior
The button text should be in a dark color
Actual behavior
The button text color is white
Logs
The text was updated successfully, but these errors were encountered: