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

Changed order of mobile layers to unscramble display on help pages #2439

Merged

Conversation

HopsAndHops
Copy link
Contributor

@HopsAndHops HopsAndHops commented Oct 27, 2023

Changed order of mobile layers to unscramble display on help pages on all FV keyboards affected.

Approved by @caforbes

@LornaSIL LornaSIL added this to In progress in Keyboards Oct 27, 2023
@keyman-server
Copy link
Collaborator

This pull request is from an external repo and will not automatically be built. The build must still be passed before it can be merged. Ask one of the team members to make a manual build of this PR.

@LornaSIL
Copy link
Contributor

LornaSIL commented Nov 7, 2023

@HopsAndHops is this still in draft or do you need it reviewed and approved?

@HopsAndHops
Copy link
Contributor Author

@LornaSIL still draft for now! Thanks for checking in :)

@HopsAndHops HopsAndHops marked this pull request as ready for review November 7, 2023 19:22
@LornaSIL
Copy link
Contributor

The system did not notify me that you had changed the status to "ready for review" so I guess in the future it would be good to tag one of us. I'll check it.

@HopsAndHops
Copy link
Contributor Author

@LornaSIL Thanks for letting me know! I'll tag you going forward :)

@LornaSIL
Copy link
Contributor

The system did not notify me that you had changed the status to "ready for review" so I guess in the future it would be good to tag one of us. I'll check it.

I should have said JUST when you change the status or label. We do get notified when you make a change in the PR like changed files.

@LornaSIL
Copy link
Contributor

@HopsAndHops Because I approved #2458 there is now a merge conflict because this PR also makes changes to fv_nuxalk. I think you'll need to resolve the conflicts before I can approve it.

@DavidLRowe
Copy link
Contributor

Would it work to remove fv_nuxalk changes from this PR? Then, if necessary, you could make a new PR with just those fv_nuxalk changes. (I'm not sure if that addresses the problem, but might be easy enough to try.)

@HopsAndHops
Copy link
Contributor Author

Whoops my bad, totally forgot that Nuxalk was included in this batch. I'll resolve those conflicts shortly

@keyman-server
Copy link
Collaborator

This pull request is from an external repo and will not automatically be built. The build must still be passed before it can be merged. Ask one of the team members to make a manual build of this PR.

@HopsAndHops
Copy link
Contributor Author

No dice, I'll undo the changes on the changes to Nuxalk and make another PR with only those changes

@keyman-server
Copy link
Collaborator

This pull request is from an external repo and will not automatically be built. The build must still be passed before it can be merged. Ask one of the team members to make a manual build of this PR.

Copy link
Contributor

@LornaSIL LornaSIL left a comment

Choose a reason for hiding this comment

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

LGTM

@LornaSIL LornaSIL merged commit 0467033 into keymanapp:master Nov 14, 2023
2 checks passed
Keyboards automation moved this from In progress to Done Nov 14, 2023
@HopsAndHops HopsAndHops deleted the mobile_unscrambling branch November 17, 2023 00:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Keyboards
  
Done
Development

Successfully merging this pull request may close these issues.

None yet

4 participants